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: Robert Pluim <rpluim <at> gmail.com>
To: Ship Mints <shipmints <at> gmail.com>
Cc: juri <at> linkov.net, Eli Zaretskii <eliz <at> gnu.org>, stephen.berman <at> gmx.net, 76439 <at> debbugs.gnu.org, Visuwesh <visuweshm <at> gmail.com>
Subject: bug#76439: [PATCH] Specify 'tab-bar-history-mode' in 'winner-mode' docstring
Date: Sun, 23 Feb 2025 13:59:19 +0100

>>>>> On Sun, 23 Feb 2025 07:18:22 -0500, Ship Mints <shipmints <at> gmail.com> said:

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

    Ship> How about "`winner-mode' window-configuration histories are tab naive, and
    Ship> will produce unexpected results when used with `tab-bar-mode`."

Iʼd say "are not aware of tabs", just to avoid us discussing whether
itʼs "tab naive", "tab naïve", "tab-naive", or "tab-naïve" 🙂

Robert
-- 

Previous Next

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