From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: Progress: eshell-defgroup. Do we really need this?
Date: Fri, 1 Aug 2008 16:10:45 +0000 [thread overview]
Message-ID: <20080801161045.GC13919@muc.de> (raw)
In-Reply-To: <20080729222754.GC2208@muc.de>
Hi, Emacs!
On Tue, Jul 29, 2008 at 10:27:54PM +0000, Alan Mackenzie wrote:
> Hi, emacs,
> So back to 'make bootstrap'. It says "can't find eshell-defgroup".
make bootstrap is generating loaddefs.el with lines like
(eshell-defgroup eshell-alias nil "Docstring" :tag "Command aliases" :gr\oup 'eshell-module)
, and AFTER them the line which should have come first:
(defalias 'eshell-defgroup 'defgroup)
. It seems that the loaddefs.el generator first builds these
(eshell-defgroup....) lines in eshell/esh-group.el, and then, somehow,
copies them to loaddefs.el. The code isn't easy to understand.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2008-08-01 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:27 eshell-defgroup. Do we really need this? Alan Mackenzie
2008-07-31 19:17 ` Ted Zlatanov
2008-07-31 19:18 ` Lennart Borgman (gmail)
2008-08-01 15:34 ` Ted Zlatanov
2008-08-01 17:08 ` Romain Francoise
2008-08-01 20:30 ` Ted Zlatanov
2008-08-02 4:18 ` Stephen J. Turnbull
2008-08-04 16:34 ` Ted Zlatanov
2008-08-04 17:49 ` Stephen J. Turnbull
2008-08-04 18:38 ` Ted Zlatanov
2008-08-05 8:20 ` Stephen J. Turnbull
2008-08-05 13:57 ` buildbots (was: eshell-defgroup. Do we really need this?) Ted Zlatanov
2008-08-05 20:25 ` Stephen J. Turnbull
2008-08-08 15:26 ` place to send build failure reports? (was: buildbots) Ted Zlatanov
2008-08-08 15:58 ` place to send build failure reports? Chong Yidong
2008-08-03 19:02 ` eshell-defgroup. Do we really need this? Romain Francoise
2008-08-04 16:31 ` Ted Zlatanov
2008-08-01 16:10 ` Alan Mackenzie [this message]
2008-08-07 19:25 ` Progress: " 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
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=20080801161045.GC13919@muc.de \
--to=acm@muc.de \
--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).