unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <snogglethorpe@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs -Q not documented
Date: Sun, 3 Apr 2005 07:17:21 +0900	[thread overview]
Message-ID: <fc339e4a050402141750a91d0c@mail.gmail.com> (raw)
In-Reply-To: <16974.31697.605551.695664@farnswood.snap.net.nz>

On Apr 2, 2005 8:02 PM, Nick Roberts <nickrob@snap.net.nz> wrote:
> I don't think these are explanatory.
> 
> If we can't think of a suitable name why should we add one?

Well obviously if we can't think of a good name, we shouldn't add a
bad one :-), but long option names, if well-chosen, are often _much_
easier to remember if you only use the option very occasionally...

So it's worth at least a bit of effort to come up with one.  I think
it needn't be _completely_ self-explanatory, as long as it's easy to
remember, and "makes sense" after reading the options documentation or
--help output.  Something like `--vanilla' is probably not going to
indicate to a completely naive user what's going on, but it's almost
certainly meaningful enough[*] to jog the memory of someone who has
read the documentation in the past (whereas -Q is more iffy).

How about `--default-settings' (which could be abbreviated
`--default'; perhaps it ought to also accept the plural of that,
`--defaults', without actually putting it in the option help)?

[*] For a native english speaker -- this is the big problem with
`--vanilla' I think.

-Miles
-- 
Do not taunt Happy Fun Ball.

  reply	other threads:[~2005-04-02 22:17 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29 14:28 emacs -Q not documented Werner LEMBERG
     [not found] ` <E1DH4IQ-00048v-Bw@fencepost.gnu.org>
2005-04-02  6:47   ` Werner LEMBERG
2005-04-02  9:58     ` David Kastrup
2005-04-02 11:02       ` Nick Roberts
2005-04-02 22:17         ` Miles Bader [this message]
2005-04-02 22:47           ` David Kastrup
2005-04-02 22:52           ` Kim F. Storm
2005-04-02 23:00             ` Miles Bader
2005-04-02 23:21               ` Henrik Enberg
2005-04-02 23:37                 ` Miles Bader
2005-04-02 23:45             ` Nick Roberts
2005-04-03 21:20     ` Richard Stallman
2005-04-04 22:12       ` Miles Bader
2005-04-04 22:13       ` Miles Bader
2005-04-05  7:31       ` Kim F. Storm
2005-04-05  9:27         ` Miles Bader
2005-04-05 10:04           ` Kim F. Storm
2005-04-05 10:27             ` Miles Bader
2005-04-05 10:40               ` Miles Bader
2005-04-05 11:16                 ` Kim F. Storm
2005-04-05 13:22         ` Robert J. Chassell
2005-04-05 13:44           ` David Kastrup
2005-04-05 14:05             ` Kim F. Storm
2005-04-05 14:09               ` David Kastrup
2005-04-05 14:44                 ` Kim F. Storm
2005-04-05 14:53                   ` David Kastrup
2005-04-06  3:02         ` Richard Stallman
2005-04-06  7:14           ` Kim F. Storm
2005-04-06  7:48             ` Nick Roberts
2005-04-06 23:02             ` Richard Stallman
2005-04-06  8:45           ` Werner LEMBERG
2005-04-06  9:28             ` Kim F. Storm
2005-04-06  9:47               ` David Kastrup
2005-04-06 10:47                 ` Kim F. Storm
2005-04-06 10:15               ` Andreas Schwab
2005-04-06 11:58                 ` David Kastrup
2005-04-06 13:31                   ` Stefan Monnier

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=fc339e4a050402141750a91d0c@mail.gmail.com \
    --to=snogglethorpe@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=rms@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 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).