unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: miles@gnu.org, schwab@linux-m68k.org, monnier@IRO.UMontreal.CA,
	emacs-devel@gnu.org
Subject: Re: remove leim/leim-list.el for make bootstrap?
Date: Fri, 27 Mar 2009 11:42:16 +0300	[thread overview]
Message-ID: <umyb7mk5z.fsf@gnu.org> (raw)
In-Reply-To: <E1Ln65j-0002gL-CY@etlken>

> From: Kenichi Handa <handa@m17n.org>
> CC: emacs-devel@gnu.org, schwab@linux-m68k.org, monnier@IRO.UMontreal.CA,
>         miles@gnu.org
> Date: Fri, 27 Mar 2009 16:02:59 +0900
> 
> % make
> ## Now leim-list.el is correctly build with utf-8 encoding.
> % ls -ltgo lisp/international/quail.el* lisp/international/mule-cmds.el* leim/leim-*.el
> -rw-rw-r-- 1  26904 2009-03-23 20:08 leim/leim-list.el
> -rw-rw-r-- 1  81164 2009-03-23 20:07 lisp/international/quail.elc
> -rw-rw-r-- 1  86291 2009-03-23 20:06 lisp/international/mule-cmds.elc
> -rw-rw-r-- 1 116870 2009-03-23 20:03 lisp/international/mule-cmds.el
> -rw-rw-r-- 1 115082 2009-03-23 20:03 lisp/international/quail.el
> -rw-rw-r-- 1   3040 2009-03-23 20:03 leim/leim-ext.el
> 
> > The situation in which the problem happens
> > should use an old quail.elc that still uses iso-2022, but new
> > leim-ext.el and mule-cmds.el which are already switched to utf-8.
> 
> It seems that such a situation doesn't happen with the
> normal building sequence as above.

<Shrug> I guess we can close the issue, then.




  reply	other threads:[~2009-03-27  8:42 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
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 [this message]
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

  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=umyb7mk5z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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 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).