Twitter | Pretraživanje | |
justinmk
Why is still fun to work on after 5 years: people keep showing up with really impressive work, out of nowhere... Built-in LSP support has landed:
There are a few outstanding questions left, like: What interface should we expose to the users? How should we handle protocol extensions/custom protocols? For example, clangd supports passing offs...
GitHub GitHub @github
Reply Retweet Označi sa "sviđa mi se" More
Tyler Leonhardt 🔌🐚 16. stu
Odgovor korisniku/ci @justinmk
👋 Hi! I'm a maintainer of a PowerShell extension for nvim/vim I'm very curious about this built-in LSP support and would love to know how I can hook it up to our language server. Our LS is very.. unique.. So it might be a good robustness test for you 😅
Reply Retweet Označi sa "sviđa mi se"
justinmk 16. stu
Odgovor korisniku/ci @TylerLeonhardt
hi :) is currently using this repo as a home for "a bunch of LSP configs": Maybe that answers your question, else create an issue there... or PR ;)
Reply Retweet Označi sa "sviđa mi se"
pontus 14. stu
Odgovor korisniku/ci @justinmk
This is fantastic! 😍
Reply Retweet Označi sa "sviđa mi se"
TJ DeVries 14. stu
Odgovor korisniku/ci @justinmk
Congrats Justin. Glad my original PR finally frankensteined it's way into implementation 😂
Reply Retweet Označi sa "sviđa mi se"
Gregory Kapfhammer 20. stu
Odgovor korisniku/ci @justinmk
Thanks for all of your hard work on this project! RT : Why is still fun to work on after 5 years: people keep showing up with really impressive work, out of nowhere... Built-in LSP support has landed:
Reply Retweet Označi sa "sviđa mi se"
Luis Michael 18. stu
Odgovor korisniku/ci @justinmk
Does this mean it won’t be necessary coc.vim and others?
Reply Retweet Označi sa "sviđa mi se"
Jun Kai Gan 13. sij
Odgovor korisniku/ci @Clvx @justinmk
I have the same question, what js他he different between this and coc.vim?
Reply Retweet Označi sa "sviđa mi se"