Filter by symbol?

[jgarte]

Hi,

How can I filter by variables, for example. Or, only by classes.

[mohkale]

@jgarte

This is configured through consult-eglot-narrow. I believe you're looking for v.

[jgarte]

oh cool, thanks for pointing that out. Should I add that notion/reference/feature to the readme as a TLDR/heads up for others who also bypassed reading the source code in their haste to quickly use consult-eglot?

[jgarte]

BTW, what language servers have you tested this on? It worked for me with pyright but not pylsp, for example.

That's because pylsp does not support workspace symbols, unfortunately.

[mohkale]

Gopls and clangd are the reference ones I've used it with. Shame more language servers don't support it but ripgrep fills the gap for them well enough in my experience.

Happy to accept a PR to add a section to the README clarifying more customization options. I might be the weird one who always jumps to the code for customization options instead of looking in READMEs :-).

[jgarte]

I'm a weirdo to read the src code first also ;) But, I believe it's nice to have some notes of interest that invites new users to read the code and to have enough background context on how things work. Sometimes, a library or package is using other dependencies (even emacs native libraries) that the user is not yet familiar with. Giving this sort of information allows people not as familiar with the emacs ecosystem to get a quick big picture idea that invites and assists them in learning more about the emacs ecosystem. In other words, not everybody has the same level of education to immediately read the source code and make sense of it. Maybe they are almost there. Let's assist those people with better documentation and background on the code. I don't believe that the source code alone is the documentation. It is only one part of the picture that everybody should definitely be reading, of course.

[jgarte]

Internally tempel-key uses tempel-insert to trigger the insertion. ...

From https://github.com/minad/tempel#binding-important-templates-to-a-key

I think that prose docs like the above about internals are nice.