unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Igor Epstein <igorepst@gmail.com>
Cc: 59522@debbugs.gnu.org
Subject: bug#59522: 29.0.50; `C-x C-c' on undeleted frame closes Emacs server
Date: Wed, 23 Nov 2022 22:06:58 +0200	[thread overview]
Message-ID: <83sfi9xwnx.fsf@gnu.org> (raw)
In-Reply-To: <CAHsLZBYr-n1CCuF774SwDauFhEmcjKGNyLmuVLPMM9YEqCgMnA@mail.gmail.com> (message from Igor Epstein on Wed, 23 Nov 2022 15:40:32 +0200)

> From: Igor Epstein <igorepst@gmail.com>
> Date: Wed, 23 Nov 2022 15:40:32 +0200
> 
> Hello. There is a sequence of actions that triggers shutting down Emacs
> server when using undelete frame and `C-x C-c' it.
> 1. Start with the following init.el:
> (require 'server)
> (unless (server-running-p) (server-start))
> (undelete-frame-mode)
> 2. In a graphical terminal emulator, run `emacs'
> 3. In another window of a terminal emulator, run `emacsclient -c'
> 4. Ensure the second frame is selected, use `C-x C-c'
> 5. Undelete the frame and again use `C-x C-c' inside the undeleted frame
> 6. Observe that both frames are now closed
> 7. Running `emacsclient -c' produces "can't find socket; have you
> started the server?"

I'm not sure I understand the expectation that the above should not shut
down Emacs.  The first "C-x C-c" doesn't do that because you are typing
this in a client frame.  But when you undelete that frame, Emacs cannot make
it a client frame, because it cannot restore connection to emacsclient.  So
it makes an ordinary frame, and then "C-x C-c" shuts down Emacs.

So I' not sure I see a bug here, perhaps just a surprising behavior.  Bottom
line is that undeleting a frame doesn't restore all frame attributes of that
frame.





  reply	other threads:[~2022-11-23 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 13:40 bug#59522: 29.0.50; `C-x C-c' on undeleted frame closes Emacs server Igor Epstein
2022-11-23 20:06 ` Eli Zaretskii [this message]
2022-11-23 20:37 ` Igor Epstein
2022-11-24  6:24   ` 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=83sfi9xwnx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59522@debbugs.gnu.org \
    --cc=igorepst@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).