[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: David Ramsey
Subject: Re: [Nano-devel] [PATCH 1/2 V3] cutting: when ^K does not actually cut anything, do not add an undo item
Date: Wed, 2 Jan 2019 14:22:37 -0600

Benno Schulenberg:
> If that is what filebot is for, then I am all for getting rid of it.
> It will save us the trouble of keeping the thing in sync.

You'll effectively replace it with the trouble of having to loop to the
end of the buffer in a lot of spots where the last line of the file
needs to be quickly accessible.  That will affect performance and add a
lot more lines of code.  Calculating the cursor position; word counting;
a few parts of the undo code, etc....

It's not a simple thing like removing editbot (as was done years ago),
since the bottom of the edit window isn't used very often.

> If the user has truly forgotten that the mark is on, then cutting
> *nothing* when the user types ^K is majorly unexpected.

Trying to guess what the user wants when it comes to destructive things
like cutting is a bad idea; cutting nothing is the least destructive
option.  Or at least have some other visual indicator that the mark is

> We're leaving Pico behind.  Or rather: we've left Pico behind long
> ago. We took from Pico what was good, and tried to improve where it
> wasn't.

And how far do we go with that?  Nano is still called "an enhanced free
Pico clone".  If we diverge enough from it, that's no longer true.  I
still like most Pico behavior enough to go with it; am I the only one?

reply via email to

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