[Github-comments] Re: [geany/geany-plugins] projectorganizer: ignored directory patterns are not applied to project root paths (Issue #1283)

2023-10-18 Thread elextr via Github-comments
> creating the Geany project one directory above so foo becomes a single > directory of the project and can get ignored as a whole. Which is why I showed it as `project_dir/remote` where remote is the mount and the ignored pattern. -- Reply to this email directly or view it on GitHub: https://

[Github-comments] Re: [geany/geany-plugins] projectorganizer: ignored directory patterns are not applied to project root paths (Issue #1283)

2023-10-18 Thread Jiří Techet via Github-comments
> 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). But I think the problem (if I understand it correctly) is, that when you

[Github-comments] Re: [geany/geany-plugins] projectorganizer: ignored directory patterns are not applied to project root paths (Issue #1283)

2023-10-18 Thread elextr via Github-comments
> 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 `projec

[Github-comments] Re: [geany/geany-plugins] projectorganizer: ignored directory patterns are not applied to project root paths (Issue #1283)

2023-10-18 Thread Jiří Techet via Github-comments
> I don't use the plugin's sidebar BTW - I haven't even noticed that there is > one till now. Just curious - what are you using the plugin for then? > I'd also be fine with an option to disable to plugin/directory traversal on a > per project basis I can do that - IMO that makes more sense t

[Github-comments] Re: [geany/geany-plugins] projectorganizer: ignored directory patterns are not applied to project root paths (Issue #1283)

2023-10-17 Thread elextr via Github-comments
> 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

[Github-comments] Re: [geany/geany-plugins] projectorganizer: ignored directory patterns are not applied to project root paths (Issue #1283)

2023-10-17 Thread Stefan Tauner via Github-comments
You both seem to ignore the fact that one can have projects where the plugin makes sense and others where it doesn't (work). @techee In the instance I am describing here, the whole project directory is remote. The problem is not the indexing itself but the directory traversal which happens no m

[Github-comments] Re: [geany/geany-plugins] projectorganizer: ignored directory patterns are not applied to project root paths (Issue #1283)

2023-10-17 Thread elextr via Github-comments
To be clear, the ignore patterns are only applied _within_ the project directory tree, not to the path to the root, so as @techee said, unless the mount points are inside the tree they will not be filtered. Any filter applied to the path to root could only ignore the root and therefore the whol

[Github-comments] Re: [geany/geany-plugins] projectorganizer: ignored directory patterns are not applied to project root paths (Issue #1283)

2023-10-17 Thread Jiří Techet via Github-comments
I'm not sure if I understand the problem correctly. "root" for the plugin is - either the project directory itself, e.g. `/home/techet/projects/geany` - or added external directories, e.g. `/home/techet/projects/geany-plugins` and possibly some more Since `/home/techet/projects/geany` is the dire