From 9dad3721a9535b6ae864cbc5f70eda92d3ac02ca Mon Sep 17 00:00:00 2001 From: Wayne Davison Date: Sun, 4 Jul 2021 12:42:51 -0700 Subject: [PATCH] Make whole-line comments clearer. --- rsync.1.md | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) diff --git a/rsync.1.md b/rsync.1.md index ec55a688..24457b2b 100644 --- a/rsync.1.md +++ b/rsync.1.md @@ -2049,9 +2049,11 @@ your home directory (remove the '=' for that). 0. `--exclude-from=FILE` This option is related to the `--exclude` option, but it specifies a FILE - that contains exclude patterns (one per line). Blank lines in the file and - lines starting with '`;`' or '`#`' are ignored. If _FILE_ is '`-`', the - list will be read from standard input. + that contains exclude patterns (one per line). Blank lines in the file are + ignored, as are whole-line comments that start with '`;`' or '`#`' + (filename rules that contain those characters are unaffected). + + If _FILE_ is '`-`', the list will be read from standard input. 0. `--include=PATTERN` @@ -2064,9 +2066,11 @@ your home directory (remove the '=' for that). 0. `--include-from=FILE` This option is related to the `--include` option, but it specifies a FILE - that contains include patterns (one per line). Blank lines in the file and - lines starting with '`;`' or '`#`' are ignored. If _FILE_ is '`-`', the - list will be read from standard input. + that contains include patterns (one per line). Blank lines in the file are + ignored, as are whole-line comments that start with '`;`' or '`#`' + (filename rules that contain those characters are unaffected). + + If _FILE_ is '`-`', the list will be read from standard input. 0. `--files-from=FILE` @@ -3501,8 +3505,9 @@ available rule prefixes: 0. `risk, 'R'` files that match the pattern are not protected. 0. `clear, '!'` clears the current include/exclude list (takes no arg) -When rules are being read from a file, empty lines are ignored, as are comment -lines that start with a "#". +When rules are being read from a file, empty lines are ignored, as are +whole-line comments that start with a '`#`' (filename rules that contain a hash +are unaffected). [comment]: # (Remember that markdown strips spaces from start/end of ` ... ` sequences!) [comment]: # (Thus, the `x ` sequences below use a literal non-breakable space!) -- 2.47.2