On Sat, 24 Nov 2012, david at tethera.net wrote: > From: Jani Nikula <jani at nikula.org> > > --- > man/man1/notmuch-tag.1 | 52 > +++++++++++++++++++++++++++++++++++++++++++++++- > 1 file changed, 51 insertions(+), 1 deletion(-) > > diff --git a/man/man1/notmuch-tag.1 b/man/man1/notmuch-tag.1 > index 0f86582..751db7b 100644 > --- a/man/man1/notmuch-tag.1 > +++ b/man/man1/notmuch-tag.1 > @@ -4,7 +4,12 @@ notmuch-tag \- add/remove tags for all messages matching the > search terms > > .SH SYNOPSIS > .B notmuch tag > -.RI "+<" tag> "|\-<" tag "> [...] [\-\-] <" search-term ">..." > +.RI "+<" tag ">|\-<" tag "> [...] [\-\-] <" search-terms ">" > + > +.B notmuch tag > +.RI "--batch" > +.RI "[ --input=<" filename "> ]" > + > > .SH DESCRIPTION > > @@ -29,6 +34,51 @@ updates the maildir flags according to tag changes if the > configuration option is enabled. See \fBnotmuch-config\fR(1) for > details. > > +Supported options for > +.B tag > +include > +.RS 4 > +.TP 4 > +.BR \-\-batch > + > +Read batch tagging operations from standard input. This is more > +efficient than repeated > +.B notmuch tag > +invocations. See > +.B TAG FILE FORMAT > +below for the input format. This option is not compatible with > +specifying tagging on the command line. > +.RE > + > +.RS 4 > +.TP 4 > +.BR "\-\-input=" <filename> > + > +Read input from given file, instead of from stdin. Implies > +.BR --batch . > + > +.SH TAG FILE FORMAT > + > +The input must consist of lines of the format: > + > +.RI "T +<" tag ">|\-<" tag "> [...] [\-\-] <" search-terms ">"
I think we should replace "<search-terms>" with "<search-term> [...]", and ditch the plural below... > + > +Each line is interpreted similarly to > +.B notmuch tag > +command line arguments. The delimiter is one or more spaces ' '. Any > +characters in <tag> and <search-terms> > +.B may > +be hex encoded with %NN where NN is the hexadecimal value of the > +character. Any ' ' and '%' characters in <tag> and <search-terms> > +.B must > +be hex encoded (using %20 and %25, respectively). Any characters that ...so it would make the above description more accurately depict reality. We don't care about hex encoding spaces between individual search terms. BR, Jani. > +are not part of <tag> or <search-terms> > +.B must not > +be hex encoded. > + > +Leading and trailing space ' ' is ignored. Empty lines and lines > +beginning with '#' are ignored. > + > .SH SEE ALSO > > \fBnotmuch\fR(1), \fBnotmuch-config\fR(1), \fBnotmuch-count\fR(1), > -- > 1.7.10.4