[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: comment bug
Re: comment bug
Sat, 26 May 2018 20:57:53 +0200
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
Am 26.05.2018 um 20:15 schrieb bb:
On top of the code snippet you have the version number. If one starts
the code, I get an unexpected but descriptive error message. Something
Strictly speaking, yes.
You expect people to copy your code example and execute it in LilyPond,
without giving a hint on why you sent it. Actually this should prevent
anyone to even bother with the post.
But that set aside the undescribed code example doesn't expose a bug. So
one is initially left with alone figuring out what you mean.
I do not need any help with this, I have some experience with
programming languages and can live with this behaviour.
I think it is a good idea to mention in the manual not to nest comments
(for non-programmers). It's just a suggestion, not an impolite ultimate
demand. If you think that hint is not needed, it's ok.
That is not what I said.
I would say that it *is* a good idea to explicitly repeat the fact of
the non-nestedness in the Notation Reference. But let me show you how an
appropriate "bug report" might have looked like. What you could have
written is something along the lines of:
"As you can see from the following MWE LilyPond doesn't seem to support
nested multiline comments. However, since some languages do so and
others don't I think it would be good to explicitly mention that fact in
section 3.1.5 of the Notation Reference. An option would be to add the
following sentence after ...: ..."
Rushing ahead with unsolicited claims and no politeness won't get you
very far in the community. Then acting offended and claiming that your
suggestions are being ignored, doesn't help either.