[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: Benno Schulenberg
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 20:09:43 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1

Op 09-01-19 om 02:19 schreef David Ramsey:
> What I want to know is, given your comments, how far do we go
> with breaking away from Pico?

Just the small things needed to make nano a general, sensible editor.

Pico's purpose was to compose emails.  But nano is mostly used as an
editor of config files.  For such an editor it is not sensible to
hard-wrap lines by default at screen width minus eight columns.  For
most people scrolling per half-screen is disorienting, or the cursor
not coming back to the same place after a PageDown plus PageUp.  So,
in such things nano should behave in a sensible way by default, and
not stick to whatever Pico did.

Nano doesn't follow Pico's behavior in the Replacing menu, nor its
Tab-completion-of-filenames behavior, nor its spell-checking behavior,
nor in a few other things, 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.

But the basic keybindings (^X for exit, ^W for search, etcetera) are
not going to change, nor the peculiar manner of cutting (per full line
and cumulative).  Regular users of nano are too used to those.


Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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