From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Thuna <thuna.cing@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Keep global-mode-string on its own "modeline"?
Date: Sat, 29 Oct 2022 11:20:27 -0400 [thread overview]
Message-ID: <jwvzgdehd7n.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87czabzmuk.fsf@gmail.com> (Thuna's message of "Fri, 28 Oct 2022 22:58:59 +0200")
> There is no good reason for `global-mode-string' to be displayed in
> every single window's modeline separately, it takes a lot of space, and
> it usually ends up not completely showing when the window is split more
> than once.
Indeed, we moved it to the end of the mode-line because it ended up
hiding more important info :-)
As to where to put it, it's kind of tricky since Emacs doesn't have much
single place where to put such a thing.
https://elpa.gnu.org/packages/minibuffer-line.html is an attempt to use
the echo area for that.
It has many shortcomings, IIRC, and would probably benefit from some
love, but you might want to try it out, both to discover its limits and
to see whether it hypothetically could be a good approach if we could
fix some of its shortcomings.
Stefan
next prev parent reply other threads:[~2022-10-29 15:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 20:58 Keep global-mode-string on its own "modeline"? Thuna
2022-10-29 6:59 ` Eli Zaretskii
2022-10-29 11:08 ` Thuna
2022-10-29 12:38 ` Eli Zaretskii
2022-10-29 13:05 ` Thuna
2022-10-29 13:40 ` Eli Zaretskii
2022-10-29 13:55 ` Thuna
2022-10-29 15:13 ` Eli Zaretskii
2022-10-29 15:20 ` Thuna
2022-10-29 15:22 ` Eli Zaretskii
2022-10-29 15:26 ` Thuna
2022-10-29 16:07 ` John Yates
2022-10-29 17:49 ` Óscar Fuentes
2022-10-29 7:04 ` Akib Azmain Turja
2022-10-29 15:20 ` Stefan Monnier [this message]
2022-10-30 5:47 ` Akib Azmain Turja
2022-10-29 15:43 ` Philip Kaludercic
[not found] ` <87leoya8xw.fsf@gmail.com>
[not found] ` <87a65epp04.fsf@posteo.net>
2022-10-29 16:41 ` Thuna
2022-10-29 16:27 ` Visuwesh
2022-10-30 8:01 ` Manuel Giraud
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvzgdehd7n.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=thuna.cing@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.