From: Evgeny Roubinchtein <zhenya1007@gmail.com>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: Glenn Morris <rgm@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 36b9955: Add --new-daemon, which runs in the foreground and does not fork
Date: Wed, 16 Nov 2016 11:24:34 -0500 [thread overview]
Message-ID: <CAGYXaSYriCiCc1sMrtXw=Lx_gO9mTSyZ9W6mXfpcwYj1yWhoqw@mail.gmail.com> (raw)
In-Reply-To: <87polvz9b6.fsf@udel.edu>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
Alternatively alternatively an optional argument to the "--daemon" option
so that, for example "--daemon=foreground" is the no-forking behavior,
whereas plain "--daemon" (for backward compatibility) and
"--daemon=background" (for completeness) are both the forking behavior.
Bikeshedding can be fun. ;-)
On Wed, Nov 16, 2016 at 11:19 AM, Mark Oteiza <mvoteiza@udel.edu> wrote:
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
> >> Add --new-daemon, which runs in the foreground and does not fork
> >
> > Could we have more meaningful names than "old" and "new"?
> > E.g. --fg-daemon and --bg-daemon?
>
> Alternatively, an extra flag simply to indicate not to fork the daemon,
> perhaps -F for emacs.
>
>
[-- Attachment #2: Type: text/html, Size: 1196 bytes --]
next prev parent reply other threads:[~2016-11-16 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161116072925.16550.32364@vcs.savannah.gnu.org>
[not found] ` <20161116072926.098DB220167@vcs.savannah.gnu.org>
2016-11-16 13:12 ` [Emacs-diffs] master 36b9955: Add --new-daemon, which runs in the foreground and does not fork Stefan Monnier
2016-11-16 16:19 ` Mark Oteiza
2016-11-16 16:24 ` Evgeny Roubinchtein [this message]
2016-11-16 18:34 ` Óscar Fuentes
2016-11-18 6:56 ` Glenn Morris
2016-11-18 13:01 ` Stefan Monnier
2016-11-18 17:18 ` John Wiegley
2016-11-18 17:31 ` Eli Zaretskii
2016-11-18 18:44 ` John Wiegley
2016-11-19 16:10 ` Philipp Stephani
2017-05-30 2:24 ` Noam Postavsky
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='CAGYXaSYriCiCc1sMrtXw=Lx_gO9mTSyZ9W6mXfpcwYj1yWhoqw@mail.gmail.com' \
--to=zhenya1007@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=mvoteiza@udel.edu \
--cc=rgm@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.