Question: On Lint on Save and the breaking of Templater scripts about obsidian-linter HOT 5 CLOSED

No worries. The commander macro can use lint unless ignored and that should take care of it.

I am glad this is fixed for you!

from obsidian-linter.

I am not 100% sure what is happening here since I have used this plugin for years now and have not hit the issue where I have linted Templater files since I added them to my ignore path.

So I would like to better understand the problem since I believe that, except for manually telling a file to be linted, it should be checking that the file is a markdown file and that it is not ignored.

How are you currently able to lint your Templater files if they are in your ignored path? It may be a bug in the Linter unless you are using the rule/logic that is meant to bypass that.

from obsidian-linter.

I did double check the logic and there is some logic in place to make sure that lint on file change does not run on ignored files. So if it is running on them, that would be a bug that needs fixing.
Edit: this comment is unrelated.

from obsidian-linter.

Note: Lint on save is checking that the file is a markdown file and that it is ignored.

I am not sure how you are linting ignored folders (not sure if that is where your Templater scripts live), but if they do, a reproducible example would help greatly in getting to the bottom of this.

Thanks!

from obsidian-linter.

Turns out the command I was using with the key combo was actually a Commander macro (with the same name) that contained the single command 'lint the current file' -- probably I needed that on mobile where I cannot press key combinations...?

Indeed, when one lints on save, the ignored folders are respected.

Sorry about the trouble.

Cheers

from obsidian-linter.