From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@elta.co.il>, emacs-devel@gnu.org
Subject: Re: Proposal: emacs -Q option
Date: 07 Feb 2004 18:16:26 -0500 [thread overview]
Message-ID: <jwvwu6ytrph.fsf-monnier+emacs/devel@asado.iro.umontreal.ca> (raw)
In-Reply-To: <87wu6znx3a.fsf@mail.jurta.org>
> --no-shared-memory, -nl (#ifdef HAVE_SHM)
> present in --help
> missing in cmdargs.texi
No clue what this actually does. It should at least be removed from --help
when HAVE_SHM is not defined.
> --map-data, -map (#ifdef VMS)
> missing in --help, cmdargs.texi
> --no-loadup, -nl
> missing in --help, cmdargs.texi
IIRC this is only used for undumped Emacsen. It's "for hackers only".
> --vertical-scroll-bars, -vb
> present in --help
> missing in cmdargs.texi
> --horizontal-scroll-bars, -hb
> missing in --help, cmdargs.texi
I guess they should both be added.
> --line-spacing, -lsp
> present in --help
> missing in cmdargs.texi
Maybe this one as well.
> --smid
> missing in --help, cmdargs.texi
This is used internally by the session-manager code (i.e. X11-specific).
> -psn_ (#ifdef MAC_OSX)
> missing in --help, cmdargs.texi
This looks very "not-for-user".
> --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
I suspect these were X11 specific. Maybe they are also somewhat supported
under other platforms. They should definitely be mentioned in --help and
in the Texinfo doc. Maybe it would be worthwhile to add them to
cmdargs.texi.
This said, I really think the --help text should be generated more
dynamically to match the exact set of args accepted by the executed Emacs.
Stefan
next prev parent reply other threads:[~2004-02-07 23:16 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
2004-02-07 23:16 ` Stefan Monnier [this message]
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=jwvwu6ytrph.fsf-monnier+emacs/devel@asado.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=eliz@elta.co.il \
--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).