[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Just a thought about comment-line
From: |
Drew Adams |
Subject: |
RE: Just a thought about comment-line |
Date: |
Sun, 31 May 2020 14:54:15 -0700 (PDT) |
> > You're fairly sure for whom? For you? Not for me.
>
> The only complaints against comment-dwim I have seen
I wasn't complaining about `comment-dwim'.
I was saying that it's not the be-all and
end-all. I use it for end-of-line comments.
And I use something else for block commenting.
It doesn't matter to me if you use `M-;' for
everything. If you're happy that way, great.
> were along the lines "I want to micromanage
> how comments are made",
I see. If someone says your one-size-fits-all
dream command doesn't fit all then their idea
for doing something additional or different
just wastes your time. Sorry to hear that.
> and not "this code-writing scenario becomes
> suboptimal".
>
> Are you still writing code? I'm surprised,
Surprise! And irrelevant.
> > Tell me why Common Lisp behavior for block comments
> > (#|...|#) is missing? I don't mean that those macro
> > chars are missing, but that the block-commenting
> > behavior (nesting, unnesting) is missing.
>
> You might want to elaborate.
I think I did. Maybe you can show us how
`comment-dwim' provides the same behavior.
> It definitely can create nested comments (i.e. in
> the cases they are really needed, when you call it
> on a region containing both commented and
> non-commented lines).
A bit of a tautology. I can leap over buildings
in a single bound, in the cases where that's
really needed, which is when the buildings are
at most 1-foot tall.
Anyway. The point of this thread is the problem
with `comment-line' raised by the OP. If you're
curious why `comment-line' was added, since we
already had `comment-dwim', see the thread I
pointed to, where `comment-line' was discussed
and added.
Re: Just a thought about comment-line, Eli Zaretskii, 2020/05/31
RE: Just a thought about comment-line, Drew Adams, 2020/05/31