all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: brickviking <brickviking@gmail.com>
To: 65277@debbugs.gnu.org
Subject: bug#65277: 29.1.50; emacsclient Dired: frame is closed/killed when opening another dir
Date: Wed, 16 Aug 2023 18:37:59 +1200	[thread overview]
Message-ID: <CAHWye86ekQdhbGfsT8q6usv2Nmk6iPZX7KSE-PD+BVodLOOZJg@mail.gmail.com> (raw)
In-Reply-To: <87350mpkho.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

Further to the above tests from me which were in graphics mode, I also did
the same test with textmode as follows:

shell1$ emacs -Q  # in graphics mode
A frame renders, I then start up the server:
   M-x server-start

That frame stays around.  Going off to another shell, I started an
emacsclient, but this time in text mode.

   shell2$ emacsclient -t GNUmakefile

The terminal is cleared, and the contents of GNUmakefile appear. A buffer
is assigned, as I can tell in C-x C-b in the original server window.

In the minibuffer (of the emacsclient) I then go:
  C-x C-v INSTALL
and the terminal returns to the shell prompt. Interestingly, the contents
of INSTALL then appear in the original emacs server window, and in the
buffer listing, GNUmakefile has been replaced by INSTALL when I refresh the
buffer listing.

My conclusion is that this bug hasn't exactly been "fixed" with the patches
to files.el and server.el, but at least in graphics mode the frame hangs
around instead of the content turning up in the parent frame with the
server running.

Hope that helps,

Regards,
brickviking

[-- Attachment #2: Type: text/html, Size: 1219 bytes --]

  parent reply	other threads:[~2023-08-16  6:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13 23:53 bug#65277: 29.1.50; emacsclient Dired: frame is closed/killed when opening another dir Maxim Kim
2023-08-14 13:37 ` Eli Zaretskii
2023-08-16  2:22 ` brickviking
2023-08-16  6:37 ` brickviking [this message]
2023-08-17  9:44   ` Eli Zaretskii
2023-08-17 19:02     ` Eli Zaretskii
2023-08-18  7:42       ` Eli Zaretskii
     [not found]         ` <CAHWye84OVBfhF+PX7Y9eAWPW=m46TRHHXfp40dKTe4zRGvPsRw@mail.gmail.com>
2023-08-18  8:41           ` bug#65277: Fwd: " brickviking
     [not found]           ` <CAHWye86Vmme-S60+aMgX9aDv9eOd+UX45sCrhPWfS3jiMvqvmw@mail.gmail.com>
2023-08-18  8:42             ` brickviking
2023-08-18 12:10             ` Eli Zaretskii
2023-08-19  0:51               ` brickviking
2023-08-19  7:36                 ` Eli Zaretskii
2023-08-28  1:09                   ` brickviking
2023-08-28 12:21                     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHWye86ekQdhbGfsT8q6usv2Nmk6iPZX7KSE-PD+BVodLOOZJg@mail.gmail.com \
    --to=brickviking@gmail.com \
    --cc=65277@debbugs.gnu.org \
    /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.