From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: find-file and backward-kill-word Date: Tue, 12 Oct 2004 10:31:41 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: <16746.62602.225874.363145@zarniwoop.ms25.local> <200410120059.i9C0x3O16263@raven.dms.auburn.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1097569966 7345 80.91.229.6 (12 Oct 2004 08:32:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 12 Oct 2004 08:32:46 +0000 (UTC) Cc: reinhard.kotucha@web.de, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 12 10:32:41 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CHI5I-0003ur-00 for ; Tue, 12 Oct 2004 10:32:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CHICH-0002S9-Jo for ged-emacs-devel@m.gmane.org; Tue, 12 Oct 2004 04:39:53 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CHIC6-0002Rp-41 for emacs-devel@gnu.org; Tue, 12 Oct 2004 04:39:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CHIC5-0002RD-0J for emacs-devel@gnu.org; Tue, 12 Oct 2004 04:39:41 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CHIC4-0002RA-Ln for emacs-devel@gnu.org; Tue, 12 Oct 2004 04:39:40 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CHI4M-0003FV-3v for emacs-devel@gnu.org; Tue, 12 Oct 2004 04:31:42 -0400 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1CHI4L-0002gB-Ko; Tue, 12 Oct 2004 04:31:42 -0400 Original-To: Luc Teirlinck In-Reply-To: <200410120059.i9C0x3O16263@raven.dms.auburn.edu> (Luc Teirlinck's message of "Mon, 11 Oct 2004 19:59:03 -0500 (CDT)") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) 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: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:28277 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:28277 Luc Teirlinck writes: > Reinhard Kotucha wrote: > > When I run find-file I get a prompt like this: > > Find file: /tmp/reinhard/ > > I can edit everything on the right to the space after the colon. For > instance, beginning-of-line moves the cursor to the first slash. > > So far so good. But if I then run the command backward-kill-word > (M-DEL), the cursor moves to the "f" of the word "file" and I get the > message > > Text is read-only: # > > That is not a bug. It is also not pretty. > You are right after the prompt: `Find file: '. `backward-kill-word' > kills the preceding word, in this case `file: '. Of course, `file: > ' is read-only, so it can not be deleted. But it is copied to the > kill ring, which in certain situations could be useful. The cursor > moves to the `f' to allow a following `backward-kill-word' to > prepend `Find ' to the kill-ring entry, which would then be `Find > file: '. > > See `(emacs)Killing' for details. Perhaps we should not move the cursor when "killing" readonly material? It would have the disadvantage that using kill-word three times will not copy three words into the kill buffer, but I don't think that killing readonly text is used so often that we need to provide this sort of "convenience". If we signal an error, I don't think we should really move point, either. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum