gui, man, authors: Update docs, translations, and contributors

This commit is contained in:
Jakob Borg
2020-04-15 07:45:24 +02:00
parent 81ff31b8fc
commit 41ef945b2b
45 changed files with 72 additions and 39 deletions
+6 -2
View File
@@ -1,6 +1,6 @@
.\" Man page generated from reStructuredText.
.
.TH "SYNCTHING-STIGNORE" "5" "Apr 06, 2020" "v1" "Syncthing"
.TH "SYNCTHING-STIGNORE" "5" "Apr 14, 2020" "v1" "Syncthing"
.SH NAME
syncthing-stignore \- Prevent files from being synchronized to other nodes
.
@@ -82,7 +82,7 @@ separator. \fBte??st\fP matches \fBtebest\fP but not \fBteb/st\fP or
.IP \(bu 2
Characters enclosed in square brackets \fB[]\fP are interpreted as a character range \fB[a\-z]\fP\&. Before using this syntax you should have a basic understanding of regular expression character classes.
.IP \(bu 2
A pattern beginning with \fB/\fP matches in the current directory only.
A pattern beginning with \fB/\fP matches in the root of the folder only.
\fB/foo\fP matches \fBfoo\fP but not \fBsubdir/foo\fP\&.
.IP \(bu 2
A pattern beginning with \fB#include\fP results in loading patterns
@@ -125,6 +125,10 @@ single pair of parentheses (not “(?di)”).
Include patterns (that begin with \fB!\fP) cause Syncthing to traverse and
watch the entire directory tree regardless of other
ignore patterns.
.sp
Top\-level include patterns are treated as special cases and will not force Syncthing to
scan the entire directory tree. For example: \fB!/foo\fP is a top\-level include
pattern, while \fB!/foo/bar\fP is not.
.UNINDENT
.UNINDENT
.SH EXAMPLE