From: Juri Linkov <juri@jurta.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: M-g in dired
Date: Sat, 05 Nov 2005 09:55:35 +0200 [thread overview]
Message-ID: <87pspfa8ig.fsf@jurta.org> (raw)
In-Reply-To: <E1EYCzj-00045Z-VT@fencepost.gnu.org> (Richard M. Stallman's message of "Fri, 04 Nov 2005 20:37:23 -0500")
> However, if this is not what the docstring meant, and leaving the logic
> of the current return value is desirable, then maybe `lookup-key' needs
> an additional argument defining another logic of its return value.
>
> Why?
>
> Otherwise, almost all code in `lookup-key' should be duplicated in
> `shadow_lookup'.
>
> Why?
To fix the bug, I think changes should be made in `shadow_lookup'.
Let's see how it currently works for the case when dired-mode-map
defines the "M-g" key, and the global-map defines "M-gn":
`shadow_lookup' iterates over two maps (dired and global) and calls
`Flookup_key' on them. When `Flookup_key' returns 1 for the key
"M-gn" on the dired map, the loop in `shadow_lookup' skips it
and advances to the next iteration on the global map where it finds
the command `next-error' bound to "M-gn", and returns it.
This causes the current code to assume that "M-gn" in the global map
is not shadowed by "M-g" in the dired map. It fails due to the value 1
returned by `Flookup_key', which is unsuitable to decide whether "M-g"
is bound in the dired map or not, and thus whether it shadows "M-gn"
in the global map or not.
To fix this, I intended to use the same code as `Flookup_key' uses
to process key sequences, but additionally to check whether a shorter
prefix key is bound or not. This can be achieved either by adding
a new argument to `Flookup_key' to check if a key is bound and to
return the corresponding return value (and not to change its current
default semantics of the return value), or to duplicate most code of
`Flookup_key' in `shadow_lookup' to do this.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-11-05 7:55 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 11:27 M-g in dired Juri Linkov
2005-10-15 19:33 ` Kim F. Storm
2005-10-16 14:40 ` Richard M. Stallman
2005-10-16 14:40 ` Richard M. Stallman
2005-10-31 1:14 ` Richard Stallman
2005-10-31 7:47 ` Juri Linkov
2005-11-01 2:13 ` Richard M. Stallman
2005-11-01 9:16 ` Juri Linkov
2005-11-01 14:09 ` Andreas Schwab
2005-11-01 19:55 ` Juri Linkov
2005-11-02 10:28 ` Richard M. Stallman
2005-11-02 10:27 ` Richard M. Stallman
2005-11-03 7:48 ` Juri Linkov
2005-11-03 15:03 ` Stefan Monnier
2005-11-04 12:06 ` Juri Linkov
2005-11-05 1:37 ` Richard M. Stallman
2005-11-05 7:55 ` Juri Linkov [this message]
2005-11-05 23:43 ` Richard M. Stallman
2005-11-07 14:27 ` Juri Linkov
2005-11-07 16:03 ` Stefan Monnier
2005-11-08 12:43 ` Juri Linkov
2005-11-09 2:57 ` Richard M. Stallman
2005-11-07 21:56 ` Richard M. Stallman
2005-11-03 21:41 ` Richard M. Stallman
[not found] <446C7B73.60907@earthlink.net>
2006-05-19 2:04 ` Richard Stallman
2006-05-19 3:04 ` Juri Linkov
2006-05-19 8:16 ` Kim F. Storm
2006-05-19 8:43 ` Miles Bader
2006-05-19 12:37 ` Kim F. Storm
2006-05-20 13:45 ` Juri Linkov
2006-05-20 5:03 ` Richard Stallman
[not found] ` <E1FhJd4-000822-Fe@fencepost.gnu.org>
2006-05-20 13:45 ` Juri Linkov
2006-05-20 15:46 ` Johan Bockgård
2006-05-20 20:03 ` Juri Linkov
2006-05-20 20:41 ` Romain Francoise
2006-05-21 0:56 ` Richard Stallman
2006-05-21 4:28 ` Juri Linkov
2006-05-22 2:38 ` Richard Stallman
2006-05-22 13:46 ` Juri Linkov
2006-05-22 20:37 ` Richard Stallman
2006-05-23 5:16 ` Juri Linkov
2006-05-19 18:53 ` David Hansen
2006-05-19 19:57 ` Reiner Steib
2006-05-19 20:07 ` Miles Bader
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=87pspfa8ig.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).