unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: phst@google.com, eliz@gnu.org, eggert@cs.ucla.edu,
	p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: [PATCH] Use recommended long options syntax in man page
Date: Thu, 11 Jan 2018 14:51:30 -0500	[thread overview]
Message-ID: <E1eZiss-0008T6-0R@fencepost.gnu.org> (raw)
In-Reply-To: <CAPM58ojEOgG5d_mOLRbHmkXKjqv4cr_mA+Xh-OtfNEPWaD=8tg@mail.gmail.com> (message from Richard Copley on Wed, 10 Jan 2018 19:26:54 +0000)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Both arguments have merit. Manuals aren't just for newbies. Maybe
  > there's room to introduce the syntax with the = first, then elaborate
  > explaining the actual syntax in full. Or maybe that level of detail is
  > best left for the TexInfo manual.

Please use = for long option arguments in the man page.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.




  reply	other threads:[~2018-01-11 19:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 23:12 [PATCH] Use recommended long options syntax in man page Philipp Stephani
2018-01-08  0:43 ` Paul Eggert
2018-01-09  2:51   ` Richard Stallman
2018-01-09  7:30     ` Paul Eggert
2018-01-09 17:24       ` Eli Zaretskii
2018-01-09 22:21         ` Paul Eggert
2018-01-10  3:36           ` Eli Zaretskii
2018-01-10 19:26             ` Richard Copley
2018-01-11 19:51               ` Richard Stallman [this message]
2018-01-17 22:33                 ` Philipp Stephani
2018-01-10  3:03       ` Richard Stallman
2018-01-08  4:08 ` Eli Zaretskii

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=E1eZiss-0008T6-0R@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=p.stephani2@gmail.com \
    --cc=phst@google.com \
    --cc=rcopley@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).