[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] Comment/Uncomment feature patch
From: |
Benno Schulenberg |
Subject: |
Re: [Nano-devel] Comment/Uncomment feature patch |
Date: |
Sat, 21 May 2016 10:32:56 +0200 |
On Fri, May 20, 2016, at 13:40, Mike Scalora wrote:
> On Thu, May 19, 2016 at 1:15 PM, Benno Schulenberg
> <address@hidden> wrote:
> > But you can easily do without colors (that is: syntaxes); it will
> > cost one #ifndef.
>
> I could do that, then one can --disable-color by itself and keep
> commenting with only '#'.
And even with --disable-nanorc.
> Does anyone ever use all the possible odd
> build combinations unless it is a platform/library limitation?
Probably not. But at least there are people who use
--disable-libmagic and --disable-justify. And probably
there are some that use --disable-color.
> > But now that I think about it: what would be really cool is if we
> > could bind this feature to a single key instead of to two: when all
> > the marked lines are commented, then they are uncommented;
> > otherwise, they are commented. [...]
>
> It has pros and cons, I've used editors in my day job that work both
> ways. Two keys are easier to know what will happen.
True. You make me hesitate... a little.
> JetBrains IDEs and BBEdit on the Mac use one key, Command-/ or Ctrl-/.
> JetBrains comments unless ALL of the non-empty lines are commented,
> then it uncomments.
That sounds like the correct method.
> A single key would take more code, the amount depending on the
> heuristic. How many lines of code have the same value as an unused
> keystroke?
Fifty lines. :)
Benno
--
http://www.fastmail.com - IMAP accessible web-mail
- Re: [Nano-devel] Comment/Uncomment feature patch, (continued)
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Scalora, 2016/05/17
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Frysinger, 2016/05/17
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Scalora, 2016/05/17
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Frysinger, 2016/05/17
- Re: [Nano-devel] Comment/Uncomment feature patch, Benno Schulenberg, 2016/05/18
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Scalora, 2016/05/18
- Re: [Nano-devel] Comment/Uncomment feature patch, Benno Schulenberg, 2016/05/19
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Scalora, 2016/05/19
- Re: [Nano-devel] Comment/Uncomment feature patch, Benno Schulenberg, 2016/05/19
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Scalora, 2016/05/20
- Re: [Nano-devel] Comment/Uncomment feature patch,
Benno Schulenberg <=
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Scalora, 2016/05/20
- Re: [Nano-devel] Comment/Uncomment feature patch, Benno Schulenberg, 2016/05/21
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Scalora, 2016/05/21
- Re: [Nano-devel] Comment/Uncomment feature patch, Benno Schulenberg, 2016/05/21
- Re: [Nano-devel] Comment/Uncomment feature patch, Mike Scalora, 2016/05/22
- [Nano-devel] getting ready to merge the Comment/Uncomment feature, Benno Schulenberg, 2016/05/22
- Re: [Nano-devel] getting ready to merge the Comment/Uncomment feature, Mike Scalora, 2016/05/22
- Re: [Nano-devel] getting ready to merge the Comment/Uncomment feature, Benno Schulenberg, 2016/05/25
- Re: [Nano-devel] Comment/Uncomment feature patch, Benno Schulenberg, 2016/05/19
- Re: [Nano-devel] Comment/Uncomment feature patch, Benno Schulenberg, 2016/05/15