GNU bug report logs - #32850
27.0.50; window-swap-states doesn't swap window prev/next-buffers

Previous Next

Full log

Message #181 received at 32850 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 32850 <at> debbugs.gnu.org
Subject: Re: bug#32850: 27.0.50;
 window-swap-states doesn't swap window prev/next-buffers
Date: Wed, 14 Nov 2018 01:43:15 +0200

>> The x-tabs branch is for X-based builds, and the gtk-tabs branch
>> that Jan implemented is for GTK-based builds.  Both are for the
>> frame-local tab-bars and can't be used for window-local tab-bars.
>> Do you know a solution for window-local tab-bars other than
>> duplicating header-line in each window to provide shelter for tab-bars?
>
> Mine uses atomic windows.

I thought side windows, no?

> But window-local tab-bars are not really useful for displaying window
> configurations anyway

Yes, they are not useful for window configurations, but
window-local tab-bars are extremely useful for displaying
the list of prev/next buffers as tabs.  So the user can see
the names of all buffers that were displayed in the window,
and clicking on the tab will switch to any of previously
displayed buffers.  And clicking on [x] will remove the
buffer from the list of previous window-local buffers.

> (just like mode-lines are not suited for displaying the battery charge
> IMHO).

I agree, mode-lines duplicate the battery charge information
in every window.  What do you think about creating the frame-local
mode-line using the bottom side window?

> Anyway, the problem with an X-based solution is that we would have to
> find a solution for non-X-based systems.  How "much" X-dependency does
> x-tabs have?

The same X-dependency as the tool-bar uses, and there is no tool-bar
on non-X-based systems.

Previous Next

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