From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Saving when the coding system can't code all buffer characters Date: Sat, 23 Dec 2006 21:41:04 +0100 Message-ID: <458D9460.7080304@student.lu.se> References: <6f1c06d176.6d1766f1c0@net.lu.se> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1166906489 26611 80.91.229.10 (23 Dec 2006 20:41:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 23 Dec 2006 20:41:29 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 23 21:41:28 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by dough.gmane.org with esmtp (Exim 4.50) id 1GyDgH-00038M-Ed for ged-emacs-devel@m.gmane.org; Sat, 23 Dec 2006 21:41:21 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GyDgG-0001W0-SR for ged-emacs-devel@m.gmane.org; Sat, 23 Dec 2006 15:41:21 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GyDg4-0001TZ-BW for emacs-devel@gnu.org; Sat, 23 Dec 2006 15:41:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GyDg2-0001Si-OR for emacs-devel@gnu.org; Sat, 23 Dec 2006 15:41:08 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GyDg2-0001Sf-Ls for emacs-devel@gnu.org; Sat, 23 Dec 2006 15:41:06 -0500 Original-Received: from [80.76.149.212] (helo=ch-smtp01.sth.basefarm.net) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GyDfy-0003Vg-RC; Sat, 23 Dec 2006 15:41:03 -0500 Original-Received: from c83-254-145-24.bredband.comhem.se ([83.254.145.24]:62595 helo=[127.0.0.1]) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.63) (envelope-from ) id 1GyDfx-000164-3e; Sat, 23 Dec 2006 21:41:01 +0100 User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) Original-To: rms@gnu.org In-Reply-To: X-Antivirus: avast! (VPS 0662-0, 2006-12-22), Outbound message X-Antivirus-Status: Clean X-Scan-Result: No virus found in message 1GyDfx-000164-3e. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1GyDfx-000164-3e 9ecfa950c44a98cf589c70fdc99a2604 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:64173 Archived-At: Richard Stallman wrote: > > It would IMHO be much more convenient if point in the buffer to save was left at the problematic character. > > Maybe we should simply include the information displayed by "C-u C-x =" > in the same *Warning* buffer that explains the problem. That would > eliminate the need for telling about "C-u C-x =" and for an > arrangement to find the problematic characters after C-g. > > That sounds like a good approach. Would someone please try it? I think it is important to have a simple way to find the problematic character too. As I wrote before something like a button field in the *Warning* buffer is one idea.