Re: comment bug

2018-05-26 Thread David Kastrup
bb writes: > The essential point: The case of nested block comments is not mentioned > in the manual. (Or I cannot find it?) > > # > > off topic: > > Have you heard about Lua? Nice language! > > |  print ("This will be printed first") >    >   --[===[ Comment out a

Re: comment bug

2018-05-26 Thread Urs Liska
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 unclear? Strictly speaking, yes. You expect people to copy your code example and execute it in LilyPond, without giv

Re: comment bug

2018-05-26 Thread bb
Sorry, I did not read the learning manual, I read the "normal" manual http://lilypond.org/doc/v2.19/Documentation/usage/invoking-convert_002dly.en.html and I found http://lilypond.org/doc/v2.19/Documentation/usage.pdf I actually searched for "nested" - no hit. Anyway, I know that everything is

Re: comment bug

2018-05-26 Thread bb
Sorry, I did not read the learning manual, I read the "normal" manual http://lilypond.org/doc/v2.19/Documentation/usage/invoking-convert_002dly.en.html and I found http://lilypond.org/doc/v2.19/Documentation/usage.pdf I actually searched for "nested" - no hit. Anyway, I know that everything is

Re: comment bug

2018-05-26 Thread bb
t;> The essential point: The case of nested block comments is not >> mentioned in the manual. (Or I cannot find it?) >> >> > > Maybe the essential point is to write properly to the (bug-lilypond) > when you want to get someone to do anything on your behalf. > > Your p

Re: comment bug

2018-05-26 Thread Sven Axelsson
On 26 May 2018 at 18:46, bb wrote: > The essential point: The case of nested block comments is not mentioned > in the manual. (Or I cannot find it?) > It most certainly is. Section 1.2.2 in the learning manual states that: "A block comment marks a whole section of music input as a comment. Anyt

Re: comment bug

2018-05-26 Thread Urs Liska
was titled "comment bug", with no further comment to it. And apart from being pretty impolite this is simply not accurate, much less a useful bug report. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/li

Re: comment bug

2018-05-26 Thread bb
Forgot Clojure, a wonderful modern functional language I recommend ;; comment can also be written as (comment …) (comment this is a block comment.   (comment block comment can be nested.) ) Am 26.05.2018 um 18:46 schrieb bb: > > The essential point: The case of nested block comments is not > men

Re: comment bug

2018-05-26 Thread bb
The essential point: The case of nested block comments is not mentioned in the manual. (Or I cannot find it?) # off topic: Have you heard about Lua? Nice language! |  print ("This will be printed first")      --[===[ Comment out a whole big block!      --[[ This

Re: comment bug

2018-05-26 Thread Urs Liska
Am 26. Mai 2018 17:43:19 MESZ schrieb Andrew Bernard : >Isn't it simply that you can't have nested block comments? I can't think of any language that allows nested multiline comments. Urs > >Andrew > > >On 27 May 2018 at 01:14, bb wrote: > >> >> \version "2.19.80" >> >> %{ >> \score { >> <<

Re: comment bug

2018-05-26 Thread Andrew Bernard
Isn't it simply that you can't have nested block comments? Andrew On 27 May 2018 at 01:14, bb wrote: > > \version "2.19.80" > > %{ > \score { > << > %{ > %some code > %} > >> > } > %} > > ___ bug-lilypond mailing list bug-lilypond@gnu.

comment bug

2018-05-26 Thread bb
\version "2.19.80" %{ \score  {   <<     %{     %some code     %}  >> } %} ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond