From: Eli Zaretskii <eliz@gnu.org>
To: Rehan Deen <rehan.deen@gmail.com>
Cc: 54331@debbugs.gnu.org
Subject: bug#54331: 27.2; Closing frames loaded from desktop-read
Date: Thu, 10 Mar 2022 22:09:40 +0200 [thread overview]
Message-ID: <83r179d0xn.fsf@gnu.org> (raw)
In-Reply-To: <87h785k5ro.fsf@gmail.com> (message from Rehan Deen on Fri, 11 Mar 2022 00:13:23 +0530)
> From: Rehan Deen <rehan.deen@gmail.com>
> Date: Fri, 11 Mar 2022 00:13:23 +0530
>
> A very annoying issue with `desktop-save` and `desktop-read` that I'm encountering at the moment:
>
> - I'm starting Emacs in `daemon-mode`, and then open a client frame via
> my WM shortcut for `emacsclient -c`. I do `desktop-read` and my saved desktop opens with the 10 or so frames I had saved.
>
> - When I go to one of the frames with a buffer I'm no longer interested in, and do `C-x C-c`, I end up not just closing that particular frame, but **all 10 or so of the frames that were open**.
>
> - The Emacs daemon is still running, and opening another client frame shows that the buffers haven't been killed, so nothing has been lost per se - it's just that the arrangement of all the frames I had is just ruined.
>
> Any idea how to stop this behaviour (i.e. being able to just kill one frame from the saved configuration)?
Is this really related to desktop-read? AFAIK, "C-x C-c" deletes all
the frames displayed on the terminal, and I see the same behavior if I
start a daemon, invoke emacsclient to open a frame, and then make
several other frames from the same session. "C-x C-c" then closes all
the frames I made.
I think this is the expected behavior. What am I missing?
next prev parent reply other threads:[~2022-03-10 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 18:43 bug#54331: 27.2; Closing frames loaded from desktop-read Rehan Deen
2022-03-10 20:09 ` Eli Zaretskii [this message]
2022-03-11 6:53 ` Rehan Deen
2022-03-11 11:39 ` Eli Zaretskii
2022-03-12 18:00 ` Lars Ingebrigtsen
2022-03-12 18:15 ` Eli Zaretskii
2022-03-13 5:55 ` Rehan Deen
2022-03-13 6:06 ` Eli Zaretskii
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=83r179d0xn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54331@debbugs.gnu.org \
--cc=rehan.deen@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 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).