From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Aidan Kehoe <kehoea@parhasard.net>
Cc: ding@gnus.org
Subject: Re: nnmail-pathname-coding-system breaks my XEmacs.
Date: Wed, 14 Jan 2009 19:57:48 +0900 [thread overview]
Message-ID: <b4mtz82duj7.fsf@jpl.org> (raw)
In-Reply-To: <b4meiz6fl7m.fsf@jpl.org>
[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]
>>>>> Katsumi Yamaoka wrote:
> system (I didn't know it!), which defaults to something according
> to the locale name.
> In XEmacs 21.5, binding of `file-name-coding-system' to nil changes
> `file-name' even if `file-name-coding-system' is nil from the outset.
[...]
> Moreover, binding of `file-name-coding-system' to any coding system
> seems to be a trigger to make the `file-name' coding sysem binary.
I realized there is no difference in XEmacs 21.4. What I tried
is attached below.
BTW, does this workaround do the trick?
(if (featurep 'xemacs)
(if (featurep 'file-coding)
(setq file-name-coding-system
(or file-name-coding-system
(coding-system-name 'file-name)))))
;; `(if (featurep 'xemacs) ...)' is a compiler directive for
;; letting GNU Emacs generate no byte code.
After performing it, XEmacs at least in Linux box seems to
run with no problem as follows:
--8<---------------cut here---------------start------------->8---
(get-coding-system 'file-name)
=> #<coding-system utf-8 unicode(utf-8)>
(let ((file-name-coding-system nil)))
=> nil
(get-coding-system 'file-name)
=> #<coding-system utf-8 unicode(utf-8)>
(let ((file-name-coding-system 'iso-2022-jp))
(get-coding-system 'file-name))
=> #<coding-system iso-2022-jp iso2022(g0=ascii, g1=nil, ...
(get-coding-system 'file-name)
=> #<coding-system utf-8 unicode(utf-8)>
--8<---------------cut here---------------end--------------->8---
If it's ok in OS X, I wish XEmacs itself to do something similar.
But it might be necessary to be in `gnus-xmas-redefine' in
gnus-xmas.el (nnmail.el loads it) for those who use old XEmacs.
For the latter case, it has to be guaranteed that the workaround
does no harm even in the distant future.
Regards,
[-- Attachment #2: Type: application/octet-stream, Size: 520 bytes --]
emacs-version
=> "21.4 (patch 22) \"Instant Classic\" XEmacs Lucid"
(getenv "LC_CTYPE")
=> "ja_JP.eucJP"
file-name-coding-system
=> iso-2022-jp
(setq file-name-coding-system nil)
=> nil
(get-coding-system 'file-name)
=> #<coding_system binary>
(define-coding-system-alias 'file-name 'iso-2022-jp)
=> nil
file-name-coding-system
=> nil
(get-coding-system 'file-name)
=> #<coding_system iso-2022-jp>
(let ((file-name-coding-system nil)))
=> nil
(get-coding-system 'file-name)
=> #<coding_system binary>
next prev parent reply other threads:[~2009-01-14 10:57 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 [this message]
2009-01-14 11:33 ` Aidan Kehoe
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=b4mtz82duj7.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=kehoea@parhasard.net \
/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).