[Top][All Lists]

[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.  :)


-- - IMAP accessible web-mail

reply via email to

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