From: Patrick Anderson <panderson@altiris.com>
Cc: emacs-devel@gnu.org
Subject: Re: reconsider defaults custom group
Date: 06 Jan 2003 09:30:52 -0700 [thread overview]
Message-ID: <un0meutoj.fsf@altiris.com> (raw)
to clarify:
i was never interested in actually changing the defaults. that may be useful for some of these, but was not my intention.
when it comes to default options the high-level goal for any product should be to satisfy the most people. but some options are chosen equally both directions. that means a default cannot be meaningfully chosen.
that is why i think popular-options.el should always be a part of the editor. a link from the welcome page could say something like "click to edit popularly changed options.". the displayed customization list should be sorted by those options which most equally split the community.
-----Original Message-----
From: Richard Stallman [mailto:rms@gnu.org]
Sent: Sunday, January 05, 2003 8:25 PM
To: alex@emacswiki.org
Cc: kfs@cua.dk; Patrick Anderson; emacs-devel@gnu.org
Subject: Re: reconsider defaults custom group
Some of us are currently discussing a list of options on the wiki; we
will get back to you with a small number of defaults we suggest to
change,
Thanks. It's conceivable I might agree instantly with changing some
options, but more likely I'll want to see arguments in favor of it.
next reply other threads:[~2003-01-06 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 16:30 Patrick Anderson [this message]
2003-01-06 20:50 ` reconsider defaults custom group Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 23:45 Patrick Anderson
2003-01-02 20:36 Patrick Anderson
2003-01-04 0:18 ` Kim F. Storm
2003-01-04 23:44 ` Richard Stallman
2003-01-05 4:03 ` Alex Schroeder
2003-01-06 3:25 ` Richard Stallman
2002-12-25 18:19 Alex Schroeder
2002-12-26 1:22 ` Miles Bader
2002-12-26 23:39 ` Richard Stallman
2003-01-02 20:26 ` patware
2003-01-03 7:50 ` Richard Stallman
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=un0meutoj.fsf@altiris.com \
--to=panderson@altiris.com \
--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).