[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

`kill-line' confused by fields in Shell mode.

From: Richard Stallman
Subject: `kill-line' confused by fields in Shell mode.
Date: Sun, 25 Mar 2007 23:52:56 -0400

The direct cause of this problem is that yank-excluded-properties
includes `field'.  But I am not sure what the solution should be.
I don't think we should change this now, but it seems clear
we need a different mechanism here.  What should it be?

Date: Thu, 22 Mar 2007 08:49:14 +0100
From: "Chris Moore" <address@hidden>
To: "Miles Bader" <address@hidden>
Cc: address@hidden
Subject: Re: `move-beginning-of-line' doesn't move to beginning of line

A similar problem exists with the command kill-line.

The documentation tells me:
  "Kill the rest of the current line"

However, in a *shell* buffer, if I:

$ echo aa RET
$ echo bb RET
C-p C-a C-k               (go to the line with the 'bb' on it and kill it)
C-p C-p C-y               (go to the line with the 'aa' on it and yank the 'bb')
C-a                           (go to the start of the line with 'bbaa' on it)
C-k                           (kill the rest of the line with 'bbaa' on it)

then only the 'bb' is killed.  the 'aa' is on the same line, after the
cursor, but it isn't killed.  The line looks like a regular
4-character line, the cursor is at the beginning of it, yet C-k only
kills half of the line.

Maybe it's useful to have an invisible field in the bottom line of a
*shell* buffer to allow the prompt to behave differently that the
editable command, but once a command has been run these invisible
fields don't seem to server any purpose other than to stop regular
editing commands from working as documented.

Am I missing something?

emacs-pretest-bug mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]