unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ljung <lars@matholka.se>
Cc: 52019@debbugs.gnu.org
Subject: bug#52019: 28.0.60; tab-bar is not updated when buffer is killed
Date: Mon, 22 Nov 2021 20:30:30 +0200	[thread overview]
Message-ID: <86lf1g11ru.fsf@mail.linkov.net> (raw)
In-Reply-To: <86h7c5shqm.fsf@mail.linkov.net> (Juri Linkov's message of "Sun,  21 Nov 2021 19:30:13 +0200")

tags 52019 wontfix
close 52019 29.0.50
quit

>> The name of that tab will be updated when you switch to it.
>
> Ideally, the tab should show some placeholder for the killed buffer
> after the user switches to it, so the tab name should keep its
> original name.  This would less confusing than showing some random
> buffer instead of the killed buffer.  But this is a separate feature
> that could be discussed in a separate request.

The same problem exists with all other uses of window-configuration.
One example: the desktop saves all windows with their buffers.
If a file was deleted before restoring the desktop,
or a buffer saved to the desktop was non-persistent,
then the desktop just deletes the window where the old buffer
was displayed, or replaces the old buffer in the window
with some other random buffer.  This loses the window layout
carefully created by the user.

So instead of replacing the name of the killed buffer
in the tab name with some other random buffer name,
a more proper solution is to keep some placeholder
in the window where the buffer was displayed.
This is a bigger task, so a new request could be created
to implement it.





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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-21 13:33 bug#52019: 28.0.60; tab-bar is not updated when buffer is killed Lars Ljung
2021-11-21 17:30 ` Juri Linkov
2021-11-22 18:30   ` 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

  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=86lf1g11ru.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=52019@debbugs.gnu.org \
    --cc=lars@matholka.se \
    /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).