|
918 | 918 | must be passed as separate words). Lone semicolons may be escaped |
919 | 919 | as <literal>\;</literal>.</para> |
920 | 920 |
|
921 | | - <para>Each command line is split on whitespace, with the first |
922 | | - item being the command to execute, and the subsequent items being |
923 | | - the arguments. Double quotes ("...") and single quotes ('...') may |
924 | | - be used, in which case everything until the next matching quote |
925 | | - becomes part of the same argument. C-style escapes are also |
926 | | - supported. The table below contains the list of allowed escape |
927 | | - patterns. Only patterns which match the syntax in the table are |
928 | | - allowed; others will result in an error, and must be escaped by |
929 | | - doubling the backslash. Quotes themselves are removed after |
930 | | - parsing and escape sequences substituted. In addition, a trailing |
931 | | - backslash (<literal>\</literal>) may be used to merge lines. |
932 | | - </para> |
| 921 | + <para>Each command line is split on whitespace, with the first item being the command to |
| 922 | + execute, and the subsequent items being the arguments. Double quotes ("...") and single quotes |
| 923 | + ('...') may be used, in which case everything until the next matching quote becomes part of the |
| 924 | + same argument. Quotes themselves are removed. C-style escapes are also supported. The table |
| 925 | + below contains the list of known escape patterns. Only escape patterns which match the syntax in |
| 926 | + the table are allowed; other patterns may be added in the future and unknown patterns will |
| 927 | + result in a warning. In particular, any backslashes should be doubled. Finally, a trailing |
| 928 | + backslash (<literal>\</literal>) may be used to merge lines.</para> |
933 | 929 |
|
934 | 930 | <para>This syntax is intended to be very similar to shell syntax, |
935 | 931 | but only the meta-characters and expansions described in the |
|
0 commit comments