GNU bug report logs - #1072
23.0.60; can't exit viper insert mode with ESC using emacsclient -t

Previous Next

Full log

View this message in rfc822 format

From: Michael Kifer <kifer <at> cs.sunysb.edu>
To: Stefano Zacchiroli <zack <at> upsilon.cc>
Cc: 1072-quiet <at> debbugs.gnu.org
Subject: bug#1072: Viper version is 3.14 of April 06, 2008; can't exit viper insert mode with ESC using emacsclient -t
Date: Sat, 22 Nov 2008 01:35:24 -0500

ok, it looks like I fixed that one also in CVS. Pls try.

On Thu, 20 Nov 2008 14:18:48 +0100
Stefano Zacchiroli <zack <at> upsilon.cc> wrote:

> On Sun, Nov 16, 2008 at 08:31:56PM -0500, Michael Kifer wrote:
> > Can you give me the exact sequence of steps?
> 
> Yes, see below.
> 
> > I tried
> > emacs -q --daemon -f server-start
> > then
> > emacsclient -t
> > M-x viper-mode
> > then I went into the insert mode and did M-x. It didn't leave the insert
> > mode.
> 
> Correct, the sequence you mention does *not* exhibit the problem. Even
> thought that is not surprising, given that the server you are
> attaching your client to started as a daemon, and not as a X11 frame,
> so I guess it gets the "correct" (wrt console) viper initialization
> environment.
> 
> The following sequence does exhibit the bug:
> 
>   emacs -q -f server-start    # starts an X11 emacs
>   M-x viper-mode	      # enable Viper _in the X11_ emacs
>   emacsclient -t
>   # now M-something leaves insert mode
> 
> Note that it is important that it is relevant to enable viper from the
> X11 emacs. If you enable viper-mode in the console client everything
> is fine.
> 
> This is not surprising either, as we've already settled that the
> relevant point is where viper gets initialized.
> 
> Cheers.
> 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.