Graham Percival-3 wrote: > > On Thu, Apr 12, 2012 at 04:35:51PM +0100, Colin Hall wrote: >> I envisage users unfamiliar with command line quoting on Windows >> wasting a lot of time on this. There is sufficient material here for a >> documentation suggestion. If Eluze is happy to prepare one then I see >> no reason not to document this. > > We generally do not get into specifics of how to use the > command-line on specific OSes, but in this case I agree that it's > worth documenting it. To avoid confusing non-Windows users with > many windows details, we could put it in its own subsection, or > within a @knownissues, or something like that (with clear links, > of course). But the bottom line is that I agree that it's worth > having it in the docs somewhere. > > just a question: could we get rid of these -doptions?
since shortly at least 50% (or is it 80% ? ) can be defined directly in LilyPond without any loss of comfort/functionality - or do I overlook something? the advantage is clear: no more OS dependencies, same processing for every option and last but not least users can rely on the same pattern of input. now unluckily (most of) the options causing problems are not usable with an internal call, probably because they must be invoked before processing ly files: init, include-settings, log redefinition; and at the same time they involve a file name. I have verified that all options with file names work when enclosed in 4 double quotes. (convert-ly requires to enclose them in 3 double quotes…) I would like to know which options are important to keep in the -doption list (and what would be bad about having them only internally); e.g. is it important to rename/redirect the log to another file? for me personally the option include-settings is very important and I'd like to propose an upgrade to a basic option. please let me know your opinion - I would be happy to discuss and integrate it in these plans thanks! Eluze -- View this message in context: http://old.nabble.com/include-settings-and-path-or-file-name-with-blanks-tp33661145p33678336.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
