GNU bug report logs - #76439
[PATCH] Specify 'tab-bar-history-mode' in 'winner-mode' docstring

Previous Next

Full log

View this message in rfc822 format

From: Visuwesh <visuweshm <at> gmail.com>
To: Ship Mints <shipmints <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, stephen.berman <at> gmx.net, 76439 <at> debbugs.gnu.org, rpluim <at> gmail.com, juri <at> linkov.net
Subject: bug#76439: [PATCH] Specify 'tab-bar-history-mode' in 'winner-mode' docstring
Date: Sun, 23 Feb 2025 18:19:03 +0530

This still doesn't say what the anomalous behaviour is, so I am not sure we should use this either.

On 23 February 2025 17:48:22 GMT+05:30, Ship Mints <shipmints <at> gmail.com> wrote:
>On Sun, Feb 23, 2025 at 1:11 AM Visuwesh <visuweshm <at> gmail.com> wrote:
>
>> [வெள்ளி பிப்ரவரி 21, 2025] Ship Mints wrote:
>>
>> > Not sure what it means to "turn" a window configuration.  Perhaps
>> something
>> > like below is simpler and gets the salient point across and adds the key
>> > binding information winner-mode users might find to be helpful
>> > encouragement.
>> >
>> > If you use `tab-bar-mode', consider using `tab-bar-history-mode', as
>> > `winner-mode' is unaware of tab switching, and can confuse `tab-bar'
>> > window configurations.  `tab-bar-history-mode' provides
>> > tab-specific window configuration history, avoiding this problem, and
>> > its default key bindings match those of `winner-mode'.
>>
>> I find "can confuse `tab-bar' window configurations" lacking in detail.
>> If the problem is the verb "turn", what do you think about using
>> "change" or "replace" instead?
>>
>
>How about "`winner-mode' window-configuration histories are tab naive, and
>will produce unexpected results when used with `tab-bar-mode`."

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.