From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68158 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: nnmail-pathname-coding-system breaks my XEmacs. Date: Wed, 14 Jan 2009 19:57:48 +0900 Organization: Emacsen advocacy group Message-ID: References: <18794.15468.881403.994781@parhasard.net> <87hc45o6ea.fsf@marauder.physik.uni-ulm.de> <18795.12614.222792.255516@parhasard.net> <18796.33500.65305.970938@parhasard.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: ger.gmane.org 1231930786 16983 80.91.229.12 (14 Jan 2009 10:59:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 14 Jan 2009 10:59:46 +0000 (UTC) Cc: ding@gnus.org To: Aidan Kehoe Original-X-From: ding-owner+M16602@lists.math.uh.edu Wed Jan 14 12:00:56 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 1LN3UT-0005Vu-U4 for ding-account@gmane.org; Wed, 14 Jan 2009 12:00:54 +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 1LN3SJ-0002cw-8b; Wed, 14 Jan 2009 04:58: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 1LN3SH-0002cg-68 for ding@lists.math.uh.edu; Wed, 14 Jan 2009 04:58: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 1LN3SE-0005py-BZ for ding@lists.math.uh.edu; Wed, 14 Jan 2009 04:58:37 -0600 Original-Received: from orlando.hostforweb.net ([216.246.45.90]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LN3SU-0000fO-00 for ; Wed, 14 Jan 2009 11:58:50 +0100 Original-Received: from localhost ([127.0.0.1]:51671) by orlando.hostforweb.net with esmtpa (Exim 4.69) id 1LN3Ra-0002Xd-DA; Wed, 14 Jan 2009 04:57:55 -0600 X-Hashcash: 1:20:090114:kehoea@parhasard.net::PaHgLi3LyhHU9oYk:000000000000000000000000000000000000000001y9T X-Hashcash: 1:20:090114:ding@gnus.org::6ZwMCyPOENraSxyn:000005cS X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110011 (No Gnus v0.11) XEmacs/21.5-b28 (linux) Cancel-Lock: sha1:qzR/im/IVq6mUKnfDs/vCunZ0Vg= X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.6 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:68158 Archived-At: --=-=-= Content-Type: text/plain; charset=iso-8859-1 >>>>> Katsumi Yamaoka wrote: > system (I didn't know it!), which defaults to something according > to the locale name. > In XEmacs 21.5, binding of `file-name-coding-system' to nil changes > `file-name' even if `file-name-coding-system' is nil from the outset. [...] > Moreover, binding of `file-name-coding-system' to any coding system > seems to be a trigger to make the `file-name' coding sysem binary. I realized there is no difference in XEmacs 21.4. What I tried is attached below. 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))))) ;; `(if (featurep 'xemacs) ...)' is a compiler directive for ;; letting GNU Emacs generate no byte code. After performing it, XEmacs at least in Linux box seems to run with no problem as follows: --8<---------------cut here---------------start------------->8--- (get-coding-system 'file-name) => # (let ((file-name-coding-system nil))) => nil (get-coding-system 'file-name) => # (let ((file-name-coding-system 'iso-2022-jp)) (get-coding-system 'file-name)) => # # --8<---------------cut here---------------end--------------->8--- If it's ok in OS X, I wish XEmacs itself to do something similar. But it might be necessary to be in `gnus-xmas-redefine' in gnus-xmas.el (nnmail.el loads it) for those who use old XEmacs. For the latter case, it has to be guaranteed that the workaround does no harm even in the distant future. Regards, --=-=-= Content-Type: application/octet-stream Content-Disposition: attachment emacs-version => "21.4 (patch 22) \"Instant Classic\" XEmacs Lucid" (getenv "LC_CTYPE") => "ja_JP.eucJP" file-name-coding-system => iso-2022-jp (setq file-name-coding-system nil) => nil (get-coding-system 'file-name) => # (define-coding-system-alias 'file-name 'iso-2022-jp) => nil file-name-coding-system => nil (get-coding-system 'file-name) => # (let ((file-name-coding-system nil))) => nil (get-coding-system 'file-name) => # --=-=-=--