From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 24949@debbugs.gnu.org
Subject: bug#24949: Command-line argument parsing: named daemons
Date: Wed, 16 Nov 2016 05:39:10 +0200 [thread overview]
Message-ID: <8337isgkkh.fsf@gnu.org> (raw)
In-Reply-To: <05vavopehh.fsf@fencepost.gnu.org> (message from Glenn Morris on Tue, 15 Nov 2016 17:25:46 -0500)
> From: Glenn Morris <rgm@gnu.org>
> Date: Tue, 15 Nov 2016 17:25:46 -0500
>
> Package: emacs
> Severity: minor
I think it should be wishlist.
> This starts a daemon with a server named "FOO":
> emacs -Q --daemon=FOO
>
> (This usage is documented in the "Initial Options" appendix of the
> manual, but not mentioned in --help, or the man page.)
>
>
> But this very similar form does not work (it starts an un-named daemon and
> visits file "FOO"):
> emacs -Q --daemon FOO
>
> Compare with something like "--chdir /tmp", where both forms (with and
> without "=") work.
I wouldn't expect it to work, since long options are documented to
need the equals sign.
> There is a 20-year old comment in emacs.c:
>
> Too bad we can't just use getopt for all of this, but we don't have
> enough information to do it right.
>
> Perhaps standard argument parsing libraries have improved since then...?
I think that comment is not about the parsing libraries, I think it's
about the fact that submitting the information getopt needs is
difficult or impossible in Emacs, given some of our options.
next prev parent reply other threads:[~2016-11-16 3:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 22:25 bug#24949: Command-line argument parsing: named daemons Glenn Morris
2016-11-16 3:39 ` Eli Zaretskii [this message]
2017-09-06 17:33 ` Philipp Stephani
2017-09-06 18:05 ` Eli Zaretskii
2017-09-06 18:32 ` Philipp Stephani
2017-09-07 2:31 ` Eli Zaretskii
2017-09-08 3:46 ` Richard Stallman
2018-01-07 22:44 ` Philipp Stephani
2018-01-08 4:00 ` Eli Zaretskii
2019-05-05 3:59 ` Noam Postavsky
2019-05-05 17:16 ` Philipp Stephani
2018-01-08 8:44 ` Andreas Schwab
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=8337isgkkh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24949@debbugs.gnu.org \
--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.