From: Juri Linkov <juri@linkov.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 57848@debbugs.gnu.org
Subject: bug#57848: 29.0.50; Problems with private tab-line-tab-name-function
Date: Sun, 18 Dec 2022 10:40:53 +0200 [thread overview]
Message-ID: <86v8m99iw2.fsf@mail.linkov.net> (raw)
In-Reply-To: <87tu1teckd.fsf@web.de> (Michael Heerdegen's message of "Sun, 18 Dec 2022 02:16:18 +0100")
>> By default the tab line displays tabs in the same order as buffers
>> in the window buffer list. So switching to the next/previous buffer
>> with 'C-x left/right' also switches the tab in the same direction.
>>
>> But then tabs don't correspond to the window buffers then there is
>> no key to switch to the next/previous tab.
>
> That's the reason why you want to couple those things? Isn't it better
> to simply provide separate keys for the tab line? We already have
> separate commands (`tab-line-switch-to-prev-tab',
> `tab-line-switch-to-next-tab').
>
> I must say I don't understand your reasoning behind what you say.
> Binding those two commands to keys was the one of the first things I did
> when setting up my tab-line. Maybe you are using the tab-line very
> differently from how I do.
The hardest problem is to find free keys where these commands could be bound.
Maybe 'C-c TAB' and 'C-c S-TAB' like used for the tab-bar.
next prev parent reply other threads:[~2022-12-18 8:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 4:39 bug#57848: 29.0.50; Problems with private tab-line-tab-name-function Michael Heerdegen
2022-10-30 7:24 ` Juri Linkov
2022-10-30 12:02 ` Michael Heerdegen
2022-10-30 17:39 ` Juri Linkov
2022-10-31 8:58 ` Michael Heerdegen
2022-11-09 2:07 ` Michael Heerdegen
2022-11-09 7:41 ` Juri Linkov
2022-11-12 1:52 ` Michael Heerdegen
2022-11-12 18:19 ` Juri Linkov
2022-11-13 17:58 ` Juri Linkov
2022-11-14 3:49 ` Michael Heerdegen
2022-11-14 7:47 ` Juri Linkov
2022-11-15 3:43 ` Michael Heerdegen
2022-12-15 17:16 ` Juri Linkov
2022-12-17 7:35 ` Michael Heerdegen
2022-12-17 17:44 ` Juri Linkov
2022-12-18 1:16 ` Michael Heerdegen
2022-12-18 8:40 ` Juri Linkov [this message]
2023-01-10 14:06 ` Michael Heerdegen
2023-01-10 17:44 ` Juri Linkov
2022-11-18 11:49 ` Michael Heerdegen
2022-11-09 7:39 ` Juri Linkov
2022-11-09 23:30 ` Michael Heerdegen
2022-11-10 18:36 ` Juri Linkov
2022-11-12 2:44 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86v8m99iw2.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=57848@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.