Open
Conversation
|
Is the auther still there? |
Author
|
@cxwx, sorry I didn't see your messages @VidocqH, the initial author of lsp-lens seems not maintain lsp-lens since 2 years. I am using my own repo since january and I am happy with it. You can use "worming004/lsp-lens.nvim" I do not intend to maintain the project. current fonctionnalities are fine for me. |
|
thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix #41,
Before fix, lsp-lens open a pipe for each symbol found without closing it. After a lot of git blame usage (by opening a lot of buffer or with huge buffer), pipes are cumulated and reach system limit.
This fix close each pipes after each usage. Pipes are not anymore cumulated.
With local test on a huge buffer, I have not any single more opened file compared with a usage without lsp-lens