From: Dan Nicolaescu <dann@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 4789@debbugs.gnu.org
Subject: bug#4789: use bootstrap-emacs to build emacs/leim directory, load emacs/leim/leim-list.el to loadup.el
Date: Mon, 18 Jul 2011 02:01:01 -0400 [thread overview]
Message-ID: <yxqtyakqg9u.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <79pql88pwu.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 17 Jul 2011 19:10:09 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Lars Magne Ingebrigtsen wrote:
>
>> Right. Was there any consensus that dumping with leim-list would be a
>> good idea? I read the thread, and I didn't really see any conclusions.
>
> Don't know. FWIW, I think leim/leim-list should be dumped (and therefore
> would need to be built with bootstrap-emacs), and normal-top-level
Or just check in the generated leim-list.el, it almost never changes.
We do something similar with ldefs-boot.el...
next prev parent reply other threads:[~2011-07-18 6:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 16:49 bug#4881: use bootstrap-emacs to build emacs/leim directory, load emacs/leim/leim-list.el to loadup.el Dan Nicolaescu
2011-07-13 14:25 ` bug#4789: " Lars Magne Ingebrigtsen
2011-07-13 17:00 ` Glenn Morris
2011-07-16 19:50 ` Lars Magne Ingebrigtsen
2011-07-16 23:37 ` Glenn Morris
2011-07-17 0:59 ` Lars Magne Ingebrigtsen
2009-10-23 5:26 ` bug#4789: leim-list.el needs to be included in the dumped images Dan Nicolaescu
2011-07-17 23:10 ` bug#4789: use bootstrap-emacs to build emacs/leim directory, load emacs/leim/leim-list.el to loadup.el Glenn Morris
2011-07-18 6:01 ` Dan Nicolaescu [this message]
2012-04-09 7:20 ` Glenn Morris
2012-04-09 7:49 ` Eli Zaretskii
2012-04-09 7:59 ` Glenn Morris
2012-04-09 8:31 ` Eli Zaretskii
2012-04-09 16:34 ` Glenn Morris
2012-04-09 17:09 ` Eli Zaretskii
2012-04-09 17:30 ` Glenn Morris
2012-04-09 17:38 ` Eli Zaretskii
2012-04-10 1:52 ` Stefan Monnier
2012-04-10 6:32 ` Eli Zaretskii
2012-04-10 12:57 ` Stefan Monnier
2013-11-26 1:08 ` Glenn Morris
2011-07-17 7:26 ` Andreas Schwab
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=yxqtyakqg9u.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=4789@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@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).