unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Kifer <kifer@cs.sunysb.edu>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Romain Francoise <rfrancoise@debian.org>,
	Stefano Zacchiroli <zack@upsilon.cc>,
	1072@emacsbugs.donarmstrong.com
Subject: 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 15:55:20 -0500	[thread overview]
Message-ID: <20081114155520.5ca2f5d0@kiferserv> (raw)
In-Reply-To: <200811142040.mAEKeL7R015416@mothra.ics.uci.edu>



On Fri, 14 Nov 2008 12:40:21 -0800 (PST)
Dan Nicolaescu <dann@ics.uci.edu> wrote:

> Michael Kifer <kifer@cs.sunysb.edu> writes:
> 
>   > On Fri, 14 Nov 2008 14:48:14 +0100
>   > Stefano Zacchiroli <zack@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.






  reply	other threads:[~2008-11-14 20:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081006095245.2FE176A99@usha.takhisis.invalid>
     [not found] ` <20081006124104.25eb7619@kiferserv>
2008-10-07 14:49   ` bug#1072: Viper version is 3.14 of April 06, 2008; can't exit viper insert mode with ESC using emacsclient -t Stefano Zacchiroli
2008-10-07 16:21     ` Lennart Borgman (gmail)
2008-10-07 23:06       ` Michael Kifer
2008-10-07 23:56         ` Lennart Borgman (gmail)
2008-11-14 13:48         ` Stefano Zacchiroli
2008-11-14 19:50           ` Michael Kifer
2008-11-14 20:40             ` Dan Nicolaescu
2008-11-14 20:55               ` Michael Kifer [this message]
2008-11-14 21:22                 ` Dan Nicolaescu
2008-11-14 22:39                   ` Stefan Monnier
2008-11-14 22:46                     ` Michael Kifer
2008-11-15  1:32                       ` Stefano Zacchiroli
     [not found]                         ` <20081116000252.32203b3a@kiferserv>
2008-11-16 16:18                           ` Stefano Zacchiroli
2008-10-09  9:08       ` Stefano Zacchiroli
2008-10-09 14:24         ` Lennart Borgman (gmail)
2008-10-07 16:28     ` Michael Kifer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081114155520.5ca2f5d0@kiferserv \
    --to=kifer@cs.sunysb.edu \
    --cc=1072@emacsbugs.donarmstrong.com \
    --cc=dann@ics.uci.edu \
    --cc=rfrancoise@debian.org \
    --cc=zack@upsilon.cc \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).