Thank you for testing.
Any feedback is appreciated!
Wow, very impressive ![]()
UPDATE:
- add batch processing to add, delete or rename attributes of the tasks displayed in the list.
The list can be extracted with custom query clause and filtered before applying the treatment.
Syntax to define the order is simple: verb + ":" + name of attribute (value can be provide when adding) and "->" to rename. Please refer to the placeholder of the input.
This feature is experimental : use it with a copy of your documentary space. - add a custom where clause history
- the input box opens a menu with three action buttons: Filter | Query | Update.
- many improvements of the UI
why not make a library & repo for easier distribution. ?
I'm too lazy to copy all the files manually ![]()
i try to use Github (the first time for me!). So, i suppose i can distribute via share, library manager, etc ... in a few days !
Suggestion: in Github, Code / Download zip on the repository. Who can do more, little less!
It’s easy with a local installation, but with a remote server you have to manage access to the file system, which is more delicate and takes more time.
That’s also the reason why I haven’t tested it yet ![]()
Thank you for your comment. I assume it concerns reading the two text files (where-history.txt and where-examples.txt). Is that right?
If you think about reading the contents of the tasks (the list), I don't think there is a big problem in a network context because the queries are just querying the index. To compensate for possible slow startup, you can define a default query that runs when opened and possibly during resets (see Configuration).
On the other hand, you could indeed notice waiting time during batch processing (update) if the target concerns several hundred tasks.
Actaully I did not really check the github repo....
In fact I guess it would be ok to do it via the SB interface only, you're right and I guess that when not used to github it might be a pain to configure...
I'll give it a try soon in its actual state, thanks.
UPDATE 2026-02-11:
- share.uri: "silverbullet-libraries/TaskExplorer.md at main · Baudogit/silverbullet-libraries · GitHub"
- filter: negation operator ("-") added
- interface: some improvements (actions menu, ...)
- documentation: simplification
Thank you for testing and your comments !
Check my repository (scripts folder contains utilities to help you) or @Mr.Red's one to follow the official structure of your github repo.
After that it will be easy to install your future contributions.
ok thanks for the advice.
Initially, I did not plan to create a "Repository" (in the Silverbullet sense). For a single plugin, using a URI via the Share command seems sufficient. Is this incorrect?
I think. I will try.
UPDATE 2026-02-12:
- add new action: SORT the list by the VALUE of one or more attributes
- installation: where-examples.txt and where-history.txt are preserved
during subsequent updates
- documentation: actions are now grouped in a chapter
Command Library: Install
URI: https://github.com/Baudogit/silverbullet-libraries/blob/main/TaskExplorer.md
Thank you for testing.
Any feedback is appreciated!

