From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: obsolete comment in tool-bar.el
Date: Fri, 15 Jul 2005 14:10:48 -0400 [thread overview]
Message-ID: <E1DtUe8-0003Ce-Eq@fencepost.gnu.org> (raw)
In-Reply-To: <200507150324.j6F3OmC12530@raven.dms.auburn.edu> (message from Luc Teirlinck on Thu, 14 Jul 2005 22:24:48 -0500 (CDT))
More precisely, without my changes, if you specify an explicit
:initialize keyword, the expansion of the define-minor-mode form
contains two :initialize keywords, first
":initialize 'custom-initialize-default" and then, at some later place
the explicit :initialize.
That's not clean, and it might not be clear which one would "win".
So it is better to keep your code, and pass just one :initialize.
However, explicitly
specified :set or :type keywords still expand to defcustoms with two
:set or :type keywords.
It would be cleaner to do the same thing for :set and :type--to suppress
the default one when there is an explicit one.
next prev parent reply other threads:[~2005-07-15 18:10 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 12:40 obsolete comment in tool-bar.el Mathias Dahl
2005-07-07 19:15 ` Luc Teirlinck
2005-07-08 6:40 ` Mathias Dahl
2005-07-08 15:29 ` Luc Teirlinck
2005-07-08 17:40 ` Richard M. Stallman
2005-07-08 18:53 ` Drew Adams
2005-07-09 1:53 ` Luc Teirlinck
2005-07-09 4:20 ` Richard M. Stallman
2005-07-09 2:35 ` Luc Teirlinck
2005-07-10 5:19 ` Richard M. Stallman
2005-07-11 3:21 ` Luc Teirlinck
2005-07-11 16:53 ` Richard M. Stallman
2005-07-11 17:56 ` David Kastrup
2005-07-11 20:28 ` Luc Teirlinck
2005-07-12 3:20 ` Richard M. Stallman
2005-07-13 3:02 ` Luc Teirlinck
2005-07-13 16:52 ` Richard M. Stallman
2005-07-14 2:08 ` Luc Teirlinck
2005-07-14 8:14 ` YAMAMOTO Mitsuharu
2005-07-14 16:50 ` Luc Teirlinck
2005-07-14 18:30 ` Luc Teirlinck
2005-07-15 4:35 ` Stefan Monnier
2005-07-15 13:53 ` Luc Teirlinck
2005-07-15 20:44 ` Stefan Monnier
2005-07-15 22:05 ` Luc Teirlinck
2005-07-15 22:46 ` Luc Teirlinck
2005-07-16 1:47 ` Luc Teirlinck
2005-07-16 2:04 ` Luc Teirlinck
2005-07-19 2:59 ` Luc Teirlinck
2005-07-19 14:41 ` Stefan Monnier
2005-07-20 4:05 ` Luc Teirlinck
2005-07-21 5:40 ` Stefan Monnier
2005-07-20 8:34 ` Richard M. Stallman
[not found] ` <E1Dt8bd-0001fH-Eu@fencepost.gnu.org>
2005-07-14 22:05 ` Luc Teirlinck
2005-07-15 3:24 ` Luc Teirlinck
2005-07-15 18:10 ` Richard M. Stallman [this message]
2005-07-16 2:32 ` Luc Teirlinck
2005-07-13 3:20 ` Luc Teirlinck
2005-07-09 3:57 ` Luc Teirlinck
2005-07-09 7:55 ` Eli Zaretskii
2005-07-09 13:57 ` Luc Teirlinck
2005-07-12 4:13 ` YAMAMOTO Mitsuharu
2005-07-12 12:20 ` YAMAMOTO Mitsuharu
2005-07-12 18:25 ` Luc Teirlinck
2005-07-12 23:58 ` Luc Teirlinck
2005-07-13 16:52 ` Richard M. Stallman
2005-07-12 20:19 ` Luc Teirlinck
2005-07-13 1:53 ` 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=E1DtUe8-0003Ce-Eq@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).