From: Aidan Kehoe <kehoea@parhasard.net>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: nnmail-pathname-coding-system breaks my XEmacs.
Date: Wed, 14 Jan 2009 11:33:24 +0000 [thread overview]
Message-ID: <18797.52612.666509.700581@parhasard.net> (raw)
In-Reply-To: <b4meiz6fl7m.fsf@jpl.org>
Ar an ceathrú lá déag de mí Eanair, scríobh Katsumi Yamaoka:
> > UTF-8 is *enforced* on OS X, in contrast to most Unix environments.
>
> I imagine it is similar to DOS machines in which shift_jis is
> used for file names in Japan. (Though I don't know how files
> are on OS X, since my daughters don't give me leave to touch
> their MacBooks.)
With the important difference that it can encode everything, so there’s no
need to play around with differing file-name-coding-systems for differing
parts of the file hierarchy, the data won’t be trashed.
> [...] Anyway I still believe there is no reason to abolish the
> `nnmail-pathname-coding-system' control in Gnus. However, for the momemnt
> I have no idea to cope with that behavior. Isn't there a chance to make
> it work like XEmacs 21.4?
I made this change yesterday to do that:
http://hg.debian.org/hg/xemacs/xemacs?cs=774e5c7522bf
This version of your macro works with versions of 21.5 both with and without
that patch, and with 21.4:
(defmacro nnmail-with-pathname-coding-system (&rest forms)
"Bind `file-name-coding-system' while running FORMS.
A non-nil value of `nnmail-pathname-coding-system' will be used for
decoding and encoding file names."
(if (featurep 'xemacs)
`(progn
(when (featurep 'file-coding)
;; Work around a bug in many 21.5 betas:
(setq file-name-coding-system (coding-system-aliasee
'file-name)))
(let ((file-name-coding-system
nnmail-pathname-coding-system))
,@forms))
`(let ((file-name-coding-system nnmail-pathname-coding-system))
,@forms)))
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
next prev parent reply other threads:[~2009-01-14 11:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18794.15468.881403.994781@parhasard.net>
2009-01-11 21:54 ` Reiner Steib
2009-01-12 1:08 ` Katsumi Yamaoka
2009-01-12 12:02 ` Aidan Kehoe
2009-01-13 6:46 ` Katsumi Yamaoka
2009-01-13 12:02 ` Aidan Kehoe
2009-01-14 6:36 ` Katsumi Yamaoka
2009-01-14 10:57 ` Katsumi Yamaoka
2009-01-14 11:33 ` Aidan Kehoe [this message]
2009-01-14 20:16 ` Reiner Steib
2009-01-14 20:48 ` Aidan Kehoe
2009-01-15 0:25 ` Katsumi Yamaoka
2009-01-15 0:35 ` Aidan Kehoe
2009-01-16 8:05 ` Katsumi Yamaoka
2009-01-16 14:19 ` Aidan Kehoe
2009-01-14 20:56 ` Aidan Kehoe
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=18797.52612.666509.700581@parhasard.net \
--to=kehoea@parhasard.net \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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.
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).