unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: carlmarcos--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 56215@debbugs.gnu.org
Subject: bug#56215: Request for decluttering capability on mode-line keywords
Date: Sat, 25 Jun 2022 15:08:52 +0200 (CEST)	[thread overview]
Message-ID: <N5PyfPq--3-2@tutanota.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]


The mode-line is a very important section of a window.  But can be easily cluttered withnames of minor-modes, as well as by programming and hypertext language major-mode names.

For instance, loading an elisp file shows "Emacs-Lisp" in the made-line.  When in *scratch* the string "Lisp Interaction" shows up.  Because I use bold large font, it is easy for the mode-line to get cluttered.

As is often the case, emacs users hardly change the mode associated with the corresponding programming or hypertext language major-mode.  Most often, users work with minor-modes, meaning that people are aware that lisp programs use emacs-lisp major-mode, and C users are aware they are using c major-mode (although I find "C/*l" quite unnecessary).
Emacs package designers have the ability to display a mode-line name with the keyword-arg `:lighter'.  But the user has no way to remove the lighter from the mode-line.  Would like to request the capability for users to remove :lighter keywords, if they wish.  This would be particularly useful for those like me who usually have a dense list showing up in their mode-line.

[-- Attachment #2: Type: text/html, Size: 1467 bytes --]

             reply	other threads:[~2022-06-25 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25 13:08 carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-26  0:05 ` bug#56215: Request for decluttering capability on mode-line keywords Phil Sainty
2022-06-26 14:56   ` Lars Ingebrigtsen
2022-07-01 16:38     ` Howard Melman
     [not found]   ` <87sfnreamy.fsf@gnus.org-N5VW6WZ--3-2>
2022-06-26 15:09     ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found] ` <0c7b006177f251663dfa0f0e0d1e7344@webmail.orcon.net.nz-N5SKEQ_----2>
2022-06-26  8:34   ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-26  9:28     ` Phil Sainty
2022-06-26 10:48       ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-26 20:59         ` Phil Sainty
     [not found]       ` <N5Uc10f--3-2@tutanota.com-N5UcM5i----2>
2022-06-26 14:07         ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-08 15:57 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=N5PyfPq--3-2@tutanota.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56215@debbugs.gnu.org \
    --cc=carlmarcos@tutanota.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).