From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Understanding the behaviour of Emacs and Emacs Client
Date: Tue, 1 Mar 2022 16:54:35 +0000 [thread overview]
Message-ID: <CAMXnza3=iL__iELusgGir7GQcHtQR9kQV6UY8M60N25nPMEXyw@mail.gmail.com> (raw)
In-Reply-To: <87czj7wtx3.fsf@codeisgreat.org>
On Mon, Feb 28, 2022 at 3:29 AM Pankaj Jangid <pankaj@codeisgreat.org> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> And if Yes then what is the official way to terminate the residual
> >> Emacs process in case (2) above?
> >
> > The official way is to type "M-x kill-emacs RET". (But in general, if
> > you use the "client" icon, the assumption is that you don't want to do
> > that. rather, leave the Emacs process running and use the client icon
> > to open a new frame next time you want to do something in Emacs --
> > this way, you keep all the history and the buffers inside the
> > session, and the startup will be faster.)
>
> Thanks for the explanation, Eli. The only time I would want to do that
> is when I am shutting down or rebooting the system for some reason. I
> want to cleanly exit and save all work. "M-x kill-emacs RET" certainly
> helps.
>
> Customization var like "kill-emacs-with-last-frame" could be a good
> idea. Or "C-x C-c" on last frame may be used to default to this
> behaviour; this will prevent any lost work due to reboot or
> shutdown. Because the daemon is invisible after last frame. Just an
> idea. "C-x 5 0" remains the same.
I use the following:
emacsclient --eval "(save-some-buffers t)" --eval "(kill-emacs)"
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2022-03-01 16: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
2022-02-23 12:26 ` Eli Zaretskii
2022-02-28 3:29 ` Pankaj Jangid
2022-03-01 16:54 ` Suvayu Ali [this message]
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='CAMXnza3=iL__iELusgGir7GQcHtQR9kQV6UY8M60N25nPMEXyw@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--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).