[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Doc: Usage 1.2 - Added note about using wildcards (issue 151920044 by ad
From: |
dak |
Subject: |
Doc: Usage 1.2 - Added note about using wildcards (issue 151920044 by address@hidden) |
Date: |
Wed, 01 Oct 2014 10:08:25 +0000 |
https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):
https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.itely#newcode103
Documentation/usage/running.itely:103: Many standard @q{shell} commands
can be used alongside LilyPond.
You don't list any actual shell commands but rather make use of shell
*features*.
It's more like
Since LilyPond is a command line application, features of the
@q{shell} used for calling LilyPond can also be put to good use.
https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.itely#newcode127
Documentation/usage/running.itely:127: terminal application to see if
output @q{redirection} is supported or if
The terminal application usually is not involved with output redirection
even though there are some with the capacity of creating a session log.
But that's not for individual commands then. So I'd remove the
"terminal application" here.
https://codereview.appspot.com/151920044/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Doc: Usage 1.2 - Added note about using wildcards (issue 151920044 by address@hidden),
dak <=