[Top][All Lists]

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

Re: address@hidden: C-k must be repeated in shell to kill a line that ha

From: Miles Bader
Subject: Re: address@hidden: C-k must be repeated in shell to kill a line that has a prompt]
Date: 01 Nov 2001 10:14:23 +0900

Richard Stallman <address@hidden> writes:
> Is it ever actually a desirable feature that plain C-k should notice
> field boundaries?  If not, changing it to ignore them is one possible
> approach.

A case in which C-k obeying field boundaries may be the right thing is a
form filling interface:

    TextTextText Prompt:   FFFFFFFFFFFFF    MoreTextMoreText

where FFFF... has a field property, and probably the rest of the text is
read-only.  Then it's natural to have C-a, C-e, C-k, etc., operate only
on the input field (it's the way customize works, anyway, and seems
pretty nice to me).

> the fields used in comint have `inhibit-line-move-field-capture'
> properties which prevent next-line and previous-line from treating
> these fields specially.  Perhaps beginning-of-line and end-of-line
> should also check this property.  Then the fields used in comint would
> have no effect on ordinary cursor motion at all.
> Meanwhile, I think we should rename that property to something shorter
> and more natural, like `field-natural-motion'.

I presume you mean the _output_ fields (if none of the fields had any
effect, there wouldn't be much point to them!)....

I'll look at whether that could be made to work.

[|nurgle|]  ddt- demonic? so quake will have an evil kinda setting? one that 
            will  make every christian in the world foamm at the mouth? 
[iddt]      nurg, that's the goal 

reply via email to

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