From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 50147@debbugs.gnu.org
Subject: bug#50147: Wishlist: Display mode name in mode line tooltip
Date: Sun, 22 Aug 2021 16:46:34 +0200 [thread overview]
Message-ID: <874kbhzgdx.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmmZr2DjSovDwujZhRg-nCiMGPq22nQn9x4RNKeUW_Q46Q@mail.gmail.com> (Stefan Kangas's message of "Sat, 21 Aug 2021 18:07:35 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> When I hover over the major and minor mode names in the mode line, the
> tooltip says "Minor mode" or "Major mode".
>
> It would be useful if it could display the full mode name in the tooltip.
I think so, too. Today those things are just constant strings -- it'd
be nice to be able to add this in a non-consing way (i.e., without
having to create a new big-ish string every time we display the mode
line).
Here's the current code:
`(:propertize ("" mode-name)
help-echo "Major mode\n\
mouse-1: Display major mode menu\n\
mouse-2: Show help for major mode\n\
mouse-3: Toggle minor modes"
mouse-face mode-line-highlight
local-map ,mode-line-major-mode-keymap)
This is quite careful to not create any garbage.
Hm... perhaps we could just make the help-echo point to a function
instead? That should have no performance impact, I think.
'("" mode-line-process)
`(:propertize ("" minor-mode-alist)
mouse-face mode-line-highlight
help-echo "Minor mode\n\
mouse-1: Display minor mode menu\n\
mouse-2: Show help for minor mode\n\
mouse-3: Toggle minor modes"
local-map ,mode-line-minor-mode-keymap)
The minor modes are done in one go, though, so that'd have to be
changed?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-08-22 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 16:07 bug#50147: Wishlist: Display mode name in mode line tooltip Stefan Kangas
2021-08-22 14:46 ` Lars Ingebrigtsen [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=874kbhzgdx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50147@debbugs.gnu.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).