unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thomas Hisch <thomas.hisch@ims.co.at>
Cc: 30934@debbugs.gnu.org
Subject: bug#30934: 27.0.50; Emacsclient process in the terminal does not finish
Date: Sun, 25 Mar 2018 18:22:12 +0300	[thread overview]
Message-ID: <83efk8goyj.fsf@gnu.org> (raw)
In-Reply-To: <29725ed7-a016-7f9a-aac5-de883f43bbdb@ims.co.at> (message from Thomas Hisch on Sun, 25 Mar 2018 13:38:50 +0200)

> From: Thomas Hisch <thomas.hisch@ims.co.at>
> Date: Sun, 25 Mar 2018 13:38:50 +0200
> 
> 
> I have an emacs daemon running (started using emacs --daemon) and want
> to open files on the commandline with emacsclient. I would expect the
> emacsclient command to open the file in an existing frame and return
> immediately. However, emacsclient outputs the "Waiting for Emacs..."
> message and does not return immediately. Is this intended

Yes.

> and what does this message mean if the file is opened in an existing
> frame?

It means emacsclient is waiting for the server to indicate that
editing of the file is done.  This is for programs which invoke an
editor, let the user edit some text, then continue processing that
text after the user finishes editing it.

> There is a --no-wait command line arg, whose help text is "Don't wait
> for the server to return". To me it seems like this should not be used,
> but maybe I'm wrong. Anyway, -n does what I want, but the help text was
> not clear to me.

The --no-wait option is exactly what you want.  If you can explain
what was unclear about it in the help text, perhaps we could clarify
that.

Thanks.





  reply	other threads:[~2018-03-25 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-25 11:38 bug#30934: 27.0.50; Emacsclient process in the terminal does not finish Thomas Hisch
2018-03-25 15:22 ` Eli Zaretskii [this message]
2018-03-25 23:27   ` Thomas Hisch
2018-03-26 15:01     ` 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=83efk8goyj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30934@debbugs.gnu.org \
    --cc=thomas.hisch@ims.co.at \
    /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).