Re: nnmail-pathname-coding-system breaks my XEmacs.

[Aidan Kehoe <kehoea@parhasard.net>]

 Ar an cúigiú lá déag de mí Eanair, scríobh Katsumi Yamaoka: 

 > [...] IIUC `(setq file-name-coding-system ...)' here is for XEmacs 21.5
 > to which your patch has not been applied yet. Is it necessary to do that
 > in advance whenever one binds `file-name-coding-system' to something? 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. 

 > That is,
 > 
 > >>>>> In <b4mtz82duj7.fsf@jpl.org> Katsumi Yamaoka wrote:
 > > 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)))))

No, you want:

 (setq file-name-coding-system (coding-system-aliasee 'file-name))

 > I planned to introduce such a wrapper, however there are many
 > places that need it in Gnus:
 > 
 > $ grep '(file-name-coding-system' *.el | wc -l
 > 88
 > 
 > So, I'd like to use a much simpler way to fix the problem if
 > possible.  Note that the Gnus release (i.e. the Emacs 23 release)
 > is around the corner.
 > 
 > Regards,
 > 
 > P.S. I wonder why this is brought up now although binding of
 > pathname-coding-system (the predecessor of file-name-coding-system)
 > appeared first in Quassia Gnus v0.1 (1997). ;-)

I reported the bug because I recently learned a debugging technique which
discovering what went wrong much, much easier.

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