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

Previous Next

Full log

Message #61 received at 1072 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: kifer <at> cs.sunysb.edu
Cc: 1072 <at> debbugs.gnu.org, Stefano Zacchiroli <zack <at> upsilon.cc>,
        Romain Francoise <rfrancoise <at> debian.org>
Subject: Re: bug#1072: Viper version is 3.14 of April 06, 2008; can't exit viper insert mode with ESC using emacsclient -t
Date: Fri, 14 Nov 2008 13:22:44 -0800 (PST)

Michael Kifer <kifer <at> cs.sunysb.edu> writes:

  > On Fri, 14 Nov 2008 12:40:21 -0800 (PST)
  > Dan Nicolaescu <dann <at> ics.uci.edu> wrote:
  > 
  > > Michael Kifer <kifer <at> cs.sunysb.edu> writes:
  > > 
  > >   > On Fri, 14 Nov 2008 14:48:14 +0100
  > >   > Stefano Zacchiroli <zack <at> upsilon.cc> wrote:
  > >   > 
  > >   > > 1) viper-ESC-keyseq-timeout is a global variable, shared by all Emacs
  > >   > >    clients, can it be made local to a buffer (actually it would be
  > >   > >    enough to make it local to a client, but I don't believe it is
  > >   > >    possible), or there is some Viper magic which would defeat this
  > >   > >    solution not work?
  > >   > 
  > >   > I don't see a reason why this variable cannot be buffer-local.
  > > 
  > > Disclaimer: I don't know anything about viper.
  > > 
  > > But the above does not sound right: a buffer can be used in both an X11
  > > frame and a tty frame at the same time, so a buffer-local value won't
  > > work.
  > 
  > Yes, you are right. If there is a way to find out whether the selected window
  > is in a terminal frame or X frame then viper-ESC-keyseq-timeout can be made
  > into a function.

If (window-system) is nil, you are using a terminal frame.

Previous Next

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