From: Alex Schroeder <alex@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: encoding of lisp/language/devan-util.el
Date: Sat, 15 Mar 2003 11:13:32 +0100 [thread overview]
Message-ID: <87wuj1lyyb.fsf@gnu.org> (raw)
In-Reply-To: 200303150029.JAA23936@etlken.m17n.org
Kenichi Handa <handa@m17n.org> writes:
> In HEAD, we introduced a new charset and devan-util.el of
> HEAD contains those characters. Thus, of course, RC can't
> read that file correctly.
Ok, that explains why I cannot read the file with my RC Emacs.
Thanks. I will investigate further why it seems that I cannot build
Emacs from CVS.
Alex.
next prev parent reply other threads:[~2003-03-15 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 15:33 encoding of lisp/language/devan-util.el Alex Schroeder
2003-03-14 17:35 ` Andreas Schwab
2003-03-14 20:36 ` Alex Schroeder
2003-03-14 21:06 ` Andreas Schwab
2003-03-15 0:29 ` Kenichi Handa
2003-03-15 10:13 ` Alex Schroeder [this message]
2003-03-16 17:58 ` Alex Schroeder
2003-03-14 21:31 ` Alex Schroeder
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=87wuj1lyyb.fsf@gnu.org \
--to=alex@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 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).