From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal: emacs -Q option
Date: Sat, 07 Feb 2004 09:54:33 +0200 [thread overview]
Message-ID: <87wu6znx3a.fsf@mail.jurta.org> (raw)
In-Reply-To: <9003-Thu05Feb2004211456+0200-eliz@elta.co.il> (Eli Zaretskii's message of "Thu, 05 Feb 2004 21:14:56 +0200")
"Eli Zaretskii" <eliz@elta.co.il> writes:
> I think the proper places for this are the text printed by "emacs --help"
> and cmdargs.texi. Of these, the latter one lags behind the code
> because Emacs developers are not required to submit documentation
> changes together with code changes. Usually, when a new Emacs
> release is about to enter the pretest phase, we go through NEWS
> entries and update the docs accordingly.
>
> As for the fact that emacs.c doesn't mention some of the new options,
> it's probably a bug, unless, for some good reasons, we don't want to
> advertise them.
I looked more closely at available command line arguments and can't
decide what to do with some of them because of their unclear status:
what arguments are obsolete, what are not implemented, what are
secret developers-only options, what are too platform-dependent
and so shouldn't be known to users?
--no-shared-memory, -nl (#ifdef HAVE_SHM)
present in --help
missing in cmdargs.texi
--map-data, -map (#ifdef VMS)
missing in --help, cmdargs.texi
--no-loadup, -nl
missing in --help, cmdargs.texi
--vertical-scroll-bars, -vb
present in --help
missing in cmdargs.texi
--horizontal-scroll-bars, -hb
missing in --help, cmdargs.texi
--line-spacing, -lsp
present in --help
missing in cmdargs.texi
--smid
missing in --help, cmdargs.texi
-psn_ (#ifdef MAC_OSX)
missing in --help, cmdargs.texi
--name
present in --help
missing in cmdargs.texi, although documented in xresources.texi
--xrm
present in --help
missing in cmdargs.texi, although documented in xresources.texi
--
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-02-07 7:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 1:42 Proposal: emacs -Q option Kim F. Storm
2004-02-05 1:26 ` Miles Bader
2004-02-05 6:23 ` Eli Zaretskii
2004-02-05 8:33 ` Alan Mackenzie
2004-02-05 9:43 ` Kai Grossjohann
2004-02-05 11:53 ` Jan D.
2004-02-05 12:41 ` Kim F. Storm
2004-02-05 12:09 ` Andreas Schwab
2004-02-05 15:08 ` Kim F. Storm
2004-02-05 14:57 ` Stefan Monnier
2004-02-05 7:28 ` Juri Linkov
2004-02-09 10:46 ` Juri Linkov
2004-02-05 7:29 ` Juri Linkov
2004-02-05 19:14 ` Eli Zaretskii
2004-02-05 19:53 ` Stefan Monnier
2004-02-07 7:54 ` Juri Linkov [this message]
2004-02-07 23:16 ` Stefan Monnier
2004-02-08 0:20 ` Steven Tamm
2004-02-08 7:19 ` Juri Linkov
2004-02-08 16:56 ` Stefan Monnier
2004-02-09 7:59 ` Juri Linkov
2004-02-09 8:29 ` Miles Bader
2004-02-09 9:04 ` Juri Linkov
2004-02-09 9:22 ` Miles Bader
2004-02-10 9:46 ` Richard Stallman
2004-02-09 9:38 ` Richard Stallman
2004-02-08 15:21 ` Richard Stallman
2004-02-06 13:42 ` Richard Stallman
2004-02-08 7:12 ` Juri Linkov
2004-02-09 9:38 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 8:42 Bill Wohler
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=87wu6znx3a.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@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).