From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: [External] : Re: command mode-specificity [was: scratch/command 064f146 1/2: Change...]
Date: Wed, 17 Feb 2021 16:42:50 +0100 [thread overview]
Message-ID: <87r1len1j9.fsf@gnus.org> (raw)
In-Reply-To: <jwvmtw2vi58.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 17 Feb 2021 10:20:42 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I think it would be good to try and clarify what should be the
> criterion, and not in terms of "should be listed in M-x" since that
> inherently depends on opinions, but rather in more technical terms that
> depend on what the command does.
> [ A bit like with docstrings: we like docstrings that say what the
> function does rather than when/where it's meant to be used. ]
>
> Maybe something like "would inevitably signal an error"?
I don't think there's any hard and fast criterion that can be used,
though. For instance, there was one mode I tagged up that had a
`foo-quit' command, which just buried the buffer. Now, that's a command
that can work anywhere... but the reason it exists is presumably
because the person who wrote it either missed out on inheriting from
`special-mode', or didn't know you can bind `bury-buffer' directly, or
whatever.
In any case, it's not a command that anybody not using `foo' will (or
should) be using, so I'd say (and I did say) that it's a mode-specific
command.
Now, lots of commands do, indeed, signal an error outside the proper
mode, or completely mess things up outside the proper mode, and those
are no-brainers.
I'd planned on writing a little essay for the lispref manual about this,
once I'd gotten some more experience, because it's not immediately
obvious what's the right thing to do until you've evaluated a few
instances.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-02-17 15:42 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 19:50 command mode-specificity [was: scratch/command 064f146 1/2: Change...] Drew Adams
2021-02-16 19:54 ` Stefan Monnier
2021-02-16 20:23 ` [External] : " Drew Adams
2021-02-16 20:53 ` Lars Ingebrigtsen
2021-02-16 22:05 ` Drew Adams
2021-02-16 22:15 ` Lars Ingebrigtsen
2021-02-16 22:31 ` Drew Adams
2021-02-16 22:38 ` Lars Ingebrigtsen
2021-02-16 23:22 ` Drew Adams
2021-02-17 0:35 ` Óscar Fuentes
2021-02-17 15:47 ` Eli Zaretskii
2021-02-17 15:59 ` Dmitry Gutov
2021-02-17 16:15 ` Stefan Monnier
2021-02-17 16:17 ` Eli Zaretskii
2021-02-17 19:52 ` Dmitry Gutov
2021-02-17 20:21 ` Eli Zaretskii
2021-02-17 22:05 ` Dmitry Gutov
2021-02-17 17:36 ` Óscar Fuentes
2021-02-17 18:44 ` Drew Adams
2021-02-17 17:57 ` Drew Adams
2021-02-17 2:39 ` Yuan Fu
2021-02-17 3:22 ` Eli Zaretskii
2021-02-17 0:13 ` Óscar Fuentes
2021-02-17 0:17 ` Drew Adams
2021-02-17 0:54 ` Óscar Fuentes
2021-02-17 18:11 ` Drew Adams
2021-02-17 18:40 ` Stefan Kangas
2021-02-17 19:01 ` Drew Adams
2021-02-17 20:09 ` Yuan Fu
2021-02-17 22:31 ` Lars Ingebrigtsen
2021-02-17 0:40 ` Stefan Monnier
2021-02-17 0:59 ` Óscar Fuentes
2021-02-17 11:20 ` Lars Ingebrigtsen
2021-02-17 14:01 ` Stefan Monnier
2021-02-17 14:19 ` Lars Ingebrigtsen
2021-02-17 15:20 ` Stefan Monnier
2021-02-17 15:42 ` Lars Ingebrigtsen [this message]
2021-02-17 16:12 ` Stefan Monnier
2021-02-17 18:26 ` Lars Ingebrigtsen
2021-02-17 18:47 ` Drew Adams
2021-02-17 18:41 ` Drew Adams
2021-02-17 18:28 ` Drew Adams
2021-02-17 16:07 ` Eli Zaretskii
2021-02-17 19:30 ` Lars Ingebrigtsen
2021-02-17 20:07 ` Eli Zaretskii
2021-02-17 21:00 ` Óscar Fuentes
2021-02-18 11:33 ` Lars Ingebrigtsen
2021-02-18 14:37 ` Eli Zaretskii
2021-02-18 15:53 ` Lars Ingebrigtsen
2021-02-20 13:30 ` Lars Ingebrigtsen
2021-02-20 14:43 ` Stefan Monnier
2021-02-20 14:52 ` Lars Ingebrigtsen
2021-02-20 18:00 ` Dmitry Gutov
2021-02-21 13:10 ` Lars Ingebrigtsen
2021-02-21 19:57 ` Dmitry Gutov
2021-02-19 12:09 ` [External] : " Lars Ingebrigtsen
2021-02-19 12:27 ` Eli Zaretskii
2021-02-18 16:30 ` Alan Mackenzie
2021-02-18 16:55 ` Óscar Fuentes
2021-02-18 17:08 ` Alan Mackenzie
2021-02-18 17:20 ` Óscar Fuentes
2021-02-18 17:35 ` Alan Mackenzie
2021-02-18 17:55 ` Robert Pluim
2021-02-18 18:15 ` Yuan Fu
2021-02-19 8:47 ` Robert Pluim
2021-02-19 8:55 ` Eli Zaretskii
2021-02-19 11:21 ` Robert Pluim
2021-02-19 12:25 ` Eli Zaretskii
2021-02-18 18:15 ` Alan Mackenzie
2021-02-18 19:32 ` Óscar Fuentes
2021-02-18 20:14 ` Alan Mackenzie
2021-02-18 20:24 ` Eli Zaretskii
2021-02-18 19:42 ` Eli Zaretskii
2021-02-18 19:57 ` Alan Mackenzie
2021-02-18 20:04 ` Eli Zaretskii
2021-02-19 12:10 ` Lars Ingebrigtsen
2021-02-19 12:41 ` Dmitry Gutov
2021-02-19 12:57 ` Lars Ingebrigtsen
2021-02-19 13:12 ` Dmitry Gutov
2021-02-17 19:02 ` Yuan Fu
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=87r1len1j9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ofv@wanadoo.es \
/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).