From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: non-ascii chars in the Lisp source files
Date: Wed, 03 Sep 2003 12:43:45 +0200 [thread overview]
Message-ID: <v97k4qywwu.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b9yptiibdby.fsf@jpl.org>
On Wed, Sep 03 2003, Katsumi Yamaoka wrote:
> The following files also contain non-ascii chars:
>
> deuglify.el gnus-delay.el gnus-spec.el mml1991.el nnultimate.el
> utf7.el (the last one already contains the coding cookie.)
All mentioned files already contain a cookie:
$ for i in deuglify.el gnus-delay.el gnus-spec.el mml1991.el \
nnultimate.el utf7.el gnus-sum.el; do
grep -ne coding: $i /dev/null
done
deuglify.el:468:;; coding: iso-8859-1
gnus-delay.el:192:;; coding: iso-8859-1
gnus-spec.el:754:;; coding: iso-8859-1
mml1991.el:296:;; coding: iso-8859-1
nnultimate.el:476:;; coding: iso-8859-1
utf7.el:1:;;; utf7.el --- UTF-7 encoding/decoding for Emacs -*-coding: iso-8859-1;-*-
gnus-sum.el:11634:;; coding: iso-8859-1
Doesn't XEmacs allow the cookie in the local variables section?
,----
| ;; Local Variables:
| ;; coding: iso-8859-1
| ;; End:
|
| ;;; gnus-sum.el ends here
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-09-03 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 6:22 Katsumi Yamaoka
2003-09-03 7:01 ` Daniel Pittman
2003-09-03 9:06 ` Robert Epprecht
2003-09-03 7:38 ` Katsumi Yamaoka
2003-09-03 10:43 ` Reiner Steib [this message]
2003-09-03 11:20 ` Katsumi Yamaoka
2003-09-03 12:41 ` Katsumi Yamaoka
2003-09-03 15:10 ` Reiner Steib
2003-09-04 0:58 ` Katsumi Yamaoka
2003-09-04 10:13 ` Juha Autero
2003-09-04 11:09 ` Katsumi Yamaoka
2003-09-05 12:26 ` Katsumi Yamaoka
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=v97k4qywwu.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).