nano-devel
[Top][All Lists]
Advanced

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

Re: [Nano-devel] [PATCH] add an "afterends" configuration setting


From: Benno Schulenberg
Subject: Re: [Nano-devel] [PATCH] add an "afterends" configuration setting
Date: Wed, 9 May 2018 10:44:25 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

Op 08-05-18 om 15:12 schreef address@hidden:
> What's the hurry?

Schedules.  No available time later.

> I'm the only one who wants this feature.

*I* want this feature.  And I'm certain Mike Frysinger wants this
feature.  And most likely several other people want this feature
too, because it is the way readline behaves, it is what they are
used to from the command line.

> Why did you accept the new optional Ctrl+Right behaviour?
> I am the only person who wants that.

Already answered.

> Nobody else was bothered to send a patch or ask.

That nobody asks or sends a patch means little.  The <Enter> key
scrolling half a screen (when pressed on the bottom line even when
--smooth is used) has annoyed me for fourteen years.  Only this year
I thought about proposing to change the behavior, and changed it.
(Or no, I thought about proposing it several times before, but then
always something else demanded attention.)

>> How many blank lines do you have between blocks of text?
> 
> Two.

Text or code?  Because if it is text, you could try the paragraph
jumping commands: M-9 and M-0.

> Then don't use this setting like you and everyone else hasn't been using
> for all the time nano has existed?

But I want the changed Ctrl+Right behavior.  But not a changed Ctrl+Down
behavior.  And I don't want two settings, because that's ugly.

Also, Ctrl+Left and Ctrl+Right work in nano since just three years (2.4.0).
Most likely most users of nano don't even know that these keystrokes work
now.

If you want a changed Ctrl+Down behavior so badly: you know how to
modify nano.  I've used a custom nano for years.

> I still don't understand why you said you wouldn't accept two options instead.
> "afterwordends" and "afterblockends" would keep us both satisfied.
> Are you saving the 64 configuration flag bits?

I don't care about the bits.  It's easy enough to extend.  And I've
thought about making it a byte per flag: to make it faster.

Now the question: are you okay with the v6 version of the patch that
I posted?

Benno

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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