all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-diffs Digest, Vol 67, Issue 11
Date: Wed, 04 Jun 2008 09:40:45 +0900	[thread overview]
Message-ID: <E1K3h3V-0006NC-Cb@etlken.m17n.org> (raw)
In-Reply-To: <ud4mycr9h.fsf@gnu.org> (message from Eli Zaretskii on Tue, 03 Jun 2008 21:22:50 +0300)

In article <ud4mycr9h.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> > Date: Tue, 03 Jun 2008 03:42:09 -0400
> > From: emacs-diffs-request@gnu.org
> > 
> > +2008-06-03  Kenichi Handa  <handa@m17n.org>
> > +
> > +	* makefile.w32-in (KOREAN): Remove ${srcdir}/quail/hangul3.elc.
> > +	(leim-list.el): Remove leim-list.el at first.
> > +
> > +	* Makefile.in (KOREAN): Remove ${srcdir}/quail/hangul3.elc.
> > +	(leim-list.el): Remove leim-list.el at first.

> Handa-san, could you please tell why it is necessary to remove
> leim-list.el?  The commands after that run the function
> update-leim-list-file, so I assume that it can update an existing
> file, it doesn't need to rebuild it from scratch.

The target leim-list.el depends on leim-ext.el, and we do
this at the end:

	sed -n '/^[^;]/ p' < ${srcdir}/leim-ext.el >> $@

So, when you modify leim-ext.el, leim-list.el is re-build,
but, if we don't remove leim-list.el at first, the contents
of leim-ext.el are duplicated.

In addition, update-leim-list-file works a little bit faster
when leim-list.el is vacant.

Do you actually find any problem with this change?

---
Kenichi Handa
handa@ni.aist.go.jp




  reply	other threads:[~2008-06-04  0:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1K3R9v-0003nH-Nh@monty-python.gnu.org>
2008-06-03 18:22 ` Emacs-diffs Digest, Vol 67, Issue 11 Eli Zaretskii
2008-06-04  0:40   ` Kenichi Handa [this message]
2008-06-04  3:21     ` Eli Zaretskii
2008-06-04  5:02       ` Kenichi Handa

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=E1K3h3V-0006NC-Cb@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=eliz@gnu.org \
    --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 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.