From: Eli Zaretskii <eliz@gnu.org>
To: brickviking <brickviking@gmail.com>
Cc: 65277-done@debbugs.gnu.org
Subject: bug#65277: 29.1.50; emacsclient Dired: frame is closed/killed when opening another dir
Date: Sat, 19 Aug 2023 10:36:08 +0300 [thread overview]
Message-ID: <83edjz1o2f.fsf@gnu.org> (raw)
In-Reply-To: <CAHWye86+iT6zSVcWRd=QgESf0Cbg+=iw=_joTwNxvYbBhfHRwA@mail.gmail.com> (message from brickviking on Sat, 19 Aug 2023 12:51:13 +1200)
> From: brickviking <brickviking@gmail.com>
> Date: Sat, 19 Aug 2023 12:51:13 +1200
> Cc: 65277@debbugs.gnu.org
>
> Yes, sorry about that. I missed an error when retrieving the patch from the email. This altered the
> patch so that one of the hunks didn't succeed (I missed an initial space off the bottom comment line
> of the patch).
>
> I've corrected the patch on my end and done some more testing. Configured, patched, compiled and
> installed.
>
> ---- text ----
> shell1$ emacs -Q
>
> M-x server-mode
> Starts as per normal, window stays up.
>
> shell2$ emacsclient -t GNUmakefile
>
> This opens a text window with the contents of GNUmakefile.
> C-x C-v INSTALL
> INSTALL now opens in the buffer, and I can use it as normal. Trying to
> shut the client down with C-x # results in the message
> "No server buffers remain to edit"
> (not client buffers as you said will happen) so I just did C-x 5 0 to terminate the client.
>
> ---- GUI ----
> Starting up a GUI client with emacsclient -c GNUmakefile shows that file in the window.
> C-x C-v INSTALL
> then shows the install file, and crucially, the terminal doesn't return to the shell prompt. I still see
> "Waiting for Emacs..." in the terminal until I exit the client window.
>
> At least on my end, this appears to work as advertised.
Thanks. So I've now installed the fix on the master branch, and I'm
closing this bug.
next prev parent reply other threads:[~2023-08-19 7:36 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
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 [this message]
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=83edjz1o2f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65277-done@debbugs.gnu.org \
--cc=brickviking@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 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.