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

[markweston]

> > Didn't check the mailbox before sending the patch.
> > I didn't expect you to work on the patch for me,
>
> You hadn't responded for a whole week, and I want to get this thing
> in before the next release.

What's the hurry?
I'm the only one who wants this feature.
It's not going to affect anyone else.

> > What do you mean unlikely?
> > You're the guy who makes the decisions.
>
> Yes, but if several people say they want this particular Ctrl+Down
> behavior, then I might reconsider.

Why did you accept the new optional Ctrl+Right behaviour?
I am the only person who wants that.
Nobody else was bothered to send a patch or ask.

> > > I think there is no need for making Ctrl+Down go to the first
> > > blank line after a block of text.
> >
> > 1. I want to be able to easily navigate to any block beginning/end 
> > just like I want
> > to easily navigate to any word beginning/end. With previous nano 
> > behaviour, I had to
> > mash Left/Up key several times to get to the end of a word/block.
> > With previous behaviour of nano, I have to mash the Up button until I 
> > get there.
>
> How many blank lines do you have between blocks of text?

Two.

> > 2. I want to do operations (cut, copy, duplicate, delete, comment-out,
> > (de)indent, etc...)
> > on a block basis, not on a block+whitespace basis.
>
> You have just convinced me that the current behavior for Ctrl+Down 
> shouldn't
> change.  Because: if I want to cut or move a block, I want the 
> succeeding
> blank line to be included, otherwise it would double the blank line at 
> the
> place where I cut and I'd have to hit <Enter> at the place where I 
> paste.

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

Yes you have to hit <Enter> once, big deal.
In return, you don't have to mash <Up> to get to the end of the block.
You need to hit <Enter> only once and <Enter> is a big key on all 
keyboards.
You need to mash <Up> twice and arrow keys are super small on new
laptop keyboards.
See attached image.

> > Do you want me to send a big patch with all the changes or
> > do you want me to send an incremental patch that targets nano
> > with with this patch already applied?
> The latter, of course.  As said before: it should be a separate patch.
> So, better wait for --afterends to be merged first, in a day or two.

Fine.
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 think I could send a patch that converts it into a char array.
56 additional bytes of RAM won't hurt anybody.