rot13-other-window

[Stephen J. Turnbull]

Aidan Kehoe writes:

 > Tim Connors wrote:
 > 
 > > Unfortunately, typing into the other window when using rot13-other-window
 > > doesn't do anything very sensible -- it just enters straight unrotted text
 > > into the buffer being viewed (well actually, it's probably applying rot1
 > > 26 times :).  Anyone got any patches to make entry into that other window
 > > become rot13'd into the real buffer?
 > 
 > This doesn't do quite what you *describe,* but it should suffice for
 > what you *want*. Needs Mule, and the Quail package. To enable, hit C-u
 > C-\ rot13 RET , and start typing; to disable, hit C-\ on its own.

Ah, so that's what he means by "sensible".

Note that C-\ is a toggle, switching between the "standard" input and
the rot13 input method at this point.  If you want to change to a
different input method (Sydneydian or Canberries? ;-), then you'll
need to use C-u C-\ again.  Also the default is initialized to nil, so
if you don't use other input methods, the first C-\ will prompt.

I think this is as close as you can get to what he describes without
writing a new rot13-other-window (rot13-mirror-window?).  If you do
rot13-other-window, what you get is a window on an indirect buffer
with a different display table, so whatever you put in either buffer
gets entered into the parent buffer.  This could be considered an
improvement on his request; this way you don't have to move point to
the other window, but still get the visual feedback.  And it's fewer
keystrokes once quail/rot13 becomes the default input method.

Hmm ... I wonder if quail really needs to depend on Mule?