unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: kifer@cs.sunysb.edu (Michael Kifer)
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Viper doesn't properly handle C-h k for mouse clicks
Date: Wed, 21 Mar 2007 13:01:28 -0400	[thread overview]
Message-ID: <11043.1174496488@cs.sunysb.edu> (raw)
In-Reply-To: Message from Chong Yidong <cyd@stupidchicken.com>  of "Wed, 21 Mar 2007 12:19:51 EDT." <874poepo0o.fsf@stupidchicken.com>


> Chong Yidong <cyd@stupidchicken.com> writes:
> 
> > The problem is that viper handles describe-key using advice.
> 
> Since there has been no response, I went ahead and hacked the viper
> advice so that it works for this case at least.  We should revisit
> this issue after the release.
> 


sorry, I didn't have the time to look into this.
did you commit? I'll take a look then.

  reply	other threads:[~2007-03-21 17:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05  2:56 [lennart.borgman@gmail.com: C-h k does not catch text properies keymaps] Richard Stallman
2007-03-05 15:27 ` Chong Yidong
2007-03-05 21:21   ` David Kastrup
2007-03-05 21:33     ` Lennart Borgman (gmail)
2007-03-05 22:11       ` Chong Yidong
2007-03-05 22:35         ` Lennart Borgman (gmail)
2007-03-05 22:38           ` Chong Yidong
2007-03-05 23:30             ` Lennart Borgman (gmail)
2007-03-06 22:36             ` Richard Stallman
2007-03-06 22:48               ` Lennart Borgman (gmail)
2007-03-07  9:10                 ` Richard Stallman
2007-03-07 12:01                   ` Lennart Borgman (gmail)
2007-03-17 20:32                     ` Viper doesn't properly handle C-h k for mouse clicks Chong Yidong
2007-03-21 16:19                       ` Chong Yidong
2007-03-21 17:01                         ` Michael Kifer [this message]
2007-03-06 16:01       ` [lennart.borgman@gmail.com: C-h k does not catch text properies keymaps] Richard Stallman
2007-03-06 17:25         ` Lennart Borgman (gmail)
2007-03-05 21:50   ` Richard Stallman

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=11043.1174496488@cs.sunysb.edu \
    --to=kifer@cs.sunysb.edu \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    /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).