Gnus development mailing list
 help / color / mirror / Atom feed
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 17:10:16 +0200	[thread overview]
Message-ID: <v9wucpj4br.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b9yk78q9kzm.fsf@jpl.org>

On Wed, Sep 03 2003, Katsumi Yamaoka wrote:

>>>>>>	Reiner Steib <4.uce.03.r.s@nurfuerspam.de> wrote:
>
>> All mentioned files already contain a cookie:
[...]
>> Doesn't XEmacs allow the cookie in the local variables section?
>
> Unfortunately, it probably be so. :(

This seems to be a bug (see also [1]) in XEmacs 21.4 then, as (info
"(XEmacs)Recognize Coding") in XEmacs 21.4.12 mentions local
variables:

,----[ (info "(XEmacs)Recognize Coding") ]
|    You can specify the coding system for a particular file using the
| `-*-...-*-' construct at the beginning of a file, or a local variables
| list at the end (*note File Variables::).  You do this by defining a
| value for the "variable" named `coding'.  XEmacs does not really have a
| variable `coding'; instead of setting a variable, it uses the specified
| coding system for the file.
`----

Bye, Reiner.

[1]
<URL:http://news.gmane.org/onethread.php?group=gmane.emacs.xemacs.beta
&root=%3C20020506193719.30420.qmail%40ypy.tky.hut.fi%3E>
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  parent reply	other threads:[~2003-09-03 15:10 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
2003-09-03 11:20   ` Katsumi Yamaoka
2003-09-03 12:41     ` Katsumi Yamaoka
2003-09-03 15:10     ` Reiner Steib [this message]
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=v9wucpj4br.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).