Colin Hall-3 wrote > > >> >> "Must have Linux line endings" is not a mere "usage problem". > > Agreed. I was referring to the syntax of the "read-file-list" option > which was the topic of this bug report. > > You may have (understandably) confused this bug report with the fourth > of Eluze's recent bug reports relating to Windows command line usage. > >> But as long as Windows is a supported platform, a line-organised file >> needs to be able to contain platform-specific line endings. > > Totally agree. See issue tracker 2765 which I created earlier today. > > http://code.google.com/p/lilypond/issues/detail?id=2765 > >> And in any case: behavior that can only be figured out and interpreted >> by trial and error and code reading is, at the very least, a >> documentation issue. > > I agree. After a careful reading of: > > http://lilypond.org/doc/v2.15/Documentation/usage/command_002dline-usage > > I decided the documentation was correct, if a little lacking in > concrete examples, which at this point is good enough for me. > > If anyone would like to create a doc enhancement request I will be > happy to create a tracker for it. > >
I wonder if it's correct to have this option in "Advanced command line options for LilyPond". it rather seems an alternative to /lilypond [option]… file…/! if it's kept under advanced options, after "read-file-list #f [file] Specify name of a file which contains a list of input files to be processed." (new) "in contrast to other advanced options you must /not/ use an equal sign here! also, this file should have Linux line endings (i.e. LF instead of CRLF)." could be inserted. thanks Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/lilypond-dread-file-list-dows-not-produce-the-expected-output-tp130935p131030.html Sent from the Bugs mailing list archive at Nabble.com. _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
