Updates:
Status: Verified
Comment #12 on issue 2090 by elu...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
(No comment was entered for this change.)
___
bug-lilypo
Comment #11 on issue 2090 by elu...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
I'm not worried about widows/orphans, I just wanted to point to the wrong
placement of the note which in the pdf case looks specially
Comment #10 on issue 2090 by pkx1...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
Patch has been pushed and fixed. Please open a new tracker if you think it
is important.
Also be careful about worrying where thing
Comment #9 on issue 2090 by elu...@gmail.com: Add documentation for command
line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
I'd put the note after the instruction:
…
at the top of the .ly file.
Note: Windows users must use double quotes instead of single quot
Updates:
Labels: Fixed_2_15_24
Comment #8 on issue 2090 by philehol...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
(No comment was entered for this change.)
___
b
Updates:
Status: Fixed
Labels: -Patch-push
Comment #7 on issue 2090 by pkx1...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
Wed, 21 Dec 2011 07:57:51 + (07:57 +)
commit f3a43f0e3bbec46b4b82b4b
Updates:
Labels: -Patch-countdown Patch-push
Comment #6 on issue 2090 by colinpkc...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
Counted down to 20111219, please push
___
Comment #4 on issue 2090 by julien.r...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
Re: please verify under Linux!
I tried on a few shells here and yes you can write -dpoint-and-click=#f as
well (without spaces!).
Updates:
Labels: Patch-review
Comment #3 on issue 2090 by lilypond...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090#c3
Patchy the autobot says: LGTM.
___
bug-lilypo
Updates:
Status: Started
Owner: pkx1...@gmail.com
Labels: Patch-new
Comment #2 on issue 2090 by pkx1...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
Patch uploaded:
http://codereview.appspot.c
Comment #1 on issue 2090 by elu...@gmail.com: Add documentation for command
line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
it seems that only this example (lilypond -e '(define-public a 42)')
requires quotes (-dpoint-and-click=#f can be written without quote
Am 09.12.2011, 10:23 Uhr, schrieb :
Command line quoting is properly documented here with an example of
quoting suitable for a UNIX shell:
http://lilypond.org/doc/v2.14/Documentation/usage/command_002dline-usage
It would be helpful for Windows users to have some guidance on proper
quoting
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2090 by colingh...@gmail.com: Add documentation for command line
quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
Eluze reported unexpected behaviour when using command line options under
Windows:
13 matches
Mail list logo
