Re: force-mode-line-update ALL argument

[martin rudalics]

>> 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