Folder blacklist when Trigger Templater on new file creation

[Superkikim]

Hi.

Currently, when Trigger Templater on new file creation is enabled, it will be triggered on any file creating event.

I suggest you add a folder black list where we can exclude folders where we DON'T want Templater to be triggered.

This is useful when we use a plugin of a script to import a large amount of file, which do not need Templater to be triggered.

[Zachatoo]

Would it make more sense to disable that setting before the import, then re-enable it after you're done?

Is it a common use case to consistently import into the same folder(s), such that it's worth the time to setup blacklist folders instead of disabling the setting?

Is it common to import files that have Templater tags in them? If they don't have Templater tags, nothing should happen.

[Superkikim]

That would be cumbersome. It's a plugin that can imports hundreds of notes in seconds. I thought a black list could be helpful. I asked because when I import the notes, I have plenty of message in the console. And I don't really understand why. But it's most probably by design. It just says the notes are more than 10000: Templater skipped parsing Outils/ChatGPT/Archives/2023/11/e12d89c0-e6cb-470e-8eb7-1d44805b9638.md because file size exceeds 10000 But I guess, this is just info, and the trigger doesn't add pressure to the computer resources ? Le 2023-11-22T07:32:29.000+01:00, Zach Young ***@***.***> a écrit :

…

 Would it make more sense to disable that setting before the import,  then re-enable it after you're done?    Is it a common use case to consistently import into the same  folder(s), such that it's worth the time to setup blacklist folders  instead of disabling the setting?    Is it common to import files that have Templater tags in them? If  they don't have Templater tags, nothing should happen.    —  Reply to this email directly, view it on GitHub  [#1252 (comment)],  or unsubscribe  [https://github.com/notifications/unsubscribe-auth/ACM7BZLWFSUCXD4PZO2SZGDYFWL73AVCNFSM6AAAAAA7VWCARSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMZYGQ4DI].  You are receiving this because you authored the thread.Message ID: ***@***.***>

[Zachatoo]

It wouldn't be any more intensive than checking the blacklist, no. So for your use case it would just remove the messages from the console.

If you want it to process faster, disabling Templater would be the way to go, though the processing will be minimal if they're all large files.

[Superkikim]

Sounds right. Tx for clarifying. Have a nice end of week. Le 2023-11-22T19:56:21.000+01:00, Zach Young ***@***.***> a écrit :

…

 It wouldn't be any more intensive than checking the blacklist, no.  So for your use case it would just remove the messages from the  console.    If you want it to process faster, disabling Templater would be the  way to go, though the processing will be minimal if they're all  large files.    —  Reply to this email directly, view it on GitHub  [#1252 (reply in thread)],  or unsubscribe  [https://github.com/notifications/unsubscribe-auth/ACM7BZKQRM7WFSQEM3A6HYTYFZDFLAVCNFSM6AAAAAA7VWCARSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMNBVGU2TC].  You are receiving this because you authored the thread.Message ID: ***@***.***>