From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: carlmarcos@tutanota.com, 56258@debbugs.gnu.org
Subject: bug#56258: Changing major-mode with mouse event
Date: Tue, 28 Jun 2022 14:50:16 +0200 [thread overview]
Message-ID: <87czetq7ef.fsf@gnus.org> (raw)
In-Reply-To: <ec1161b5063acb76c92b8c9a2b731005@webmail.orcon.net.nz> (Phil Sainty's message of "Tue, 28 Jun 2022 09:08:27 +1200")
Phil Sainty <psainty@orcon.net.nz> writes:
> Major modes would need to be identifiable as such in order to
> provide the menu you propose, and I don't believe there's a reliable
> way to do that at present for all major modes.
>
> We can identify major modes defined with `define-derived-mode'
> however, as all such modes have a `derived-mode-parent' property;
> and that does cover the majority.
Yes, it should be possible to provide a command to allow you to choose
between modes. But I think having something like that callable from the
mode line would be of limited value, but perhaps not? The reason is
that we just have So Many Modes -- over 500, at least, so discovering
modes via a menu would be cumbersome.
> p.s. Tangentially, I think it would be good if all symbols for both
> major and minor modes had (or rather, were expected to have) symbol
> properties to explicitly identify which type of mode they are,
> including differentiation between the various minor mode types
> (buffer-local, global, and 'globalized' pairings), as I think there
> would be other uses for being able to query the available modes.
Yes, that might be nice if you want to explore "what are the major
modes I can possibly use here?".
We almost kinda sorta have that. All minor modes should be defined via
define-minor-mode now, and that updates the global-minor-modes and
local-minor-mode variables. So all mode functions that aren't there are
major modes, so we could use heuristics to get us pretty far (along with
`derived-mode-parent').
However, we do have functions that end with -mode that aren't modes.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-28 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:58 bug#56258: Changing major-mode with mouse event carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-27 21:08 ` Phil Sainty
2022-06-28 12:50 ` Lars Ingebrigtsen [this message]
[not found] ` <87czetq7ef.fsf@gnus.org-N5eMbXh----2>
2022-06-28 23:17 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87czetq7ef.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=56258@debbugs.gnu.org \
--cc=carlmarcos@tutanota.com \
--cc=psainty@orcon.net.nz \
/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).