Subject: bug#73027: Fwd: 31.0.50; tab-bar-formal-global erased global-modeline-string's mouse hover/click action menu

From: Juri Linkov <[email-masked]>
Date: Tue, 24 Sep 2024 09:43:04 +0300

close 73027 30.0.60
stop

>> >> The problem is that the mode-line keymap can't be used without
>> >> replacing the symbol 'mode-line' with 'tab-bar'.
>> >
>> > Should we close this bug with the above workaround?  Or would we like
>> > to solve it in some other way?
>>
>> Do you think it would be a good idea to inspect text properties
>> on the mode-line strings when they are displayed on the tab-bar,
>> and change the symbol 'mode-line' to 'tab-bar' in the 'keymap'
>> property on the fly?
>
> Sounds kludgey, TBH.  Besides, I'm not even sure this could be done
> reliably, since mode-line-format could be very recursive.

Indeed, this can't be done reliably.  Moreover, this can even cause
performance degradation when using :eval such as

  '(:eval (mu4e--modeline-string))

when such a kludge should be applied every time the tab-bar is updated.

So this is closed now with the recommendation to add
the symbol 'tab-bar' alongside 'mode-line' in
the package-specific 'mu4e--modeline-string'.