Gnus development mailing list
 help / color / mirror / Atom feed
From: Aidan Kehoe <kehoea@parhasard.net>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>, ding@gnus.org
Subject: Re: nnmail-pathname-coding-system breaks my XEmacs.
Date: Wed, 14 Jan 2009 20:48:47 +0000	[thread overview]
Message-ID: <18798.20399.284442.90062@parhasard.net> (raw)
In-Reply-To: <871vv5lk21.fsf@marauder.physik.uni-ulm.de>


 Ar an ceathrú lá déag de mí Eanair, scríobh Reiner Steib: 

 > On Wed, Jan 14 2009, Aidan Kehoe wrote:
 > 
 > > 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)))
 > 
 > I didn't follow the thread carefully.  Do I understand correctly, that
 > the problem was a bug that is/was present only in XEmacs 21.5?

Well. I don’t think much of the nnmail-pathname-coding-system idea, from my
perspective it in itself is a bug, it should not be overriding
file-name-coding-system. It is not being a very good citizen to use
non-standard encoding for path names in a given directory without very good
reason. It does not look like Yamaoka is going to come around to that
perspective, though.

With the change to the XEmacs 21.5 sources above, the consequences of the
use of nnmail-pathname-coding-system are not as serious as they used to be,
for non-Gnus code; the consequences of the use of
nnmail-pathname-coding-system remain as bad as they used to be for the Gnus
code, because since nnmail-pathname-coding-system is normally nil, the
binary coding system will be used for all file names corresponding to group
names.

With the macro as proposed, Gnus users on beta XEmacs will no longer see the
consequences of the use of nnmail-pathname-coding-system for non-Gnus code.

-- 
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?



  reply	other threads:[~2009-01-14 20:48 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 [this message]
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=18798.20399.284442.90062@parhasard.net \
    --to=kehoea@parhasard.net \
    --cc=Reiner.Steib@gmx.de \
    --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).