unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Martín" <mardani29@yahoo.es>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: Thought: Group Minor Modes Into Logical "Bundles"?
Date: Thu, 24 Nov 2022 10:42:08 +0100	[thread overview]
Message-ID: <m1mt8g7kpb.fsf@yahoo.es> (raw)
In-Reply-To: <p91leo1avqt.fsf@google.com> (T. V. Raman's message of "Wed, 23 Nov 2022 19:15:22 -0800")

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



  parent reply	other threads:[~2022-11-24  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  3:15 Thought: Group Minor Modes Into Logical "Bundles"? T.V Raman
2022-11-24  3:21 ` Stefan Monnier
2022-11-24  4:54   ` T.V Raman
2022-11-24  9:42 ` Daniel Martín [this message]
2022-11-25  8:51   ` Kévin Le Gouguec
2022-11-25 15:09   ` T.V Raman

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=m1mt8g7kpb.fsf@yahoo.es \
    --to=mardani29@yahoo.es \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.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).