gergely/taskwarrior-2.x
1
0
Fork 0
Code Issues Actions Packages Projects Releases 1 Wiki Activity

Regex

Browse Source 
- Removed references to rc.regex in the man pages.
This commit is contained in:
Paul Beckingham
2011-02-11 11:12:43 -05:00
parent 1e2b551795
commit bc5cdfecb4
2 changed files with 0 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/man/task-faq.5.in
View File

@@ -300,26 +300,6 @@ non-exact match:
This will remove the second annotation - the first non-exact match. This will remove the second annotation - the first non-exact match.
.TP
.B Q: Does task support searching using regular expressions?
Yes, taskwarrior supports IEEE Std 1003.2 (POSIX.2) regular expressions, but not
by default. You must enable this feature with the following command:
$ task config regex on
Once enabled, all searches are considered regular expressions, for example:
$ task list ^the
will list all tasks whose description or annotations start with "the".
Substitutions also support regular expressions:
$ task 1 /^the/The/
Note that regular expressions work in conjunction with the
.B search.case.sensitive
configuration setting.
.TP .TP
.B Q: Why Lua as an extension language? .B Q: Why Lua as an extension language?
Lua has many positive attributes: Lua has many positive attributes:

9
doc/man/taskrc.5.in
View File

@@ -269,15 +269,6 @@ names you have used, or just the ones used in active tasks. The default value i
May be yes or no, and determines whether keyword lookup and substitutions on the May be yes or no, and determines whether keyword lookup and substitutions on the
description and annotations are done in a case sensitive way. Defaults to yes. description and annotations are done in a case sensitive way. Defaults to yes.
.TP
.B regex=on
Enables regular expression searches in filters (task list ^Fix), and
substitutions (task <id> /^the/The/).
Note that this feature works in conjunction with the
.B search.case.sensitive
setting.
The default value is off, because this advanced feature could cause confusion The default value is off, because this advanced feature could cause confusion
among users that are not comfortable with regular expressions. among users that are not comfortable with regular expressions.