From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: Aidan Kehoe <kehoea@parhasard.net>
Subject: Re: nnmail-pathname-coding-system breaks my XEmacs.
Date: Mon, 12 Jan 2009 10:08:18 +0900 [thread overview]
Message-ID: <b4m4p05e3gd.fsf@jpl.org> (raw)
In-Reply-To: <87hc45o6ea.fsf@marauder.physik.uni-ulm.de>
>>>>> In <87hc45o6ea.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> On Sun, Jan 11 2009, Aidan Kehoe wrote:
> > Sehr geehrte Damen und Herren!
> Since all of the recent matches for nnmail-pathname-coding-system in
> ChangeLog point to Katsumi Yamaoka, a Japanese greeting would be more
> appropriate. ;-)
I'll look into it tomorrow. Sorry I have no time today. Anyway
those `file-name-coding-system' uses are for files used of
non-ASCII group names. cf. (info "(gnus)Non-ASCII Group Names")
> > Why is Gnus overriding file-name-coding-system? For example, in
> > nnmh-active-number, and pretty much everywhere that
> > nnmail-pathname-coding-system is used. In XEmacs 21.5 we have stupid hackery
> > that maintains the file-name coding system alias as equivalent to the
> > file-name-coding-system variable, but this doesn’t know about dynamic scope,
> > so after I’ve used Gnus my file-name-coding-system is reset to binary, which
> > is useless on OS X. If you’re using anything non-ASCII I imagine it’ll break
> > under Gnus too, and if you’re not using anything non-ASCII, why bother
> > messing with the variable at all?
> [...]
> > Gnus v5.10.8
> > XEmacs 21.5 (beta28) "fuki" 302136a857ec+ [Lucid] (i386-apple-darwin8.11.1, Mule) of Sat Jan 10 2009 on bonbon
next prev parent reply other threads:[~2009-01-12 1:08 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 [this message]
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
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=b4m4p05e3gd.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).