From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: master 050b830 3/3: Do interactive mode tagging for finder.el
Date: Sat, 20 Mar 2021 11:23:38 +0200 [thread overview]
Message-ID: <83o8fech5x.fsf@gnu.org> (raw)
In-Reply-To: <874kh6kxeb.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 20 Mar 2021 10:05:48 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: stefan@marxist.se, emacs-devel@gnu.org
> Date: Sat, 20 Mar 2021 10:05:48 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I guess the disagreement is about what exactly does "mode-specific"
> > mean here.
>
> If there are unclear points in the manual under
>
> 21.2.4 Specifying Modes For Commands
>
> I can try to clarify.
Just what I wrote above: that subsection talks about commands "tied to
a mode", or commands that can be used "in pretty much any mode", or
make no sense "outside" of a mode, or commands that "belong to a
mode", without clarifying what that means.
My interpretation of the notion of "being in the FOO mode" is that the
current buffer has FOO as its major mode. Under that interpretation,
commands that can only be invoked by mouse gestures cannot be
"mode-specific", because such commands normally can be invoked while
the current buffer is any buffer under any mode. The relevant buffer
is provided by the mouse event, not by the current buffer.
next prev parent reply other threads:[~2021-03-20 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 8:15 master 050b830 3/3: Do interactive mode tagging for finder.el Eli Zaretskii
2021-03-19 8:28 ` Lars Ingebrigtsen
2021-03-19 8:37 ` Eli Zaretskii
2021-03-19 16:23 ` Stefan Kangas
2021-03-19 16:35 ` Eli Zaretskii
2021-03-19 17:08 ` Stefan Kangas
2021-03-19 19:39 ` Eli Zaretskii
2021-03-19 19:55 ` [External] : " Drew Adams
2021-03-20 7:51 ` Lars Ingebrigtsen
2021-03-20 8:15 ` Lars Ingebrigtsen
2021-03-20 9:02 ` Eli Zaretskii
2021-03-20 9:05 ` Lars Ingebrigtsen
2021-03-20 9:23 ` Eli Zaretskii [this message]
2021-03-21 7:47 ` Lars Ingebrigtsen
2021-03-19 17:22 ` Dmitry Gutov
2021-03-19 17:47 ` Stefan Monnier
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=83o8fech5x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).