GNU bug report logs - #14957
24.3.50; Flyspell language visible in mode line

Previous Next

Full log

Message #59 received at 14957 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: Sebastien Vauban <sva-news <at> mygooglest.com>, 14957 <at> debbugs.gnu.org
Subject: Re: bug#14957: 24.3.50; Flyspell language visible in mode line
Date: Fri, 18 Sep 2020 17:10:53 +0200

Michael Heerdegen <michael_heerdegen <at> web.de> writes:

> Lars Ingebrigtsen <larsi <at> 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?

The language could be put in the mode-line-process position, which is
ahead of the modes:

  ...  [br]  (Text Fly Fill)

>> 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.

I haven't looked at how minor mode lighters are constructed -- if we can
use any old mode line constructs, then it should be fine.  I.e., instead
of

(propertize "Fly" ...)

it'd be

(,(propertize "Fly" ...) ,(propertize "[br]"...))

> 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.

I didn't consider that use case, but that should be easy enough to
achieve.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.