[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] [PATCH] add an "atends" configuration setting
From: |
Benno Schulenberg |
Subject: |
Re: [Nano-devel] [PATCH] add an "atends" configuration setting |
Date: |
Tue, 8 May 2018 10:49:14 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
Op 07-05-18 om 21:14 schreef address@hidden:
> 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 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.
>> 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?
> 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.
> Just like I want to do operations
> (cut/copy/delete) on a word basis, not on a word + whitespace basis.
Yes, I've noticed that with the --afterends behavior, marking and then
cutting words leaves the final whitespace in place. This is somewhat
annoying, but I'll live with it: I want the new Ctrl+Right behavior more.
> 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.
Benno
signature.asc
Description: OpenPGP digital signature
- Re: [Nano-devel] [PATCH] add an "atends" configuration setting, Benno Schulenberg, 2018/05/01
- Re: [Nano-devel] [PATCH] add an "atends" configuration setting, markweston, 2018/05/07
- Re: [Nano-devel] [PATCH] add an "atends" configuration setting, markweston, 2018/05/07
- Re: [Nano-devel] [PATCH] add an "atends" configuration setting, Benno Schulenberg, 2018/05/07
- Re: [Nano-devel] [PATCH] add an "atends" configuration setting, markweston, 2018/05/07
- Re: [Nano-devel] [PATCH] add an "atends" configuration setting,
Benno Schulenberg <=
- Re: [Nano-devel] [PATCH] add an "atends" configuration setting, markweston, 2018/05/08
- Re: [Nano-devel] [PATCH] add an "atends" configuration setting, markweston, 2018/05/08
- Re: [Nano-devel] [PATCH] add an "afterends" configuration setting, Benno Schulenberg, 2018/05/09
- Re: [Nano-devel] [PATCH] add an "afterends" configuration setting, markweston, 2018/05/09
- Re: [Nano-devel] [PATCH] add an "afterends" configuration setting, Benno Schulenberg, 2018/05/10
Re: [Nano-devel] [PATCH] add an "atends" configuration setting, Benno Schulenberg, 2018/05/07