From: Alan Mackenzie <acm@muc.de>
Subject: Re: Proposal: emacs -Q option
Date: Thu, 5 Feb 2004 08:33:08 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.3.96.1040205081556.279B-100000@acm.acm> (raw)
In-Reply-To: <ullnirqnf.fsf@elta.co.il>
On 5 Feb 2004, Eli Zaretskii wrote:
>> From: no-spam@cua.dk (Kim F. Storm)
>> Date: 05 Feb 2004 02:42:44 +0100
>> emacs -q --no-site-file --no-splash
>> --eval '(blink-cursor-mode -1)'
>> --eval '(tool-bar-mode -1)'
>> --eval '(scroll-bar-mode -1)'
>> --eval '(tooltip-mode -1)'
>> --eval '(setq visible-bell t)'
>> (the last line is because the audible bell drives me crazy).
>> I propose to add a -Q option which is equivalent to this, i.e.
>> emacs -Q
>> does the same thing as the above call.
>IMHO, using -Q for "-q --no-site-file" is fine, but adding all the other
>turn-offs makes this switch too heavily loaded. Why does it make sense
>to combine "-q --no-site-file", which basically means ``defeat all
>local deviations from the defaults'' with the rest, which disable fancy
>features? And what does visible-bell setting have to do with turning
>off features?
>I'd say let's make two options, one for "-q --no-site-file", the other
>for --no-splash and the --eval options mentioned above, excluding the
>visible-bell one.
I'd say, make a command-line "user option" instead or as well. After
all, Emacs is supposed to be user configurable. Say, -U or -U"string".
This would set a variable `option-U' to the string (or t) before running
.emacs (or, possibly site-start.el?).
So, starting emacs with `emacs -U"v"' could partner up with this in one's
.emacs:
(when option-U
(blink-cursor-mode -1)
(tool-bar-mode -1)
(scroll-bar-mode -1)
(tooltip-mode -1))
(if (equal option-U "v")
(setq visible-bell t))
--
Alan Mackenzie (Munich, Germany)
next prev parent reply other threads:[~2004-02-05 8:33 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 [this message]
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
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=Pine.LNX.3.96.1040205081556.279B-100000@acm.acm \
--to=acm@muc.de \
/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).