From: martin rudalics <rudalics@gmx.at>
To: MON KEY <monkey@sandpframing.com>
Cc: emacs-devel@gnu.org
Subject: Re: force-mode-line-update ALL argument
Date: Sun, 23 May 2010 21:05:05 +0200 [thread overview]
Message-ID: <4BF97C61.9050606@gmx.at> (raw)
In-Reply-To: <AANLkTinn7Jas1om3BYbrcvFgyR2GV9nYlhL_Yf-bMZEx@mail.gmail.com>
>> The entire idea is that `set-buffer' should not have an effect on the
>> mode line, only `set-window-buffer' should.
>
> ,---- (documentation 'window-dedicated-p)
> | Functions like `set-window-buffer' may change the buffer displayed
> | by a window, unless that window is "strongly" dedicated to its
> | buffer, that is the value returned by `window-dedicated-p' is t.
> `----
>
> IIRTC this says that `set-window-buffer' _should_ change display but
> may not be depended upon to _always_ do so esp. when a window has
> `strong' voodoo acting upon it.
How would this relate to the issue at hand?
>> set_buffer_temp doesn't enter here.
>>> {...}
>> record_buffer doesn't enter here either.
>
> Seriously, how can you be sure?
Because I studied the code.
>> in `force-mode-line-update' and the ALL argument has no effect. When
>> {...}
>> argument has been set. Now, usually the current buffer is shown in
>> the selected window, so this went by unnoticed ever since that.
>
> I doubt it has gone unnoticed for 10+ years. More likely no one was
> brave enough to assert that Fset_buffer_modified_p et al cover _all_
> cases.
A "bug" occurs iff you call `force-mode-line-update' in a state where
the current buffer is not shown in any window. Why should anyone want
to do that?
martin
next prev parent reply other threads:[~2010-05-23 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 5:39 force-mode-line-update ALL argument MON KEY
2010-05-22 8:50 ` martin rudalics
2010-05-23 4:29 ` MON KEY
2010-05-23 12:16 ` martin rudalics
2010-05-23 17:14 ` MON KEY
2010-05-23 19:05 ` martin rudalics [this message]
2010-05-25 2:45 ` MON KEY
-- strict thread matches above, loose matches on Subject: below --
2010-05-20 16:53 martin rudalics
2010-05-21 6:42 ` Tassilo Horn
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=4BF97C61.9050606@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=monkey@sandpframing.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).