From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 37667@debbugs.gnu.org
Subject: bug#37667: 27.0.50; Tab Bar display problems with more than 5 tabs
Date: Thu, 21 Nov 2019 23:56:10 +0200 [thread overview]
Message-ID: <87pnhkj3lx.fsf@mail.linkov.net> (raw)
In-Reply-To: <6166c73a-2a25-dac4-47c9-5e66e610a57b@gmx.at> (martin rudalics's message of "Thu, 21 Nov 2019 09:23:41 +0100")
> Browser tabs are usually ordered by their creation time which has no
> relationship to what has been actually shown. You can create a new
> browser tab and then remove it without ever visiting the corresponding
> link.
This is exactly how this is already implemented on the tab-bar.
> OTOH a buffer listed in 'window-prev-buffers' has been shown in
> that window at least once. After C-x 2 the new window has just one
> element in that list, the buffer it shows.
The tab-line is used just for buffer selection, so either it can use
the order of buffer-list, or the order of window-prev-buffers, or
alphabetical order. I see no other way to sort buffers.
You mentioned 'creation time' above. Does a buffer have a buffer-local
variable for its creation time? Then we could sort by buffer's
creation time. But currently I see only the variable buffer-display-time,
not buffer-creation-time.
> The (here defunct) tab mix plus had a number of ways to affect the
> (dynamic re-)sorting of tabs including the positioning of a new tab
> wrt the currently active one. Maybe we should try to simulate some of
> their more popular ones here.
Many features of the tab mix plus are already supported on the tab-bar.
next prev parent reply other threads:[~2019-11-21 21:56 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 18:55 bug#37667: 27.0.50; Tab Bar display problems with more than 5 tabs Eli Zaretskii
2019-10-10 22:25 ` Juri Linkov
2019-10-11 7:16 ` Eli Zaretskii
2019-10-13 22:39 ` Juri Linkov
2019-10-14 7:00 ` Eli Zaretskii
2019-10-14 21:47 ` Juri Linkov
2019-10-15 9:09 ` Eli Zaretskii
2019-10-15 18:07 ` Juri Linkov
2019-10-15 18:46 ` Eli Zaretskii
2019-10-15 19:10 ` Eli Zaretskii
2019-10-15 22:39 ` Juri Linkov
2019-10-16 16:51 ` Eli Zaretskii
2019-10-16 22:39 ` Juri Linkov
2019-10-17 7:20 ` Eli Zaretskii
2019-10-17 22:34 ` Juri Linkov
2019-10-18 6:57 ` Eli Zaretskii
2019-10-20 22:28 ` Juri Linkov
2019-10-21 7:58 ` Eli Zaretskii
2019-10-21 22:20 ` Juri Linkov
2019-10-22 15:16 ` Eli Zaretskii
2019-10-22 21:19 ` Juri Linkov
2019-10-23 16:10 ` Eli Zaretskii
2019-10-28 22:38 ` Juri Linkov
2019-10-29 12:01 ` Eli Zaretskii
2019-10-30 0:35 ` Juri Linkov
2019-10-30 15:59 ` Eli Zaretskii
2019-10-30 23:59 ` Juri Linkov
2019-10-31 14:25 ` Eli Zaretskii
2019-10-31 0:03 ` Juri Linkov
2019-10-31 14:30 ` Eli Zaretskii
2019-10-31 20:46 ` Juri Linkov
2019-11-01 7:43 ` Eli Zaretskii
2019-11-02 19:06 ` Juri Linkov
2019-11-02 19:28 ` Eli Zaretskii
2019-11-02 22:36 ` Juri Linkov
2019-11-17 21:44 ` Juri Linkov
2019-11-18 16:18 ` Eli Zaretskii
2019-11-18 21:57 ` Juri Linkov
2019-11-19 16:51 ` Eli Zaretskii
2019-11-19 22:25 ` Juri Linkov
2019-11-20 3:45 ` Eli Zaretskii
2019-11-20 22:40 ` Juri Linkov
2019-11-21 8:23 ` martin rudalics
2019-11-21 14:20 ` Eli Zaretskii
2019-11-21 21:56 ` Juri Linkov [this message]
2019-11-22 8:16 ` martin rudalics
2019-10-11 8:17 ` martin rudalics
2019-10-13 22:31 ` Juri Linkov
2019-10-14 6:51 ` Eli Zaretskii
2019-10-14 20:07 ` Juri Linkov
2019-10-14 20:22 ` Eli Zaretskii
2019-10-14 21:50 ` Juri Linkov
2019-10-15 6:26 ` Eli Zaretskii
2019-10-15 17:54 ` Juri Linkov
2019-10-16 18:14 ` martin rudalics
2019-10-16 20:58 ` Juri Linkov
2019-10-17 8:25 ` martin rudalics
2020-09-20 11:24 ` Lars Ingebrigtsen
2020-09-20 11:27 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnhkj3lx.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=37667@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).