[Top][All Lists]

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

Re: [Nano-devel] [PATCH 1/2 V3] cutting: when ^K does not actually cut a

From: Brand Huntsman
Subject: Re: [Nano-devel] [PATCH 1/2 V3] cutting: when ^K does not actually cut anything, do not add an undo item
Date: Wed, 9 Jan 2019 18:51:58 -0700

On Wed, 9 Jan 2019 14:47:14 -0600
David Ramsey <address@hidden> wrote:

> > so why should it copy the marking behavior exactly?  Why "cut" an
> > invisible, empty region?  It doesn't actually cut anything: it
> > doesn't make sense.  
> If the mark is on, the text covered by the mark is cut.  If the mark
> is on but doesn't cover any text, no text is cut *because* no text is
> covered by the mark.  It makes perfect sense to me (and at least one
> non-programmer I ran it by).

I agree that cutting an empty region should _not_ cut the line. It is easy to 
miss key presses and having the line vanish and needing to undo alters your 
focus and wastes mental energy.

It would however be nice if the message also mentioned the mark had been unset, 
in the case of an empty region.

  "Nothing was cut -- Mark Unset"

That message would make it easy for both situations. If you wanted to cut the 
line, just press cut again. If you wanted to select and cut, just re-mark and 
try again.

reply via email to

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