From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Understanding the behaviour of Emacs and Emacs Client
Date: Wed, 23 Feb 2022 14:54:42 +0200 [thread overview]
Message-ID: <831qztu4j1.fsf@gnu.org> (raw)
In-Reply-To: <YhYibRh6cHVTbLTa@protected.localdomain> (message from Jean Louis on Wed, 23 Feb 2022 15:02:53 +0300)
> Date: Wed, 23 Feb 2022 15:02:53 +0300
> From: Jean Louis <bugs@gnu.support>
>
> pkill "emacs --daemon" or other command line you used.
No, just "M-x kill-emacs RET" from the client frame.
Killing the process will lose any unsaved work, will not call the
hooks in the likes of saveplace.el and desktop.el, etc. Not
recommended.
next prev parent reply other threads:[~2022-02-23 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 3:23 Understanding the behaviour of Emacs and Emacs Client Pankaj Jangid
2022-02-23 6:56 ` Jean Louis
2022-02-23 8:41 ` Pankaj Jangid
2022-02-23 12:02 ` Jean Louis
2022-02-23 12:54 ` Eli Zaretskii [this message]
2022-02-23 12:26 ` Eli Zaretskii
2022-02-28 3:29 ` Pankaj Jangid
2022-03-01 16:54 ` Suvayu Ali
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=831qztu4j1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).