all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 24949@debbugs.gnu.org
Subject: bug#24949: Command-line argument parsing: named daemons
Date: Wed, 06 Sep 2017 21:05:22 +0300	[thread overview]
Message-ID: <83efrj1z4t.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkSCs9ca4k84gew9hA9ws2Pwhe22F-Wf9YQ0oxfZQ+kSzQ@mail.gmail.com> (message from Philipp Stephani on Wed, 06 Sep 2017 17:33:33 +0000)

> X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_50,
> 	FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,T_DKIM_INVALID
> 	autolearn=disabled version=3.3.2
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Wed, 06 Sep 2017 17:33:33 +0000
> Cc: 24949@debbugs.gnu.org
> 
>  > 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.
> 
> This is incredibly surprising and also inconsistent with the man page, which doesn't have equals signs for
> most options. Let's just document what everybody expects, i.e. that all options work with and without equals
> sign, and with one or two dashes. 

Why would we want to do that?  Documentation should describe the
software, not our wishes.  If we want to change how the software
works, we should change the code first, and only after that change the
documentation.  Am I missing something here?





  reply	other threads:[~2017-09-06 18:05 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 [this message]
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=83efrj1z4t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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 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.