Andrew Patton

The plugin had other issues other than the perf from indexing larger projects (mainly neglect), but as of 1.8.0, it should be working again, at least for its own source...

@broesdecat Any details about your project that causes the crash that you could share? Would be particularly great to have a repo or folder where the bug is reliably reproducible....

Big projects take a long time for the package to index. Architecturally, the package relies on grammar parsing to identify symbols across your project, which both makes it very flexible...

A couple more specific tips: - Make sure to include file extensions you don’t care about in your “More ignored names” options, like: `.css .svg` - You probably want to...

This is fixed in 1.8.0

@mefynn Can you provide any details at all? Maybe a call stack, maybe an example file, or a description of the project?

I realize it’s been a silly amount of time since you posted this issue and that for a large part of that time, this plugin has been largely broken, but...

@v3ss0n To my mind, this is the biggest issue with the package, but I also think the general problem is largely unsolvable (it takes a long time to go through...

This is by no means fixed, but it is improved as of 1.8.0. Also, I can recommend a few techniques to help: - Make sure to include file names and...

This seems like an easy win for performance. I’ve got part of the logic working in the [skip-grammars-no-matching-patterns branch](https://github.com/v3ss0n/goto/compare/skip-grammars-no-matching-patterns), though currently, it breaks other aspects of the “Project Symbols” command.