From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68144 Path: news.gmane.org!not-for-mail From: Aidan Kehoe Newsgroups: gmane.emacs.gnus.general Subject: Re: nnmail-pathname-coding-system breaks my XEmacs. Date: Mon, 12 Jan 2009 12:02:14 +0000 Message-ID: <18795.12614.222792.255516@parhasard.net> References: <18794.15468.881403.994781@parhasard.net> <87hc45o6ea.fsf@marauder.physik.uni-ulm.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1231761807 19645 80.91.229.12 (12 Jan 2009 12:03:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 12 Jan 2009 12:03:27 +0000 (UTC) Cc: ding@gnus.org To: Katsumi Yamaoka Original-X-From: ding-owner+M16588@lists.math.uh.edu Mon Jan 12 13:04:39 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1LMLWx-000227-V5 for ding-account@gmane.org; Mon, 12 Jan 2009 13:04:32 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1LMLV9-00066f-JG; Mon, 12 Jan 2009 06:02:39 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1LMLV7-00066J-Iz for ding@lists.math.uh.edu; Mon, 12 Jan 2009 06:02:37 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LMLV5-0003a1-1Z for ding@lists.math.uh.edu; Mon, 12 Jan 2009 06:02:37 -0600 Original-Received: from daedalus.ipv4.asclepian.ie ([213.133.100.226] helo=daedalus.asclepian.ie) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LMLVL-0007De-00 for ; Mon, 12 Jan 2009 13:02:51 +0100 Original-Received: by daedalus.asclepian.ie (Postfix, from userid 1002) id CCE06B831; Mon, 12 Jan 2009 12:02:14 +0000 (GMT) In-Reply-To: X-Mailer: VM 8.0.12 under 21.5 (beta28) "fuki" XEmacs Lucid (x86_64-unknown-freebsd7.0) X-Echelon-distraction: Ortega WWSP SDF HoHoCon Ceridian PCS X-Spam-Score: -0.6 (/) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:68144 Archived-At: Ar an dara l=C3=A1 d=C3=A9ag de m=C3=AD Eanair, scr=C3=ADobh Katsumi Yam= aoka:=20 > >>>>> In <87hc45o6ea.fsf@marauder.physik.uni-ulm.de> > >>>>> Reiner Steib wrote: > > On Sun, Jan 11 2009, Aidan Kehoe wrote: >=20 > > > Sehr geehrte Damen und Herren! >=20 > > Since all of the recent matches for nnmail-pathname-coding-system in > > ChangeLog point to Katsumi Yamaoka, a Japanese greeting would be mor= e > > appropriate. ;-) >=20 > 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") If this reflects the current state of affairs:=20 nnmail-pathname-coding-system The value of this variable should be a coding system or nil (which is the default). The nnml back end, the nnrss back end, the NNTP marks feature (see section 6.2.1.4 NNTP marks), the agent, and the cache us= e non-ASCII group names in those files and directories. This variable overrides the value of file-name-coding-system which specifies the coding system used when encoding and decoding those file names and directory names. In XEmacs (with the mule feature), file-name-coding-system is the onl= y means to specify the coding system used to encode and decode file names. Therefore, you, XEmacs users, have to set it to the coding sys= tem that is suitable to encode and decode non-ASCII group names. On the other hand, Emacs uses the value of default-file-name-coding-system i= f file-name-coding-system is nil. Normally the value of default-file-name-coding-system is initialized according to the local= e, so you will need to do nothing if the value is suitable to encode and decode non-ASCII group names. (from http://www.gnus.org/manual/gnus_40.html )=20 why aren=E2=80=99t you just using file-name-coding-system? This is initia= lised correctly these days (except if you=E2=80=99re dealing, say, with an exte= rnal or network drive where your host OS doesn=E2=80=99t understand its file name= encoding; but nothing can really initialise correctly in that case) though I admit there were years where we dealt with it very badly.=20 (Note that nil, your default, corresponds to the binary, no-conversion coding system under XEmacs, which, for example, Mac OS X will not accept when asked to create a file name with non-ASCII characters in that encodi= ng, it requires valid UTF-8.) > > > 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 stup= id hackery > > > that maintains the file-name coding system alias as equivalent to = the > > > file-name-coding-system variable, but this doesn=E2=80=99t know ab= out dynamic scope, > > > so after I=E2=80=99ve used Gnus my file-name-coding-system is rese= t to binary, which > > > is useless on OS X. If you=E2=80=99re using anything non-ASCII I i= magine it=E2=80=99ll break > > > under Gnus too, and if you=E2=80=99re 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-dar= win8.11.1, Mule) of Sat Jan 10 2009 on bonbon --=20 =C2=BFD=C3=B3nde estar=C3=A1 ahora mi sobrino Yoghurtu Nghe, que tuvo que= huir precipitadamente de la aldea por culpa de la escasez de rinocerontes?