Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
I can do that - IMO that makes more sense than ignoring the whole project based on the ignored directory patterns.
But using patterns allows the plugin to autoselect which projects to disable since it can distinguish between project1_dir/remote (which is the slow remote mount) and project2_dir/local (which is fast local storage).
Also it is available now and in release 2.0.
To be clear, this option would disable the whole plugin completely
I think thats the idea, for plugins where the project directory is on a slow mount disable the whole PO functionality but have it work for projects that are local. As the OP said "You both seem to ignore the fact that one can have projects where the plugin makes sense and others where it doesn't"
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.