From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: with-output-to-temp-buffer [Re: reverting CJK input methods] Date: 11 May 2004 08:55:03 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040429.150303.42778779.wl@gnu.org> <200404300142.KAA01027@etlken.m17n.org> <87u0z1puxa.fsf@mail.jurta.org> <200404301326.WAA02744@etlken.m17n.org> <8765bga5tt.fsf@mail.jurta.org> <200405020157.KAA07108@etlken.m17n.org> <200405060505.OAA21188@etlken.m17n.org> <200405061310.WAA22378@etlken.m17n.org> <200405101213.VAA04125@etlken.m17n.org> <200405110145.i4B1jNF22171@raven.dms.auburn.edu> <200405110234.LAA06316@etlken.m17n.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084266641 1521 80.91.224.253 (11 May 2004 09:10:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 May 2004 09:10:41 +0000 (UTC) Cc: juri@jurta.org, emacs-devel@gnu.org, teirllm@dms.auburn.edu, rms@gnu.org, Kenichi Handa Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 11 11:10:25 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNTHN-00055q-00 for ; Tue, 11 May 2004 11:10:25 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNTHN-0007vL-00 for ; Tue, 11 May 2004 11:10:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNTF6-0007PW-35 for emacs-devel@quimby.gnus.org; Tue, 11 May 2004 05:08:04 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNTE3-0007Ax-18 for emacs-devel@gnu.org; Tue, 11 May 2004 05:06:59 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNT9n-0005Tn-BR for emacs-devel@gnu.org; Tue, 11 May 2004 05:03:08 -0400 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.34) id 1BNT9f-0005P4-Q9 for emacs-devel@gnu.org; Tue, 11 May 2004 05:02:28 -0400 Original-Received: (qmail 4492 invoked from network); 11 May 2004 08:55:44 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 11 May 2004 08:55:44 -0000 Original-To: David Kastrup In-Reply-To: Original-Lines: 26 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23122 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23122 David Kastrup writes: > Kenichi Handa writes: > > In addtion, to make a final decision, we must study how > > erase-buffer is used in various codes, which consumes our > > working time much and results in the delay of the next > > release. I think the sooner release is more important than > > completely settling on what to do with this problem. > > Can anyone think of any reason why erase-buffer should not remove the > current buffer completely? And no, I don't think that read-only > properties on some entries in a buffer count as a reason: > erase-buffer is basically a buffer-wide operation and should only be > influenced by buffer-wide read-only-ness. > > If you want to protect your buffer against erasure, set the whole > buffer to read-only. Or signal errors in before-change-functions, > without actually doing the change. > > That is easy enough to do, and much more reliable. I agree. -- Kim F. Storm http://www.cua.dk