From: Juanma Barranquero <lektu@terra.es>
Cc: emacs-devel@gnu.org
Subject: Re: find-aliases, where-did-you-go-little-command
Date: Thu, 07 Nov 2002 17:52:58 +0100 [thread overview]
Message-ID: <20021107174617.B693.LEKTU@terra.es> (raw)
In-Reply-To: <E189oH6-0007uk-00@fencepost.gnu.org>
On Thu, 07 Nov 2002 10:08:52 -0500, Richard Stallman <rms@gnu.org> wrote:
> Few people will try it if it is not on by default.
> It is harmless, right? So turn it on by default.
I've followed Stefan's suggestion and hardcoded it to be on by default.
If later it is decided to make it customizable is just a matter of
adding a variable and a two-lines change to `where-is'.
Then I've followed Kai's suggestion and commited it ;)
> In the current code, this feature inserts the same text that would
> otherwise be displayed in another buffer. It looks like that is true
> in your version also. So why say "and more so"?
In both the code before and after my patch, C-u C-h w does not insert
the exact same text that C-h w shows. Consider:
C-h w hi-lock-face-buffer =>
hi-lock-face-buffer is not on any key;
and highlight-regexp is on C-x w h, <menu-bar> <edit> <hi-lock> <highlight-regexp>
C-u C-h w hi-lock-face-buffer =>
M-x hi-lock-face-buffer RET;
and C-x w h, <menu-bar> <edit> <hi-lock> <highlight-regexp> (highlight-regexp)
The first format is more descriptive, so adding "and " seems more natural.
/L/e/k/t/u
prev parent reply other threads:[~2002-11-07 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 11:50 find-aliases, where-did-you-go-little-command Juanma Barranquero
2002-10-22 3:13 ` Richard Stallman
2002-10-22 8:46 ` Juanma Barranquero
2002-10-22 14:28 ` Stefan Monnier
2002-10-22 14:41 ` Juanma Barranquero
2002-10-23 7:12 ` Richard Stallman
2002-10-23 7:35 ` Stefan Monnier
2002-11-06 17:44 ` Juanma Barranquero
2002-11-06 19:27 ` Stefan Monnier
2002-11-06 21:49 ` Juanma Barranquero
2002-11-07 7:23 ` Kai Großjohann
2002-11-07 15:08 ` Richard Stallman
2002-11-07 16:52 ` Juanma Barranquero [this message]
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=20021107174617.B693.LEKTU@terra.es \
--to=lektu@terra.es \
--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).