From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: file coding for ChangeLog?
Date: Tue, 18 Dec 2001 10:04:40 -0500 [thread overview]
Message-ID: <874rmoa7sn.fsf@paradoxical.net> (raw)
In-Reply-To: <vafbsgwvnj6.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> In Emacs, this means that the file is opened and decoded using the
> default coding system, and only later is the coding system set to
> what you specify. And if Emacs decides to use UTF-8 (say) for
> decoding, then you lose.
Ah yes, I hadn't thought of this.
> Please use "coding" with Emacs.
Yes, and after reading the documentation for XEmacs, it's supposed to
support the coding tag, so it appears this is a problem on my end.
sorry for the confusion.
I've changed buffer-file-coding-system back to coding, but left the
conversion to Local Variables...
Sorry for the noise...I'll see if it's a configuration problem here or
a bug in my Emacs. :(
--
Josh Huber
next prev parent reply other threads:[~2001-12-18 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 21:10 Josh Huber
2001-12-15 6:25 ` ShengHuo ZHU
2001-12-16 4:23 ` Josh Huber
2001-12-18 10:19 ` Kai Großjohann
2001-12-18 15:04 ` Josh Huber [this message]
2001-12-18 15:36 ` Kai Großjohann
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=874rmoa7sn.fsf@paradoxical.net \
--to=huber@alum.wpi.edu \
/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.
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 NNTP newsgroup(s).