unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Carlos Pita <carlosjosepita2@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 51935@debbugs.gnu.org
Subject: bug#51935: 29.0.50; tab-switch hides identically named tabs
Date: Thu, 18 Nov 2021 21:31:45 -0300	[thread overview]
Message-ID: <CAEOO5TdBztSdx0Q8dgd0skepOKB5xz+TeQzMDk5pF=Qb80DR0A@mail.gmail.com> (raw)
In-Reply-To: <86r1bdxvt8.fsf@mail.linkov.net>

Hi Juri,

> How adding a numeric suffix in completions of tab-switch (C-x t RET)
> could help to disambiguate the tabs?  If there will be such automatically
> generated completions as "same-buffer<1>", "same-buffer<2>", "same-buffer<3>",
> there is no way for users to distinguish these tabs.

Tabs are positional so the position can be used to disambiguate
choices. I would use it as a suffix but only where it helps
disambiguate options.

That said, I believe even "same-buffer<1>", "same-buffer<2>",
"same-buffer<3>" is preferable to nothing, first because it's the same
in tab-switcher, tabs are all named equal and it's only the position
that distinguishes them, adding a sequential number conveys the same
information than the position in the tab-switcher menu, so if that's
good for one case it's likely good for the other one as well, at least
as long as it doesn't make completion cumbersome, which is the case
when it's a suffix sparingly added; second, because as it is today one
gets the impression that tabs are missing, it can get pretty
confusing, more confusing than arbitrary suffixes I would say. Notice that I
don't use the tabbar (and I believe I'm not alone in that respect) so I rely
on the tab list to get an overall picture every now and then, sometimes to
figure out what tabs need renaming.

Best regards,
Carlos





  reply	other threads:[~2021-11-19  0:31 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 [this message]
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

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='CAEOO5TdBztSdx0Q8dgd0skepOKB5xz+TeQzMDk5pF=Qb80DR0A@mail.gmail.com' \
    --to=carlosjosepita2@gmail.com \
    --cc=51935@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).