From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: Bootstrapping Unicode branch on Windows
Date: Fri, 9 Feb 2007 11:27:26 +0100 [thread overview]
Message-ID: <f7ccd24b0702090227u2feb9a28x912de597e80d6500@mail.gmail.com> (raw)
In-Reply-To: <f7ccd24b0702081731j281b042ay1759e484db0a33c6@mail.gmail.com>
Finally I've been able to solve the mystery, and it's my fault...
While trying to work around the initial issue (with
lisp/international/uni-*.el files) I did several tests with and
without -kb. In one of these tests, I accidentally updated most of
leim/*/* with
cvs -q update -C -A
instead of
cvs -q update -C -A -r emacs-unicode-2
so I had an emacs-unicode-2 source tree with leim/* switched back to
HEAD. Definitely Not Recommendable.
All in all, I'd suggest adding a note somewhere in the emacs-unicode-2
branch (nt/INSTALL, perhaps) clarifying which files need to be checked
out with -kb, and the trick of defining a LANG environment variable
with UTF-8 to avoid warnings about conflicting codesets. This will
make life easier for anyone trying to compile the unicode branch (and
soon the HEAD, hopefully) on Windows.
/L/e/k/t/u
next prev parent reply other threads:[~2007-02-09 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 16:35 Bootstrapping Unicode branch on Windows Juanma Barranquero
2007-02-08 11:27 ` Juanma Barranquero
2007-02-08 12:33 ` Jason Rumney
2007-02-08 13:15 ` Juanma Barranquero
2007-02-08 18:01 ` Zhang Wei
2007-02-09 1:31 ` Juanma Barranquero
2007-02-09 10:27 ` Juanma Barranquero [this message]
2007-02-09 16:14 ` Eli Zaretskii
2007-02-09 16:23 ` Juanma Barranquero
2007-02-11 2:49 ` Kenichi Handa
2007-02-12 9:41 ` Juanma Barranquero
2007-02-12 13:59 ` Kenichi Handa
2007-02-12 14:57 ` Juanma Barranquero
2007-02-12 15:06 ` Jason Rumney
2007-02-12 15:13 ` Juanma Barranquero
2007-02-12 20:37 ` Eli Zaretskii
2007-02-12 21:26 ` Juanma Barranquero
2007-02-14 3:18 ` Juanma Barranquero
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=f7ccd24b0702090227u2feb9a28x912de597e80d6500@mail.gmail.com \
--to=lekktu@gmail.com \
--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.