From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, schwab@linux-m68k.org,
monnier@iro.umontreal.ca, miles@gnu.org
Subject: Re: remove leim/leim-list.el for make bootstrap?
Date: Mon, 23 Mar 2009 12:56:11 +0900 [thread overview]
Message-ID: <E1LlbGl-0000I8-NU@etlken> (raw)
In-Reply-To: <uprgcp6f1.fsf@gnu.org> (message from Eli Zaretskii on Fri, 20 Mar 2009 17:20:34 +0200)
In article <uprgcp6f1.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> Btw, since we remove leim-list.el before updating it, why does
> quail-update-leim-list-file works so hard to remove some parts of it,
> identify garbled lines, etc.? Isn't all that just a waste of cycles?
Because quail-update-leim-list-file is designed to be used
even for a non-empty leim-list.el. That's why its name
contains "update" instead of "create".
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-03-23 3:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 5:00 remove leim/leim-list.el for make bootstrap? Miles Bader
2009-03-20 10:41 ` Eli Zaretskii
2009-03-20 11:39 ` Andreas Schwab
2009-03-20 12:36 ` Eli Zaretskii
2009-03-20 12:50 ` Eli Zaretskii
2009-03-20 13:15 ` Stefan Monnier
2009-03-20 15:20 ` Eli Zaretskii
2009-03-20 20:22 ` Stefan Monnier
2009-03-23 3:56 ` Kenichi Handa [this message]
2009-03-20 13:14 ` Andreas Schwab
2009-03-20 15:13 ` Eli Zaretskii
2009-03-20 15:46 ` Andreas Schwab
2009-03-20 18:08 ` Eli Zaretskii
2009-03-20 18:47 ` Andreas Schwab
2009-03-20 21:05 ` Eli Zaretskii
2009-03-23 2:51 ` Kenichi Handa
2009-03-23 4:18 ` Eli Zaretskii
2009-03-23 6:07 ` Kenichi Handa
2009-03-20 16:13 ` Stefan Monnier
2009-03-23 2:47 ` Kenichi Handa
2009-03-23 3:12 ` Miles Bader
2009-03-23 4:19 ` Eli Zaretskii
2009-03-23 4:16 ` Eli Zaretskii
2009-03-27 7:02 ` Kenichi Handa
2009-03-27 8:42 ` Eli Zaretskii
2009-03-20 21:43 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LlbGl-0000I8-NU@etlken \
--to=handa@m17n.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.