From: "Drew Adams" <drew.adams@oracle.com>
To: <sds@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: RE: custom: how do I augment an option?
Date: Wed, 5 Sep 2012 14:27:55 -0700 [thread overview]
Message-ID: <B33EDBC32CE349759A61B811B4CD16CC@us.oracle.com> (raw)
In-Reply-To: <67A2247E25BC41A09BFD76399CE3A03F@us.oracle.com>
> > also see below (sneak preview: customize is broken :-).
>
> Please, don't just tell us here. `M-x report-emacs-bug', if
> you think Emacs code is broken. That's the only real hope
> (however slim it might be in some cases) of getting something fixed.
>
> In all likelihood (my guess), if "customize" does not seem to
> do the right thing in this particular case it is not because
> Customize is broken but because the programmer who coded this
> particular user option did not do the right thing.
> Those are not the same thing. And the devil is in the details.
> So provide the details to Emacs Dev by reporting a bug.
BTW, the doc string and source code comments seem to be an admission that there
are some remaining problems. They suggest that this option is complex and is
not necessarily for most end users to fiddle with. IOW, this is not your
typical option.
In the doc string:
Don't touch this variable unless you really know what you're doing.
In the code comments:
;; Guess this one shouldn't be easy to customize...
...
; Fixme: improve this
next prev parent reply other threads:[~2012-09-05 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 17:56 custom: how do I augment an option? Sam Steingold
2012-09-05 18:27 ` Jambunathan K
2012-09-05 19:18 ` Sam Steingold
2012-09-05 20:04 ` Drew Adams
2012-09-05 20:45 ` Sam Steingold
2012-09-05 21:15 ` Drew Adams
2012-09-05 21:27 ` Drew Adams [this message]
[not found] ` <mailman.8164.1346872698.855.help-gnu-emacs@gnu.org>
2012-09-06 13:14 ` Stefan Monnier
2012-09-06 13:37 ` Drew Adams
2012-09-06 18:20 ` Sam Steingold
2012-10-26 18:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B33EDBC32CE349759A61B811B4CD16CC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sds@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.