From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: customize-apropos
Date: Tue, 13 Dec 2005 20:13:59 -0600 (CST) [thread overview]
Message-ID: <200512140213.jBE2Dxu17342@raven.dms.auburn.edu> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICKEDDDAAA.drew.adams@oracle.com>
Drew Adams wrote:
I probably shouldn't jump in here, but that text tells me nothing,
except to stay away from the option in question.
That is what it tells you _if_ you do not know what you are doing.
What else do you believe people should be doing if they did not
_deliberately_ want to override the usual Custom safeguards, but got
to see these options by accident (presumably through a bug)?
If this is truly dangerous, then we shouldn't show it.
By default, we do not show it.
If this is truly dangerous, then we shouldn't show it.
It is not necessarily dangerous if you know what you are doing.
Sincerely,
Luc.
next prev parent reply other threads:[~2005-12-14 2:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 3:47 customize-apropos Luc Teirlinck
2005-12-10 3:51 ` customize-apropos Luc Teirlinck
2005-12-10 23:04 ` customize-apropos Kim F. Storm
2005-12-10 23:07 ` customize-apropos Luc Teirlinck
2005-12-11 16:49 ` customize-apropos Richard M. Stallman
2005-12-11 5:03 ` customize-apropos Richard M. Stallman
2005-12-11 17:57 ` customize-apropos Drew Adams
2005-12-12 5:03 ` customize-apropos Luc Teirlinck
2005-12-12 5:40 ` customize-apropos Drew Adams
2005-12-12 23:56 ` customize-apropos Luc Teirlinck
2005-12-13 0:22 ` customize-apropos Drew Adams
2005-12-13 0:45 ` customize-apropos Luc Teirlinck
2005-12-13 3:55 ` customize-apropos Drew Adams
2005-12-13 1:01 ` customize-apropos Luc Teirlinck
2005-12-13 1:29 ` customize-apropos Luc Teirlinck
2005-12-13 23:33 ` customize-apropos Richard M. Stallman
2005-12-14 1:14 ` customize-apropos Luc Teirlinck
2005-12-14 1:25 ` customize-apropos Drew Adams
2005-12-14 2:13 ` Luc Teirlinck [this message]
2005-12-14 3:20 ` customize-apropos Drew Adams
2005-12-14 3:40 ` customize-apropos Luc Teirlinck
2005-12-14 3:52 ` customize-apropos Drew Adams
2005-12-14 5:58 ` customize-apropos Luc Teirlinck
2005-12-14 15:07 ` customize-apropos Drew Adams
2005-12-15 5:33 ` customize-apropos Luc Teirlinck
2005-12-15 16:33 ` customize-apropos Drew Adams
2005-12-16 5:09 ` customize-apropos Richard M. Stallman
2005-12-14 3:45 ` customize-apropos Luc Teirlinck
2005-12-14 3:54 ` customize-apropos Drew Adams
2005-12-14 20:02 ` customize-apropos Richard M. Stallman
2005-12-15 4:18 ` customize-apropos Luc Teirlinck
2005-12-16 1:51 ` customize-apropos Richard M. Stallman
2005-12-16 3:47 ` customize-apropos Luc Teirlinck
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=200512140213.jBE2Dxu17342@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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).