From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 12872@debbugs.gnu.org
Subject: bug#12872: 24.2; Provide a feature to trigger mode-line redisplay
Date: Tue, 13 Nov 2012 07:38:45 -0800 [thread overview]
Message-ID: <147CB8FB2F7B4B83A18C26B553085D76@us.oracle.com> (raw)
In-Reply-To: <83vcdaupbs.fsf@gnu.org>
> > I wonder (without being very familiar with the mode-line
> > %-constructs, so maybe speaking nonsense) whether it might be
> > useful to add specific %-constructs (or variables?) that say
> > when (i.e., in what contexts) to trigger mode-line redisplay.
>
> What would be the advantages of such a feature? Since the mode line
> format is not even consulted in order to decide whether or not to
> redisplay the mode line (because its processing is very non-trivial,
> what with all the propertize stuff and Lisp expressions going on there
> even in the standard value), we will need internal variables to shadow
> these constructs anyway.
>
> Having variables or maybe a plist of the mode line format allows
> easier access to this information, and is IMO more Lispy than hiding
> the information in some % magic.
I agree that (local) variables make more sense than %-constructs. That was part
of my suggestion. I don't know much about how these things work.
Even from my point of view, ignoring what I didn't know, including the reasons
you gave, variables make more sense, because we are not replacing the
%-construct with anything, in context - IOW, the positions of the new
%-constructs in `mode-line-format' would be irrelevant.
Consider my suggestion to be just to have some easy way to specify mode-line
redisplay triggering conditions, so users can easily separate triggering from
the mode-line format/content.
So for the case that motivated this, you would be able to separate the two %l
effects: triggering and line-# content.
Having different variables (or plist keywords) to specify different triggering
contexts would be one way.
[Someone else might prefer that we come up with a single monster variable a la
`buffer-display-alist' ;-).]
next prev parent reply other threads:[~2012-11-13 15:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 18:27 bug#12872: 24.2; Provide a feature to trigger mode-line redisplay Eli Zaretskii
2012-11-12 19:46 ` Eli Zaretskii
2012-11-12 22:17 ` Drew Adams
2012-11-13 3:57 ` Eli Zaretskii
2012-11-13 15:38 ` Drew Adams [this message]
2021-12-04 4:46 ` Lars Ingebrigtsen
2021-12-04 7:54 ` Eli Zaretskii
2021-12-04 18:55 ` Lars Ingebrigtsen
2021-12-04 19:26 ` Eli Zaretskii
2021-12-04 19:40 ` Lars Ingebrigtsen
2021-12-04 19:43 ` Eli Zaretskii
2021-12-04 22:04 ` Lars Ingebrigtsen
2021-12-05 7:02 ` Eli Zaretskii
2021-12-05 20:05 ` Lars Ingebrigtsen
2021-12-05 20:14 ` Eli Zaretskii
2021-12-06 6:00 ` Lars Ingebrigtsen
2021-12-06 13:02 ` Eli Zaretskii
2021-12-07 20:49 ` Lars Ingebrigtsen
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=147CB8FB2F7B4B83A18C26B553085D76@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12872@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).