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: Wed, 28 Dec 2005 12:01:32 -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 1135791363 723 80.91.229.2 (28 Dec 2005 17:36:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 28 Dec 2005 17:36:03 +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 Wed Dec 28 18:36:01 2005 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ErfDP-0004VR-No for ged-emacs-devel@m.gmane.org; Wed, 28 Dec 2005 18:35:56 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ErfEe-0000uz-32 for ged-emacs-devel@m.gmane.org; Wed, 28 Dec 2005 12:37:12 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EreiG-0001T4-7x for emacs-devel@gnu.org; Wed, 28 Dec 2005 12:03:45 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EreiD-0001RY-O9 for emacs-devel@gnu.org; Wed, 28 Dec 2005 12:03:42 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EreiD-0001RE-38 for emacs-devel@gnu.org; Wed, 28 Dec 2005 12:03:41 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EreiP-0007JQ-Ic for emacs-devel@gnu.org; Wed, 28 Dec 2005 12:03:53 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1Ereg8-0000Fq-AH; Wed, 28 Dec 2005 12:01:32 -0500 Original-To: Kenichi Handa In-reply-to: (message from Kenichi Handa on Sun, 20 Nov 2005 21:05:56 +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:48434 Archived-At: Please forgive the delay in my response. > 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? A function registered in find-operation-coding-system have to find which buffer is pretending to visit FILENAME if FILENAME doesn't exist. And, get-file-buffer is the only (or at least the very natural) way for that. Could you give me an example or two? Which filename handler function does this? Looking at an example, I can understand the issue.