From: David Kastrup <dak@gnu.org>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: Strange eval-after-load
Date: Mon, 03 Jul 2006 12:21:45 +0200 [thread overview]
Message-ID: <85ac7rouo6.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20060703105727.GA2626@muc.de> (Alan Mackenzie's message of "Mon, 3 Jul 2006 11:57:28 +0100")
Alan Mackenzie <acm@muc.de> writes:
> Morning, Richard!
>
> On Sun, Jul 02, 2006 at 06:30:55PM -0400, Richard Stallman wrote:
>> > Starting immediately, please do NOT install calls to eval-after-load
>> > in Emacs without asking for my specific approval.
>>
>> I would beg you not to be so dogmatic.
>
>> This rule is the only way to get control over the situation.
>
> I don't really understand what the situation is over which control has
> to be got. It is possible to to use eval-after-load badly, just as it
> is possible to use goto badly. That's a far cry from demonstrating that
> all e-a-l's/goto's are bad.
What about "asking for my specific approval" did you not understand?
That's a far cry from claiming that all e-a-l's/goto's are bad.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-07-03 10:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 2:22 Strange eval-after-load Richard Stallman
2006-05-26 7:59 ` Eli Zaretskii
2006-05-26 14:20 ` Luc Teirlinck
2006-05-26 19:32 ` Eli Zaretskii
2006-05-27 3:36 ` Richard Stallman
2006-07-02 13:33 ` Hi, I'm back! + " Alan Mackenzie
2006-07-02 17:28 ` Thien-Thi Nguyen
2006-07-02 19:18 ` Alan Mackenzie
2006-07-03 15:05 ` Richard Stallman
2006-07-03 17:16 ` Alan Mackenzie
2006-07-03 16:28 ` Michael Albinus
2006-07-03 17:06 ` John Paul Wallington
2006-07-03 21:54 ` Alan Mackenzie
2006-07-03 21:48 ` Johan Bockgård
2006-07-04 12:54 ` Richard Stallman
2006-07-04 15:02 ` Alan Mackenzie
2006-07-04 20:52 ` Richard Stallman
2006-07-04 21:41 ` Bob Rogers
2006-07-05 16:38 ` Stuart D. Herring
2006-07-05 17:01 ` Richard Stallman
2006-07-02 22:30 ` Hi, I'm back! + " Richard Stallman
2006-07-03 10:57 ` Alan Mackenzie
2006-07-03 10:21 ` David Kastrup [this message]
2006-07-03 13:50 ` Alan Mackenzie
2006-07-03 23:21 ` Richard Stallman
2006-07-04 8:02 ` Alan Mackenzie
2006-07-04 7:15 ` David Kastrup
2006-07-04 10:04 ` Alan Mackenzie
2006-07-04 9:23 ` David Kastrup
2006-07-04 10:00 ` Nick Roberts
2006-07-04 13:08 ` Johan Bockgård
2006-07-04 14:17 ` Thien-Thi Nguyen
2006-07-04 17:30 ` Richard Stallman
2006-07-04 21:08 ` Alan Mackenzie
2006-07-04 21:48 ` Nick Roberts
2006-07-05 3:20 ` Eli Zaretskii
2006-07-05 8:57 ` Alan Mackenzie
2006-07-05 9:09 ` David Kastrup
2006-07-05 22:28 ` Alan Mackenzie
2006-07-06 6:49 ` David Kastrup
2006-07-07 4:14 ` Richard Stallman
2006-07-07 11:46 ` Alan Mackenzie
2006-07-05 17:02 ` Richard Stallman
2006-07-05 14:51 ` Richard Stallman
2006-07-05 18:01 ` Alan Mackenzie
2006-07-03 23:21 ` Richard Stallman
2006-07-03 23:21 ` 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=85ac7rouo6.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).