all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: brickviking <brickviking@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65277@debbugs.gnu.org
Subject: bug#65277: 29.1.50; emacsclient Dired: frame is closed/killed when opening another dir
Date: Sat, 19 Aug 2023 12:51:13 +1200	[thread overview]
Message-ID: <CAHWye86+iT6zSVcWRd=QgESf0Cbg+=iw=_joTwNxvYbBhfHRwA@mail.gmail.com> (raw)
In-Reply-To: <83bkf44klh.fsf@gnu.org>

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

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.

Regards, brickviking


On Sat, 19 Aug 2023 at 00:10, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: brickviking <brickviking@gmail.com>
> > Date: Fri, 18 Aug 2023 20:22:24 +1200
> >
> > Okay. Patch applied, compiled, installed, executed emacs from shell1.
> > ----- text -----
> >     shell1$ emacs -Q
> > I started server: M-x server-start. Window stays up.
> >
> >     shell2$ emacsclient -t GNUmakefile
> > It then opens with contents of GNUmakefile.
> >
> > I then go C-x C-v INSTALL, hit enter, and get returned back to the
> prompt.
>
> That's not what I see here.  I see INSTALL, and I don't get back to
> the prompt.  If you indeed compiled the latest patch, this is strange.
>
> > The behaviour differs for the GUI client in that I open emacsclient -C
> GNUmakefile after starting the
> > server, and GNUmakefile shows in the window.
> > When I go C-x C-v INSTALL <RET> the emacsclient window closes (and
> returns me to a prompt),
> > and the INSTALL appears in a buffer in the original server window.
>
> That's also not what I see.
>
> I suspect you used one of the previous patches, or maybe didn't
> install the patch correctly.
>
> Thanks.
>

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

  reply	other threads:[~2023-08-19  0:51 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 [this message]
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='CAHWye86+iT6zSVcWRd=QgESf0Cbg+=iw=_joTwNxvYbBhfHRwA@mail.gmail.com' \
    --to=brickviking@gmail.com \
    --cc=65277@debbugs.gnu.org \
    --cc=eliz@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.