unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs -Q not documented
Date: Wed, 06 Apr 2005 11:47:45 +0200	[thread overview]
Message-ID: <x54qeki6da.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3u0mk9rur.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Wed, 06 Apr 2005 11:28:28 +0200")

storm@cua.dk (Kim F. Storm) writes:

> Werner LEMBERG <wl@gnu.org> writes:
>
>> Well, -Q has definitely its merits, especially for reporting bugs.
>> After seeing this discussion I still think that my `--bare' proposal
>> is not that bad: The -Q options really strips off all features you
>> would normally like to have for daily work.
>
> Yes, --bare-bones or --no-frills seem like good candidates, too.

--bare-bones seems ok.  But things like menus are not "frills", and we
don't want to spread that impression.  I don't want to get bug reports
from people that did not bother using the help menu or tutorial
announced on the splash screen because they decided from the manual
page that they were not the type of person interested in frills.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-04-06  9:47 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
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 [this message]
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=x54qeki6da.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@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).