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

[markweston]

> Hmm.  It would have been better if you had used my version of the patch
> as a base, to improve upon.

Didn't check the mailbox before sending the patch.
I didn't expect you to work on the patch for me, only to merge/reject 
it.

> You left out several improvements that I
> made: adding the option to the nano.1 manpage, better comments, the
> standard "TRUE" instead of "true", ...

I fixed the five things you asked me to fix.
If you listed more I would have fixed those too.

> > > And it leaves it open whether this option will apply to
> > > Ctrl+Down too later on.
> >
> > So now I have to send a new patch
>
> You don't have to send anything.  Also because it is unlikely to get
> accepted:

What do you mean unlikely?
You're the guy who makes the decisions.

> 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.
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. Just like I want to 
do operations
(cut/copy/delete) on a word basis, not on a word + whitespace basis.
3. It's just intuitive because it follows the same logic.

> Also: Geany does not do that either.
> Is there any other editor that does this?

I'll check it out.


> > that expands the "afterends" behaviour
> > to Ctrl+Down and Shift+Ctrl+Down,
>
> Yes, *if* anything, then this.
>
> > or should I rename this to "afterwordends"
> > and send a new patch that introduces "afterblockends" option?
>
> Certainly not.

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?