This plugin finds notes and to-dos without a tag and tags them with a configurable tag. The plugin will also automatically remove the given tag if another tag is added to that note or to-do. Settings options allow you to set the name of the tag for untagged notes (eg."Untagged", "Not Tagged", "Inbox", "Uncategorised", etc). A setting option also exists to enable or disabling the removal of the untagged tag for notes that has been tagged with a separate tag.
Installation
Untagged can be installed from within Joplin by navigating to the plugins page in the settings menu then searching for and installing "Untagged"
Does it take a certain time before it finds an untagged note? It found one from several days ago, but is not finding a test one that I created. I've restarted Joplin a few time to no avail.
It should find it near instantaneously, At least within a few seconds, though it does take a while to iterate through each untagged note, maybe 1 per second. Are you sure the test note contains no tags at all?
Deleting the untagged tag sort of helped. It did find the test note that it couldn't find before. However, the name of the tag is strange: >>71557>>untagged<<71557<<. Also, it still doesn't find any new untagged notes I create.
That code triggers if it tries to create the untagged tag and it already exists. You would then rename it to something else. But tomorrow after I get some sleep, ill get rid of the hardcoded tag ID and tag names to keep track of which tag to assign to untagged notes.
Strange, indeed. I just tried installing it again, and got the same problem. It wouldn't have anything to do with another plugin, would it? I do have most plugins installed.
Hmm, im not sure. My suspicion is that those noteshave another tag or for some reason, arent showing up in the "notes without a tag" search that untagged uses
When I enable this plugin, Joplin takes ~98% of my CPU constantly. I have tried all the plugins one by one (i.e disabled all and gradually enabled them) and I am positive that this plugin is the cause...
Could this be in connection with the aforementioned search-loop that is constantly runnig?
Also, does anyone have an idea how this plugin arrived at a version of 2.0.1 (the second highest of all plugins) in just 16 days since creation?