From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Sebastien Vauban <sva-news@mygooglest.com>, 14957@debbugs.gnu.org
Subject: bug#14957: 24.3.50; Flyspell language visible in mode line
Date: Fri, 18 Sep 2020 17:00:19 +0200 [thread overview]
Message-ID: <87bli3xh8c.fsf@web.de> (raw)
In-Reply-To: <87v9gbf9rf.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 18 Sep 2020 16:19:00 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Perhaps putting it in the Flyspell lighter? So it'd be
>
> ... (Text Fly[br] Fill)
Yes, I think so. What's a reasonable alternative at all?
> I'm not sure whether that's possible with the mode line machinery,
> though -- we want clicking on "Fly" to switch the mode off, but
> clicking on "[br]" to allow changing the dictionary.
That should be possible I think. Ideally, the part with the clickable
language would be factored as a separately usable mode-line element so
that people who don't want to have all minor modes in the mode-line
still can take advantage of something built-in.
Michael.
next prev parent reply other threads:[~2020-09-18 15:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 12:59 bug#14957: 24.3.50; Flyspell language visible in mode line Sebastien Vauban
2013-07-26 14:21 ` Stefan Monnier
2013-09-17 16:47 ` Michael Heerdegen
[not found] ` <87wqmfz96x.fsf-S0/GAf8tV78@public.gmane.org>
2013-11-08 20:46 ` Sebastien Vauban
2013-11-08 21:30 ` Michael Heerdegen
2020-09-18 14:19 ` Lars Ingebrigtsen
2020-09-18 15:00 ` Michael Heerdegen [this message]
2020-09-18 15:10 ` Lars Ingebrigtsen
2020-09-18 15:45 ` Eli Zaretskii
2020-09-19 14:01 ` Lars Ingebrigtsen
2020-09-19 14:43 ` Eli Zaretskii
2020-09-19 22:31 ` Michael Heerdegen
2020-09-19 22:34 ` Lars Ingebrigtsen
2020-09-18 16:17 ` Michael Heerdegen
[not found] ` <mailman.5609.1383955137.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.5609.1383955137.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-11-12 13:29 ` Sebastien Vauban
2013-11-14 0:03 ` Michael Heerdegen
[not found] ` <mailman.6021.1384387520.10748.bug-gnu-emacs@gnu.org>
2013-11-14 10:41 ` Sebastien Vauban
2013-11-14 19:05 ` Stefan Monnier
2014-01-14 8:58 ` Sebastien Vauban
2014-01-14 15:31 ` Michael Heerdegen
2014-01-14 17:04 ` Glenn Morris
[not found] ` <mailman.11900.1389713605.10748.bug-gnu-emacs@gnu.org>
2014-01-14 17:32 ` Sebastien Vauban
2014-01-14 21:33 ` Stefan Monnier
2014-01-15 13:44 ` Michael Heerdegen
2014-01-15 15:23 ` Stefan Monnier
[not found] ` <mailman.11946.1389735261.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.11946.1389735261.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-01-15 10:13 ` Sebastien Vauban
[not found] ` <mailman.11900.1389713605.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-01-14 18:12 ` Sebastien Vauban
[not found] ` <mailman.11912.1389719107.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.11912.1389719107.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-01-15 10:42 ` Sebastien Vauban
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=87bli3xh8c.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=14957@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=sva-news@mygooglest.com \
/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).