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: Fri, 16 Jan 2009 17:05:37 +0900 [thread overview]
Message-ID: <b4md4en4qwe.fsf@jpl.org> (raw)
In-Reply-To: <18798.33999.638951.592345@parhasard.net>
>>>>> Aidan Kehoe wrote:
> Ar an cúigiú lá déag de mí Eanair, scríobh Katsumi Yamaoka:
>> In other words, supposing `file-name' will not vary after having
>> been set to a certain value according to the system, isn't it
>> enough to do it once when XEmacs starts?
> Once should be okay, yes.
>>> (if (featurep 'xemacs)
>>> (if (featurep 'file-coding)
>>> (setq file-name-coding-system
>>> (or file-name-coding-system
>>> (coding-system-name 'file-name)))))
> No, you want:
> (setq file-name-coding-system (coding-system-aliasee 'file-name))
I've installed this workaround in nnmail.el in No Gnus as follows:
(defvar nnmail-pathname-coding-system
;; This causes Emacs 22.2 and 22.3 to issue a useless warning.
;;(if (and (featurep 'xemacs) (featurep 'file-coding))
(if (featurep 'xemacs)
(if (featurep 'file-coding)
;; Work around a bug in many XEmacs 21.5 betas.
;; Cf. http://thread.gmane.org/gmane.emacs.gnus.general/68134
(setq file-name-coding-system (coding-system-aliasee 'file-name))))
"*Coding system for file name.")
I concluded it's better to be in Gnus (and none other) which
necessarily uses binding of `file-name-coding-system'. By this
change XEmacs users ought to have gotten not to have to customize
this variable if the default value satisfies encoding of all
non-ASCII group names. Also I've updated the Gnus Info manual.
Cf. http://article.gmane.org/gmane.emacs.gnus.commits/6138
and http://article.gmane.org/gmane.emacs.gnus.commits/6139
Regards,
next prev parent reply other threads:[~2009-01-16 8:05 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
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 [this message]
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=b4md4en4qwe.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).