From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: po file charset via auto-coding-functions Date: Sat, 19 Nov 2005 18:27:06 -0500 Message-ID: References: <87zmp399ue.fsf@zip.com.au> <87ll0ma3ow.fsf@zip.com.au> <87fyqu9ung.fsf@zip.com.au> <877jbhrwox.fsf-monnier+emacs@gnu.org> <87psp8qrz9.fsf-monnier+emacs@gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1132443042 13175 80.91.229.2 (19 Nov 2005 23:30:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 19 Nov 2005 23:30:42 +0000 (UTC) Cc: user42@zip.com.au, monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 20 00:30:33 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EdcA8-00018T-2y for ged-emacs-devel@m.gmane.org; Sun, 20 Nov 2005 00:30:28 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EdcA7-0004u6-Gk for ged-emacs-devel@m.gmane.org; Sat, 19 Nov 2005 18:30:27 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Edc73-0003ni-E3 for emacs-devel@gnu.org; Sat, 19 Nov 2005 18:27:17 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Edc72-0003mu-O6 for emacs-devel@gnu.org; Sat, 19 Nov 2005 18:27:17 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Edc72-0003mh-H0 for emacs-devel@gnu.org; Sat, 19 Nov 2005 18:27:16 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Edc72-0005RZ-MX for emacs-devel@gnu.org; Sat, 19 Nov 2005 18:27:16 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1Edc6s-0002BI-Ax; Sat, 19 Nov 2005 18:27:06 -0500 Original-To: Kenichi Handa In-reply-to: (message from Kenichi Handa on Fri, 18 Nov 2005 22:08:34 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:46297 Archived-At: I don't know exactly which command uses it, but it is used by any operations that call get-file-buffer. Most callers of get-file-buffer pass a real file name. So unless someone uses a file whose name resembles that of a tar subfile, get-file-buffer will never return one of these buffers, and I think that is the correct result. Thus, looking at my question: > Does that file name get used for anything except to appear in the C_x > C-b listing and be helpful for the user? I think it does not. I think I was right--it is not used for anything else, or at least, not unless a problem is occurring. Therefore, we do not want to install any file name handler for this syntax. > If it is simply a matter to call find-operation-coding-system here, > in tar-extract, then I agree it is ok to pass buffer-file-name. Yes, that is what the change I propsed for an archived file does. Ok, please make that change. + (let ((buffer-file-name + (concat file "!" + (jka-compr-byte-compiler-base-file-name file)))) + Binding buffer-file-name is rather unclean. And I don't see a reason to do it. so that find-operation-coding-system (called in decode-coding-inserted-region) can surely find po-find-file-coding-system to be called, and it can surely find the current buffer by get-file-buffer. decode-coding-inserted-region passes its FILENAME arg to find-operation-coding-system. So all you need to do is to pass this funny file name to decode-coding-inserted-region. There is no need to bind buffer-file-name. Why are you concerned about whether get-file-buffer can be used with this funny file name?