Search tasks by text within annotation files

[dbogdanov]

It may be useful to expand Taskwarrior search functionality to the notes created with taskopen.

For example,

taskopen --search /Text to search/  

could output all matching tasks, and offer to open one of them.

[jschlatow]

This can probably be solved by an external script and the new filter command hook.

[miguelpduarte]

@dbogdanov I managed to get a simple version of this concept working using ripgrep - although I'm sure good old grep would work just fine.

Demo:

~
$ cat ~/tasknotes/2f7ebc61-7ed9-46ed-b832-8fab271e6ecb.md
* [ ] Track bugwarrior.toml maybe  #2f7ebc61-7ed9-46ed-b832-8fab271e6ecb

We dont have that text here

~
$ cat ~/tasknotes/7f445bef-4fbe-4fae-9f4c-0141eaa2aba6.md
* [ ] Fix bugwarrior interaction with DB somehow  #7f445bef-4fbe-4fae-9f4c-0141eaa2aba6


CANARY is here


~
$ taskopen -- --include=finder
~/tasknotes/7f445bef-4fbe-4fae-9f4c-0141eaa2aba6.md matched text - ID is 4

This is the action definition:

finder.target = annotations
finder.regex="Notes"
finder.filtercommand="rg CANARY --files-with-matches ~/tasknotes/$UUID.md"
finder.command="echo ~/tasknotes/$UUID.md matched text - ID is $ID"

This is matching the hardcoded string of CANARY but I suppose that there might be a way to specify the text to filter by. I saw that there's $ARGS but this seems to only take the commandline arguments for the whole prompt 😅
But at the very least this could be a starting point 😁

(Also the weirdness with the extra -- is probably due to something broken in my setup as I'm messing with some configs about default arguments which might have broken something)

[jschlatow]

@miguelpduarte Thanks for sharing. Note that any additional argument provided to taskopen is passed to taskwarrior as a filter. In order to provide a search string solely for "grepping" you may use the --args argument whose value will be made available in the $ARGS environment variable.