From: Eli Zaretskii <eliz@gnu.org>
To: Claudio Grondi <claudio.grondi@freenet.de>
Cc: ruijie@netyu.xyz, 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 15:32:36 +0300 [thread overview]
Message-ID: <835yafzst7.fsf@gnu.org> (raw)
In-Reply-To: <98caff99-1890-cf9e-9b49-7f4882c89caa@freenet.de> (message from Claudio Grondi on Sat, 1 Apr 2023 14:28:14 +0200)
> Date: Sat, 1 Apr 2023 14:28:14 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, 62575@debbugs.gnu.org
> From: Claudio Grondi <claudio.grondi@freenet.de>
>
>
> Along with this I have also noticed following problem:
>
> 1. ~ $ emacs -Q
> 2. Menu -> Options -> Show/Hide -> Tab Bar (gives Tab *scratch*)
> 3. resize the Emacs window to a small one, but large enough to show some Tab labels
> 3. 1x click on rightmost * in the Tab Bar to create a new Tab
>
> The bug: No new Tab will be created and the minibuf and *Messages* show:
>
> split-window: Window #<window 3 on *Messages*> too small for splitting
>
> Is it worth a new bug number?
Yes, please.
next prev parent reply other threads:[~2023-04-01 12:32 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835yafzst7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62575@debbugs.gnu.org \
--cc=claudio.grondi@freenet.de \
--cc=ruijie@netyu.xyz \
/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.