From: Andreas Schwab <schwab@suse.de>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 24949@debbugs.gnu.org
Subject: bug#24949: Command-line argument parsing: named daemons
Date: Mon, 08 Jan 2018 09:44:23 +0100 [thread overview]
Message-ID: <mvmvagcn3iw.fsf@suse.de> (raw)
In-Reply-To: <CAArVCkTcscNsRL+ZK=2FVTfvBj9CygHieO0wk0QqbPGXeMq+OQ@mail.gmail.com> (Philipp Stephani's message of "Sun, 07 Jan 2018 22:44:26 +0000")
On Jan 07 2018, Philipp Stephani <p.stephani2@gmail.com> wrote:
> I've just re-checked this. The manual states: "When a long option takes an
> argument, you can use either a space or an equal sign to separate the
> option name and the argument. Thus, you can write either
> @samp{--display sugar-bombs:0.0} or @samp{--display=sugar-bombs:0.0}. "
>
> So it's even documented that both forms should work.
That's only true for options with a non-optional argument. For optional
arguments the equal sign is required, otherwise it doesn't know whether
the argument belongs to the option.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2018-01-08 8:44 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
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 [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=mvmvagcn3iw.fsf@suse.de \
--to=schwab@suse.de \
--cc=24949@debbugs.gnu.org \
--cc=p.stephani2@gmail.com \
/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).