From: Miles Bader <miles@lsi.nec.co.jp>
Cc: "Kim F. Storm" <storm@cua.dk>
Subject: Re: eval-after-load as a macro (and eval-next-after-load)
Date: 09 Apr 2003 11:31:24 +0900 [thread overview]
Message-ID: <buok7e4766b.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <E1934s0-00056O-00@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> It could be useful to clean up the way Custom handles hooks. For
> instance, if Custom sees elements in the hook that it did not put
> there, it could automatically divide the elements into two parts:
> those specified thru Custom, and those specified outside Custom.
> The user, in Custom, would edit only the former.
This sounds good; but I think if it does this, it should also at least
display the `non-custom' hooks in some way, so that the user can see
the whole value.
-Miles
--
`To alcohol! The cause of, and solution to,
all of life's problems' --Homer J. Simpson
next prev parent reply other threads:[~2003-04-09 2:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 20:30 eval-after-load as a macro (and eval-next-after-load) Stefan Monnier
2003-04-05 8:13 ` Richard Stallman
2003-04-06 21:05 ` Stefan Monnier
2003-04-07 9:25 ` Kai Großjohann
2003-04-07 9:33 ` Miles Bader
2003-04-07 12:50 ` Luc Teirlinck
2003-04-07 13:36 ` Kai Großjohann
2003-04-07 19:05 ` Luc Teirlinck
2003-04-07 19:43 ` Kai Großjohann
2003-04-07 20:04 ` Luc Teirlinck
2003-04-07 20:19 ` Kai Großjohann
2003-04-07 19:35 ` Luc Teirlinck
2003-04-08 2:31 ` Richard Stallman
2003-04-08 10:46 ` Kim F. Storm
2003-04-08 10:21 ` Kai Großjohann
2003-04-08 18:17 ` Stefan Monnier
2003-04-09 23:41 ` Kim F. Storm
2003-04-09 1:59 ` Richard Stallman
2003-04-09 2:31 ` Miles Bader [this message]
2003-04-10 0:00 ` Kim F. Storm
2003-04-10 22:47 ` Richard Stallman
2003-04-07 17:04 ` Juanma Barranquero
2003-04-07 17:56 ` Stefan Monnier
2003-04-07 19:50 ` Juanma Barranquero
2003-04-08 2:31 ` Richard Stallman
2003-04-13 18:55 ` Juanma Barranquero
2003-04-14 7:10 ` Juanma Barranquero
2003-04-05 15:57 ` Kai Großjohann
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=buok7e4766b.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=miles@gnu.org \
--cc=storm@cua.dk \
/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).