Allow custom placement of global task filter string

[Gewerd-Strauss]

Hello,

I like the tasks-plugin, it is absurdly useful. However, I would love to specify the position of the task filter string, for me #task within the task text. I use the plugin within my daily notes often, but I would like to make it compatible to the day-planner plugin. Said plugin requires Todo's in the following structure (1):

- [ ] 21:00 Take out the Trash 

On the other hand, "Tasks" uses the format (2)

- [ ] #task Prime Time Show https://www.twitch.tv/SomeChannel 🔽 🔁 every week on Monday, Wednesday 🛫 2022-09-05

This could be combined for (3)

- [ ] 21:00 Prime Time Show https://www.twitch.tv/SomeChannel #task 🔽 🔁 every week on Monday, Wednesday 🛫 2022-09-05

so that f.e. Dayplanner could read the task correctly. My recommendation would be to simply move the identifier (#task) before the section of the string which contains the information for the plugin, as is done in (3). This would allow one to use the add-task-modal to simply enter a time at the beginning of the text to make it compatible.

Could this be implemented?

Thank you.
Sincerely,
~Gw

[claremacrae]

Hello @Gewerd-Strauss. How does this relate to #147?

Also, a bit of lateral thinking: do you put your #task tag on every single line with - [ ]? If so, there is no advantage in having a global filter at all, and you could just turn the global filter off and remove all the #task text...

[Gewerd-Strauss]

Hello @Gewerd-Strauss. How does this relate to #147 ?

Well now I am annoyed at myself. I somehow missed both this issue and the related PR #462;

And there is an advantage, especially if oyu use tasks only to handle recurring ones, and don't bother with it for day-specific things (as I do, I just use dayplanner for that instead.)
As I understand it, Tasks will consider any - [ ] XXX as a task without that filter active - which would mean a couple thousand ones across the entire vault. As this is simply impractical, I need to filter for those tasks which I want to display.
In theory I believe the plugin's codeblock could allow a setting to pre-filter to only include those tasks that have the required syntax at the end (or at least one indicator emoji from the set used, maybe), but until then the identifier is required.

I hope this cleared up my reasoning a bit more.

~Gw

[claremacrae]

Well now I am annoyed at myself. I somehow missed both this issue and the related PR #462;

Yes, it took me a while to find it too. In theory all new features are in Discussions not Issues, but that was not always true.

And there is an advantage, especially if oyu use tasks only to handle recurring ones, and don't bother with it for day-specific things (as I do, I just use dayplanner for that instead.)

Oh that's really interesting. That's another way of dividing up the data that I hadn't thought of.

As I understand it, Tasks will consider any - [ ] XXX as a task without that filter active - which would mean a couple thousand ones across the entire vault. As this is simply impractical, I need to filter for those tasks which I want to display.

Yes that makes perfect sense.

In theory I believe the plugin's codeblock could allow a setting to pre-filter to only include those tasks that have the required syntax at the end (or at least one indicator emoji from the set used, maybe), but until then the identifier is required.

In theory, yes.

It's not currently a high priority for my time - there are a lot of competing issues and ideas. However, I would certainly welcome an uptodate, well-tested PR to address it though.

[Gewerd-Strauss]

Yea, unfortunately JS? (I believe?) is absolutely not my area of expertise, I'm only a hobby coder with a reasonable amount of experience in Autohotkey so far :P
I suspect with a large amount of time I could figure it out, but that would assume setting up an editor and all the other shit I'd need.

I am not prepared to look into it at the moment, and quite honestly I unfortunately don't have the time to read up on JS at the moment for various personal and study-related reasons.

[claremacrae]

No problem at all!