unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Claudio Grondi <claudio.grondi@freenet.de>
Cc: 62575@debbugs.gnu.org
Subject: bug#62575: 29.0.60; Tabs are not showing the right names of the buffers
Date: Sat, 01 Apr 2023 08:37:38 +0300	[thread overview]
Message-ID: <83cz4o17tp.fsf@gnu.org> (raw)
In-Reply-To: <7f7b17d6-63e2-d7fc-1091-802f972f9a62@freenet.de> (message from Claudio Grondi on Fri, 31 Mar 2023 23:06:02 +0200)

> Date: Fri, 31 Mar 2023 23:06:02 +0200
> From: Claudio Grondi <claudio.grondi@freenet.de>
> 
> I have switched in between from gtk to lucid observing the mentioned issue.
> 
> See 
> https://emacs.stackexchange.com/questions/76593/bug-or-feature-click-on-tab-does-not-give-the-buffer-with-the-shown-buffer-name

Please always report bugs with all the details included in the
report.  Please do NOT just cite a report posted elsewhere, but
include all the details here.  We want our bug tracker to have all the
information, and do not want to depend on some other site, which may
or may not keep this information for the years to come.

> This should be easy to reproduce, right?

I don't know, because you didn't show the steps for reproducing the
problem, neither here nor on SE.  The description on SE starts in the
middle of a situation without telling how to get to that situation
starting from "emacs -Q".  Can you describe those steps, please?

> Can you reproduce it?

Not if I try to do so naïvely.  Here's what I tried:

  emacs -Q
  M-x tab-bar-mode RET
  click on the "+" to add a new tab
  C-x C-f ~/.emacs RET

Now I have two tabs: one showing "*scratch*", the other showing
".emacs".  Clicking on a tab causes Emacs to display the buffer whose
name is on the tab I click.

Does this mean the problem is not reproduced here?





  reply	other threads:[~2023-04-01  5:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 21:06 bug#62575: 29.0.60; Tabs are not showing the right names of the buffers Claudio Grondi
2023-04-01  5:37 ` Eli Zaretskii [this message]
2023-04-01 11:19   ` Claudio Grondi
2023-04-01 11:38     ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-01 12:28       ` Claudio Grondi
2023-04-01 12:32         ` Eli Zaretskii
2023-04-01 11:55     ` Eli Zaretskii
2023-04-01 14:07     ` Eli Zaretskii
2023-04-02  6:48       ` Juri Linkov
2023-04-02 15:26         ` Claudio Grondi
2023-04-02 16:29           ` Juri Linkov
2023-04-02 21:45             ` Claudio Grondi
2023-04-03  6:30               ` Juri Linkov
2023-04-03 12:37                 ` Claudio Grondi
2023-04-03 16:11                   ` Juri Linkov
2023-04-03 18:06                     ` Claudio Grondi
2023-04-04  6:56                       ` Juri Linkov
2024-05-02 18:12                         ` 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=83cz4o17tp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62575@debbugs.gnu.org \
    --cc=claudio.grondi@freenet.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 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).