[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Doc: Usage 1.2 - Added note about using wildcards (issue 151920044 b

From: pkx166h
Subject: Re: Doc: Usage 1.2 - Added note about using wildcards (issue 151920044 by address@hidden)
Date: Wed, 01 Oct 2014 10:42:55 +0000

Reviewers: dak,
File Documentation/usage/running.itely (right):
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

Terminal Application is what it is called (or 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.

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'

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

Please review this at

Affected files (+20, -14 lines):
  M Documentation/usage/running.itely

Index: Documentation/usage/running.itely
diff --git a/Documentation/usage/running.itely b/Documentation/usage/running.itely index 0bff8f68df9636786d7eed1e0fdf43b83b8e4ea2..49d5178b3e6325a7da6e5b41e6d2020b86bb2bea 100644
--- a/Documentation/usage/running.itely
+++ b/Documentation/usage/running.itely
@@ -100,26 +100,32 @@ will output @address@hidden and

 @unnumberedsubsubsec Standard shell commands

-If your shell (i.e. command window) supports normal redirects,
-then you might find it useful to use the following commands to
-redirect console output to a file:
+Many standard @q{shell} commands can be used alongside LilyPond.

+For example:

address@hidden 1>stdout.log} to redirect normal output
+lilypond *.ly
address@hidden example

address@hidden 2>stderr.log} to redirect error messages
+will process all LilyPond files in the current directory.

address@hidden &>all.log} to redirect all output
+Redirecting the console output (e.g. to a file) may also be useful:

address@hidden itemize
+lilypond 1> stdout.txt
+lilypond 2> stderr.txt

-Consult the documentation for your shell to see if it supports these
-options, or if the syntax is different.  Note that these are shell
-commands and have nothing to do with lilypond.
+lilypond &> all.txt
address@hidden example
+Redirects normal output, errors only or everything, respectively, to a
+text file.  Consult the documentation for your shell, cmd window or
+terminal application to see if output @q{redirection} is supported or if
+the syntax is different.

 @node Basic command line options for LilyPond

reply via email to

[Prev in Thread] Current Thread [Next in Thread]