From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: storm@cua.dk, emacs-devel@gnu.org
Subject: Re: Suggestion: Simple way to make conditional key bindings.
Date: Mon, 26 Aug 2002 12:21:18 -0400 [thread overview]
Message-ID: <200208261621.g7QGLIE25159@rum.cs.yale.edu> (raw)
In-Reply-To: 200208260036.g7Q0aSR12388@wijiji.santafe.edu
> One advantage (IMO) is that C-h k C-y will report yank or
> yank-with-properties depending on the actual function taken if
> you hit C-y.
>
> If we use menu-item, what will C-h c say?
Same thing (it runs the filter).
> (define-key global-map "\C-y" 'yank-careful)
> (defun yank-careful (...)
> "Reinsert the last stretch of killed text, like `yank'.
> Contrary to `yank' this function is careful to preserve some important
> text properties when yanking tables."
> ...)
>
> The advantage is that C-h k C-y doesn't just give you one of the two
> bindings but a docstring that describes both.
>
> I think that sometimes this will be better, but sometimes it will be
> better for C-h k to give the doc string for the specific command
> that will be executed.
Agreed. But in the example he gave I think that a docstring that
describes the range of behavior rather than the specific command is
better, because you can't expect the user to know that the current
string is "special".
I think that whether the docstring should cover all the possible behaviors
or just the specific current one depends on how what the behavior depends on:
if it's very implicit and/or changes often the first is preferable.
This is the case for his example.
OTOH if it's explicit and/or doesn't change often, then the latter is
preferable. This is the case (and the current behavior) for minor modes.
Stefan
next prev parent reply other threads:[~2002-08-26 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 12:05 Suggestion: Simple way to make conditional key bindings Kim F. Storm
2002-08-26 0:36 ` Richard Stallman
2002-08-26 16:21 ` Stefan Monnier [this message]
2002-08-30 10:27 ` Robert J. Chassell
-- strict thread matches above, loose matches on Subject: below --
2002-08-23 12:52 David PONCE
[not found] <3D49FF140074EFAE@mel-rta7.wanadoo.fr>
2002-08-23 13:16 ` Kim F. Storm
2002-08-23 17:22 ` Stefan Monnier
2002-08-25 23:33 ` Kim F. Storm
2002-08-26 15:47 ` Stefan Monnier
2002-08-26 19:33 ` Miles Bader
2002-08-27 19:05 ` Richard Stallman
2002-08-27 22:58 ` Kim F. Storm
2002-08-28 23:32 ` Richard Stallman
2002-08-29 8:54 ` Kim F. Storm
2002-08-28 1:00 ` Miles Bader
2002-08-28 1:22 ` Stefan Monnier
2002-08-27 11:23 ` Kim F. Storm
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=200208261621.g7QGLIE25159@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).