all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Carlos Pita <carlosjosepita2@gmail.com>
Cc: 51935@debbugs.gnu.org
Subject: bug#51935: 29.0.50; tab-switch hides identically named tabs
Date: Mon, 22 Nov 2021 20:16:46 +0200	[thread overview]
Message-ID: <86bl2c3vjl.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAEOO5TfC7wXkJuWORpRFv=jrmTgtrhAG5Av6wEq5x3_=7Q97zw@mail.gmail.com> (Carlos Pita's message of "Sat, 20 Nov 2021 00:17:22 -0300")

close 51935 29.0.50
thanks

> Depending on the configured completion framework C-x t RET will show
> candidates in order or not, but the interpretation of the suffix as a
> position seems relatively clear to me even in the unordered case, if
> not anything else at least it's an indication that there are
> additional tabs with the same name.

Actually, not only tab-bar-switch-to-tab has such function signature
that uses the argument NAME, but also other functions such as
tab-bar-close-tab-by-name and tab-bar-rename-tab-by-name.
All they expect a unique name of the tab.  There is no way
to distinguish tabs with the same name.  In practice,
this problem doesn't exist because in this case
the users just rename the tab to a unique name.

To make is more easy to rename the tab, I improved 'C-x t RET' in master
that now it creates a new tab when the provided tab name doesn't exist.
So instead of using 'C-x t 2' to create a new tab, you can use
'C-x t RET new-tab-name RET', exactly in the same way as
'C-x b new-buffer RET' can be used to create a new buffer.





      parent reply	other threads:[~2021-11-22 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18  6:10 bug#51935: 29.0.50; tab-switch hides identically named tabs Carlos Pita
2021-11-18 17:32 ` Juri Linkov
2021-11-19  0:31   ` Carlos Pita
2021-11-19  8:36     ` Juri Linkov
2021-11-20  3:17       ` Carlos Pita
2021-11-20 19:42         ` Juri Linkov
2021-11-22 18:16         ` Juri Linkov [this message]

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=86bl2c3vjl.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=51935@debbugs.gnu.org \
    --cc=carlosjosepita2@gmail.com \
    /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.