[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Customizing the mode line
Re: Customizing the mode line
Fri, 30 Oct 2009 09:38:16 -0400
Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)
> Can we make the mode line display more ergonomic, or at least more
I hope so, although I don't know how right now.
> Should I file a "wish-list" bug for this?
Yes, please (such requests have already appeared in the past, actually,
tho it was before the bugtracker, I guess).
> information that is much less important, like
> the percentage of the file before the window start
I indeed never look at it, but I'm uneasy removing it: basically I find
it redundant when you have scrollbars, but in case you don't have
scrollbars (e.g. in a non-GUI terminal) it's not redundant (but I got
so used to using the scrollbars that it never occurs to me to look at
the modeline for that info. Actually, I do look at the mode-line when
I need to figure out "where am I" but then I look at the line number
rather than the percentage).
What do other people think about it?
> I frequently find myself in a situation where the information that's
> important to me is pushed beyond the right edge of the mode line, and
> is thus invisible. Annoyingly, a large part of the real estate of the
> mode line is taken by information that is much less important, like
> the percentage of the file before the window start and the list of
> minor modes in effect. The latter, for example, is quite static in
> any given buffer, so once you saw it for the first time, there's no
> need to continue showing it in such a central place. However, even in
> a C buffer, the mode shown is "C/l Abbrev", which is quite long. And
> when I read mail, I see something like "RMAIL XXXX/YYYY answered,
> deleted"; when replying to mail it's "Mail Fly Abbrev Fill", etc.
> These are very long strings that I don't need to see all the time,
> because they almost never change. But they steal too much precious
I think the major-mode/minor mode display is important, but I agree that
it often takes up a lot of space to display unchanging info. It would
be good to come up with some way to make it more space efficient.
Maybe we could replace "(Mail Fly Abbrev Fill)" with "(Mail..FAF)" and
then expand the FAF to "Fly Abbrev Fill" in a tooltip.
Maybe we should also come up with a scheme to shrink the displayed
buffer-name if it exceeds some number of chars.
> By contrast, dynamic information such as the current time, the system
> load, the battery condition, the mail indicator, the current function
> (when in which-func-mode), etc.
I'd separate which-func-mode from the others because it is
buffer-specific whereas the others are system-global, so the others
really just shouldn't be displayed in each and every mode-line (that's
a waste of very scarce resource).
So there are two problems:
- how/where to display global properties such as time, system load, mail
- how to make sure which-func-mode gets displayed in a visible part of
Another thing we could consider is a generic "make the modeline fit"
feature: after building the complete unshrunk modeline, we look at its
length and if it exceeds the window's width, we shrink it
"intelligently" (e.g. using shrink functions provided via
text-properties on the various parts of the modeline).
> I consider this a bad misfeature. What's more, modifying what's in
> the mode line is not an easy task (unless I'm missing something): it
> boils down to reading bindings.el and manually setting various parts
> of standard-mode-line-* variables to remove or rearrange what is
Yes, modifying the mode-line is a pain. I think it's more important to
improve the default mode-line, but I agree that we also want to make it
easier to customize it.