From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs -Q not documented
Date: Tue, 05 Apr 2005 23:02:41 -0400 [thread overview]
Message-ID: <E1DJ0oT-0001Xc-Cc@fencepost.gnu.org> (raw)
In-Reply-To: <m3sm25ptlp.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
It is intended to be an option turn off all "extra features".
On what criterion are these features "extra"?
But most important, running emacs -Q when debugging redisplay problems
makes it much easier to know what's going on.
Why does the blinking cursor relate to this?
Just because we cannot find a long name for it -- that's silly, IMO!
The difficulty in finding a long name for it reflected a lack of
apparent coherence of the functionality of the option. Nobody
could see what it was good for. That is why I thought of removing
it or changing it.
next prev parent reply other threads:[~2005-04-06 3:02 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
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 [this message]
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=E1DJ0oT-0001Xc-Cc@fencepost.gnu.org \
--to=rms@gnu.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).