perl-language-server
perl-language-server copied to clipboard
Loading of user snippets in VSCode after file opening is not working
Hey there,
thanks a lot for this really nice VSCode extension, I love it! There is only one point which I dislike a lot:
- I'm opening up one single directory (a repository) in VSCode.
- I'm jumping to one specific line in my code and start to type a defined shortcut of a user snippet I do have.
- As usual, I expected that my user snippet is working fine, but currently it's not.
- I have to wait several seconds, maybe up to 30s, to have everything "loaded" and running fine (the snippet is working then).
Any idea what is going on there? If I'm going to disable the extensions, my user snippets are loaded without any delay.
Please, let me know if I could help with this.
Thanks! Flo
There is an indexing operation that needs to complete before many things will work in PLS. Not sure why that would affect user snippets.
Hey @FractalBoy, thanks for your quick answer!
Is it possible to execute this indexing operation as an async operation somehow? Currently it seems that some stuff is really blocked by this operation.
As already mentioned in my first post, if there is anything I could help with, please, let me know!
It's already async, but anything that needs it will block until the index is ready.
It's already async, but anything that needs it will block until the index is ready.
Is there any chance to get this improved? For me, the question is: Why the user snippets are blocked by PLS indexing operation?
I may have been mistaken. I actually think that anything that needs it will just complete without the data from the index. I don't know why the user snippet would cause a problem. I'll have to create one for myself and see.
I am unable to reproduce this. Here are the steps I took.
- Created a user snippet
- Deleted the cache (.pls_cache)
- Restarted VSCode
- I was able to use my snippet before the indexing finished.
Can you test this again and let me know if this is still an issue for you?
@fliebe92 Is this still an issue for you?
@fliebe92 Is this still an issue for you?
Nope, I am not using it anymore. Closed.