From: "Richard M. Stallman" <rms@gnu.org>
Cc: mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: mh-e/mh-acros.el advices `require' incorrectly
Date: Sun, 15 Jan 2006 18:07:19 -0500 [thread overview]
Message-ID: <E1EyGxz-0005Ws-Uq@fencepost.gnu.org> (raw)
In-Reply-To: <87vewmifds.fsf@olgas.newt.com> (message from Bill Wohler on Sat, 14 Jan 2006 15:00:47 -0800)
What do people think about my updating lisp/Makefile.in to remove
lisp/mh-e/*.elc if and only if lisp/mh-e/*.el changes?
That won't help with M-x byte-recompile. The right solution is to
make the graph of requires acyclic, and put the macro file at the
start of the alphabet. Given the way the software in fact works,
that should be totally reliable.
next prev parent reply other threads:[~2006-01-15 23:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87oe2gez38.fsf@olgas.newt.com>
2006-01-13 21:04 ` mh-e/mh-acros.el advices `require' incorrectly Drew Adams
2006-01-13 22:11 ` Bill Wohler
2006-01-13 23:36 ` Satyaki Das
2006-01-14 1:39 ` Bill Wohler
2006-01-14 0:29 ` Kenichi Handa
2006-01-14 16:14 ` Richard M. Stallman
2006-01-14 23:00 ` Bill Wohler
2006-01-14 23:16 ` Andreas Schwab
2006-01-15 0:26 ` Bill Wohler
2006-01-15 2:22 ` Stefan Monnier
2006-01-15 23:07 ` Richard M. Stallman [this message]
2006-01-16 1:29 ` Bill Wohler
2006-01-17 3:24 ` Richard M. Stallman
2006-01-17 4:20 ` Bill Wohler
2006-01-17 9:18 ` David Kastrup
2006-01-17 17:19 ` Bill Wohler
2006-01-29 19:22 ` MH-E reorg (was: mh-e/mh-acros.el advices `require' incorrectly) Bill Wohler
2006-01-29 21:10 ` MH-E reorg Bill Wohler
2006-01-30 18:45 ` MH-E reorg (was: mh-e/mh-acros.el advices `require' incorrectly) Richard M. Stallman
2006-01-30 19:24 ` Bill Wohler
2006-01-13 7:49 mh-e/mh-acros.el advices `require' incorrectly Kenichi Handa
2006-01-13 18:56 ` Bill Wohler
2006-01-13 21:45 ` Stefan Monnier
2006-01-14 2:52 ` Bill Wohler
2006-01-14 16:14 ` Richard M. Stallman
2006-01-14 17:47 ` Stefan Monnier
2006-01-14 5:49 ` Richard M. Stallman
2006-01-14 8:25 ` Bill Wohler
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=E1EyGxz-0005Ws-Uq@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mh-e-devel@lists.sourceforge.net \
/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).