Doc: Usage 1.2 - Added note about using wildcards

Doc: Usage 1.2 - Added note about using wildcards

Added note about being able to use wildcards with the
LiltPond command in the 'Stndard shell commands'
section.

Changed some of the text for Windows and MacOS users
who may not know what a 'shell' is to relfect each
OS's nomenclature.

[dak, 2014-10-01 10:08:25]

https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.i...
File Documentation/usage/running.itely (right):

https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.i...
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.i...
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.

[pkx166h, 2014-10-01 10:42:56]

https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.i...
File Documentation/usage/running.itely (right):

https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.i...
Documentation/usage/running.itely:127: terminal application to see if output
@q{redirection} is supported or if
On 2014/10/01 10:08:25, dak wrote:
> 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.

Terminal Application is what it is called (or Terminal.app) on MacOS. I am
assuming that users who are *NIX or BSD based will probably not need much
educating on 'shells', but more likely for the Windows or MacOS users. In the
latter case, there is no 'shell' application or 'command' window (again it
depends on the user's ability to deduce I suppose), so Terminal in this sense
isn't 'Terminal' in the *NIX sense.

Unless someone from the MacOS world can correct me - it's been a few years since
I used MacOS.

[pkx166h, 2014-10-02 07:18:22]

Using David K's suggestions

[pkx166h, 2014-10-02 07:24:08]

Thanks David.

https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.i...
File Documentation/usage/running.itely (right):

https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.i...
Documentation/usage/running.itely:103: Many standard @q{shell} commands can be
used alongside LilyPond.
On 2014/10/01 10:08:25, dak wrote:
> 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.

Done.

https://codereview.appspot.com/151920044/diff/1/Documentation/usage/running.i...
Documentation/usage/running.itely:127: terminal application to see if output
@q{redirection} is supported or if
On 2014/10/01 10:08:25, dak wrote:
> 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.

I reworded this similar to a section near the beginning of this *.tely file
where we also reference Windows and MacOS X users.

[pkx166h, 2014-10-09 16:17:51]

author	James Lowe <pkx166h@gmail.com>	
	Wed, 1 Oct 2014 07:10:53 +0000 (08:10 +0100)
committer	James Lowe <pkx166h@gmail.com>	
	Thu, 9 Oct 2014 16:16:28 +0000 (17:16 +0100)
commit	0877e9d2844c470e37e3e97e4384652e605fcebc