From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: `*' interactive spec in some text-killing functions Date: Thu, 28 Jun 2007 00:11:17 +0200 Message-ID: References: <86fy4dzdzd.fsf@lola.quinscape.zz> <858xa56rm5.fsf@lola.goethe.zz> <85y7i55a0v.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1182982286 13341 80.91.229.12 (27 Jun 2007 22:11:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 27 Jun 2007 22:11:26 +0000 (UTC) Cc: emacs-devel To: "David Kastrup" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 28 00:11:24 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1I3fjP-00026q-9w for ged-emacs-devel@m.gmane.org; Thu, 28 Jun 2007 00:11:23 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I3fjO-00035i-EB for ged-emacs-devel@m.gmane.org; Wed, 27 Jun 2007 18:11:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I3fjL-00032s-Fz for emacs-devel@gnu.org; Wed, 27 Jun 2007 18:11:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I3fjK-00031V-S1 for emacs-devel@gnu.org; Wed, 27 Jun 2007 18:11:19 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I3fjK-00031J-Oc for emacs-devel@gnu.org; Wed, 27 Jun 2007 18:11:18 -0400 Original-Received: from wx-out-0506.google.com ([66.249.82.225]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I3fjK-0006ve-Be for emacs-devel@gnu.org; Wed, 27 Jun 2007 18:11:18 -0400 Original-Received: by wx-out-0506.google.com with SMTP id h26so323739wxd for ; Wed, 27 Jun 2007 15:11:17 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sp22aNJxMoEI9U8RQdNBGgbxX3v4nqXXTgancO0zLVl8vLjgSAyJ3+IcQOj+qSr5IM6yRgwUjzbRvmgCgKNzAXsUcHfq+iR3BBpK1bQeRi3EjWS0kZ8QgbbEX0oOVtGwAVtqBr+2aAd6xTnSKPVN2bOsEJGaKXu+YcvdJJRP/98= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=P7V93OZKmE6fF0eOX8k7cxXGiINpCmfh/1wM1Sxl+7OiIJ98/Kp8MUzwH94ons+o152W3yVlT3E2BcETdipCLL9S4x8TDizfYUptNratjLHNvOLmYdADcr/3Wg3xogkzkmWzk1I7zib9kAHE3UThnzCBKDvVb46ZUqj7EM10Ns0= Original-Received: by 10.90.93.6 with SMTP id q6mr1221229agb.1182982277710; Wed, 27 Jun 2007 15:11:17 -0700 (PDT) Original-Received: by 10.90.87.8 with HTTP; Wed, 27 Jun 2007 15:11:17 -0700 (PDT) In-Reply-To: <85y7i55a0v.fsf@lola.goethe.zz> Content-Disposition: inline X-detected-kernel: Linux 2.4-2.6 (Google crawlbot) 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:73946 Archived-At: On 6/28/07, David Kastrup wrote: > No. `*' does not warn, it throws an error. Interactively, what's an error but a warning to the user? I get a non-intrusive "Buffer is read-only: #" message, and that's all. And non-interactively there's no change in behavior. > That is the reason that the kill > functions that want to affect the kill buffer can't use `*'. I understand that, which is irrelevant to my point. > And a readonly buffer does not get a warning when you try to change > it, but again throws an error, and nothing happens. Regardless > whether you try it interactively or not. `*' does not change that: it > might just throw an error at a more convenient time. I'm not sure what are you trying to say here. Juanma