You both seem to ignore the fact that one can have projects where the plugin makes sense and others where it doesn't (work).

Plugins can be disabled in the plugin manager.

The problem is not the indexing itself but the directory traversal which happens no matter what the index setting is AFAICT

What evidence do you have for that? Directory reading is likely to be much cheaper than reading all the files in that directory.

And AFAICT traversal does not enter a directory which matches the directory ignore patterns. So you can likely stop the tree traversal by setting the directory and file ignore patterns to * and only the root directory will be read. That is as close as there is to disabling the plugin except for actually disabling it in the plugin manager AFAIK.

and that it is done synchronously (apparently even in the UI thread).

Correct, Geany is non re-entrant single threaded code because the UI framework, GTK, is single threaded and most of Geany is interacting with the UI.

I would argue that it is not at all obvious that the filter does not apply to the project's root directory.

Documentation contributions welcome.

I'd also be fine with an option to disable to plugin/directory traversal on a per project basis

So thats a UI and storing and restoring the option and making functionality dependent on it and "somebody"s gotta do it. Each of the plugins in this collection are mostly the contributed work of one individual (with (un?)helpful comments from the rest of us ;-). Most plugins are therefore focused on that individuals use-case, in this case large projects on fast machines with local fast storage.

the workaround of having the mountpoint as a subdirectory successfully and that's good enough for now.

Great.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.