The minor mode indicators in the modeline are getting to be too many -- and though :lighter for shorter indicators help, I'm still finding them overly heavy to consume --- it's painful to listen to :-) though I suspect they also place a level of cognitive load on users who can that we might be able to reduce. For instance, in programming language modes, I suspect it's increasingly common to have autofill, abbrev, -- perhaps company etc turned on; would be nice if a user could: 1. Define a "logical bundle of minor modes " that are specific to various tasks, and then have a modeline indicater for that "bundle" defined -- so the Modeline would indicate "prog" for the user to know and remember that a preferred set of programming affordances are turned on. Thoghts? -- Thanks, --Raman(I Search, I Find, I Misplace, I Research) ♉ Id: kg:/m/0285kf1 🦮 -- Thanks, --Raman(I Search, I Find, I Misplace, I Research) ♉ Id: kg:/m/0285kf1 🦮
Hi,
> 1. Define a "logical bundle of minor modes " that are specific to
> various tasks, and then have a modeline indicater for that "bundle"
> defined
You forgot to include the link to that package of yours,
Stefan :-)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset=gb18030, Size: 493 bytes --] Stefan Monnier <monnier@iro.umontreal.ca> writes: :-) if you mean emacspeak :-) https://github.com/tvraman/emacspeak > Hi, > >> 1. Define a "logical bundle of minor modes " that are specific to >> various tasks, and then have a modeline indicater for that "bundle" >> defined > > You forgot to include the link to that package of yours, > > > Stefan :-) > -- Thanks, --Raman(I Search, I Find, I Misplace, I Research) 7©4 Id: kg:/m/0285kf1 0Ü8
"T.V Raman" <raman@google.com> writes: > The minor mode indicators in the modeline are getting to be too many > -- and though :lighter for shorter indicators help, I'm still finding > them overly heavy to consume --- it's painful to listen to :-) though > I suspect they also place a level of cognitive load on users who can > that we might be able to reduce. > > For instance, in programming language modes, I suspect it's > increasingly common to have autofill, abbrev, -- perhaps company etc > turned on; would be nice if a user could: > > 1. Define a "logical bundle of minor modes " that are specific to > various tasks, and then have a modeline indicater for that "bundle" > defined -- so the Modeline would indicate "prog" for the user to > know and remember that a preferred set of programming affordances > are turned on. Thoghts? There is the Diminish package in GNU ELPA: https://elpa.gnu.org/packages/diminish.html I don't know if it already supports the "bundling" feature that you propose, or something equivalent.
Daniel Martín <mardani29@yahoo.es> writes:
> "T.V Raman" <raman@google.com> writes:
>
>> The minor mode indicators in the modeline are getting to be too many
>> -- and though :lighter for shorter indicators help, I'm still finding
>> them overly heavy to consume --- it's painful to listen to :-) though
>> I suspect they also place a level of cognitive load on users who can
>> that we might be able to reduce.
>>
>> For instance, in programming language modes, I suspect it's
>> increasingly common to have autofill, abbrev, -- perhaps company etc
>> turned on; would be nice if a user could:
>>
>> 1. Define a "logical bundle of minor modes " that are specific to
>> various tasks, and then have a modeline indicater for that "bundle"
>> defined -- so the Modeline would indicate "prog" for the user to
>> know and remember that a preferred set of programming affordances
>> are turned on. Thoghts?
>
> There is the Diminish package in GNU ELPA:
> https://elpa.gnu.org/packages/diminish.html I don't know if it already
> supports the "bundling" feature that you propose, or something
> equivalent.
AFAIK Diminish (and delight, and rich-minority, and maybe others) simply
let the user redefine (or disable) the lighter for individual minor
modes.
Off the top of my head, if I wanted to implement Raman's proposal today
(as I undertand it) through user code, I guess I'd replace
mode-line-modes in mode-line-format with an :eval form that hrm… runs
through a list of {PRED ↦ LIGHTER} functions, where each PRED is fed (or
looks up) the list of enabled minor modes, and outputs a short LIGHTER
for a logical bundle? E.g.
(defvar my/prog-minor-modes
'(auto-fill-function
abbrev-mode))
(defun my/prog-lighters ()
(and (derived-mode-p 'prog-mode)
(seq-every-p 'identity my/prog-minor-modes)
" prog"))
… and then append my/prog-lighters to another list variable that the
:eval form will go through… hm, it's clearly half-baked (e.g. if any of
the modes are disabled, then the lighter won't be shown, so should
my/prog-lighters fall back to listing all enabled modes? 🤷), and/or
over-engineered.
I'm mostly posting this to see if my understanding of Raman's proposal
is correct.
diminish does do some of what I want, thanks for that pointer. -- Thanks, --Raman(I Search, I Find, I Misplace, I Research) ♉ Id: kg:/m/0285kf1 🦮 -- Thanks, --Raman(I Search, I Find, I Misplace, I Research) ♉ Id: kg:/m/0285kf1 🦮