Комментарии:
Thanks a lot, great comprehensive and explanatory video
ОтветитьThe author of Lua is using M as abbreviation for Module all across his book Programming in Lua, especially in the chapter "The Basic Approach for Writing Modules in Lua". Though I don't recommend this book for getting started with Lua for Neovim, since it's covering Lua 5.3 which has some significant changes since 5.1 which is used in NeoVim's LuaJit. And it's also very academical and has a horrible editing and didactic approach, despite 4th edition. You're better off with Neovim's lua help pages. But once you figured out most important stuff in NeoVim and Lua it might be a valuable resource for advanced Lua programming.
ОтветитьM is for Module
Ответить:LspInstallInfo didn't work for me. Now I'm eager to find out why 😃
Ответитьcmp-nvim-lua should be replaced by plugin neodev.
lsp-installer should be replaced by plugin mason
This is probably the most important video. And since it has gone somewhat obsolete it would be great if you made another video on this. I know your repo has the latest code but your explanations are really helpful.
ОтветитьThis whole series is so awesome!
ОтветитьNice tutorial for us newbies! Is there any chance that you worked with a NX integrated monorepo?! I cannot get the "find references" feature to work and this is holding me back from using neovim! Thanks!
ОтветитьDude, you're godsent. Thank you, thank you, thank you for your amazing playlist, and for all the hard work you've put into creating your repo and teaching a bunch of randos online how to turn neovim into an amazing, personolized IDE. I've been doing a lot of work in Inteliji Idea, and though it is very good in its niche, I grew tired of all the bloat, lags, and endless indexing. This, what you've done to promote neovim to people, is truly great. 10/10
ОтветитьHi I hope you see this CM. Which font are you using in this video? and which theme? Thanks
ОтветитьThis content in the Repo is not the content from this video. For example the installer File is missing.
ОтветитьVery good tutorial, thanks for creating it
Ответитьthe `gl` command doesn't expand the error message for Rust. I have rust-analyzer installed, still doesn't work. What to do?
ОтветитьHi chris, love your videos and like your wallpaper more : ) . Can you share your wallpapers to us?
ОтветитьExcellent series, Chris. I have a LSP question. Thanks to lsp-zero and Mason, I'm set up for C++. There's one minor issue, it's flagging a correct statement as an error. I think that's because I'm using c++20, and clangd is using an earlier standard. How do I get clangd to use C++20? Thank you.
ОтветитьCan you make a video updating the LSP Config using mason.nvim instead? nvim-lsp-installer is no longer being maintained. Thanks!
ОтветитьEven a year after, this playlist is helping me learn how to configure neovim so good.
ОтветитьIf anyone else is having issues with null-ls being shown as the client for TS, add "tsserver" to the servers table in user/lsp/mason.lua.
ОтветитьSo, one thing I noticed while getting this working is that I have to be typing a method name to get the signature/docs to show. Is there a way to hover on a method (eg, go's fmt.Printf) and have it display the text without having to do a substitution on Printf?
ОтветитьThank you very much for this useful resource.
How are people getting the icons to display properly? They're not displaying well when I checkout the repo.
You don't need cmp_nvim_lua now since the LSP manages it with the Lua server.
ОтветитьI imagine 'M' stands for Module.
ОтветитьIt appears you have replaced nvim-lsp-installer by something named mason?
Ответить10xing my understanding of NVIM with this series! This is so awesome. Your hard work on all this is appreciated.
ОтветитьTack!
ОтветитьI get this error:
Error while calling lua chunk: C:\Users\a\AppData\Local\nvim/lua/user/lsp/mason.lus:36: attempt to index a boolean value stack traceback:
C:\Users\a\Appdata\Local\nvim/lua/user/lsp/mason.lua:36: in main chunk
[C]: in function 'require'
C:\Users\a\Appdata\Local\nvim/lua/user/lsp/init.lua:6: in main chunk
[C]: in function 'require'
C:\Users\a\Appdata\Local\nvim\init.lua:6: in main chunk
Hi! Awesome video, as always, I'm binging all the content. Can you please update this video for mason? because the repo it's now updated on the branch LSP. Thanks!
Ответитьwhy there is different files in the repo in lsp branch? i just wanted to copy some of the code, because your vids was helpfull so far, and its just no there. can you pls mark this video outdated and link new one in the description
ОтветитьAs of 19 Oct 2021, it is recommended to use cmp_nvim_lsp.default_capabilities(capabilities) instead of cmp_nvim_lsp.update_capabilities(capabilities) as the latter will be deprecated
Ответитьnah, this is too much for a code editor! i don't want to spend half my life reading docs, writing configs, programming my code editor instead of doing my work. i guess i'll stay with vscode. i tried to follow (but now nvim-lsp-installer is called mason.nvim) and make pyright work, but it's just not working at all.
ОтветитьHi, Thanks for the great tutorial, but I want ask something about "lsp_highlight_document" (the M.on_attach set up function).
I mention that is not work on my neovim, so I think the problem is "client.server_capabilities.documentHighlight", and then I print the value, I get "nil", and then I print the other value (client) I get "{".
so... I just want ask how can I print the right value from config file? no matter I use "print" or "vim.vim.pretty_print" I always get a single curly bracket ( "{" ), that's make me really confusing. I didn't know is I use the wrong way or something wrong,
can u make another vid using mason.nvim plss
ОтветитьThank you for these videos.
Best LSP tutorial
I'll bet you M stands for module a generic name for a set of code. I know this is just speculation but it makes sense to me
ОтветитьThank you very much Chris for all these tutorials, i am learning a ton from you.
ОтветитьThe LSP is not working I tried everything for DAYS, I am about to lose my mind. Pyright and copilot is not working in python files here is my config of pyright.lua in configs file: ( i added that into servers list and installed pyright)
return {
settings = {
python = {
analysis = {
indexing = true,
typeCheckingMode = 'basic',
autoSearchPaths = true,
diagnosticMode = "workspace",
useLibraryCodeForTypes = true
},
},
},
filetypes={
"python"
},
cmd={
{ "pyright-langserver", "--stdio" }
},
}
===============================
Here is configs.lua
local status_ok, lsp_installer = pcall(require, "nvim-lsp-installer")
if not status_ok then
return
end
local lspconfig = require("lspconfig")
local servers = { "jsonls", "sumneko_lua", "pyright", "copilot" }
lsp_installer.setup({
ensure_installed = servers,
})
for _, server in pairs(servers) do
print("SERVEr=",server)
local opts = {
on_attach = require("user.lsp.handlers").on_attach,
capabilities = require("user.lsp.handlers").capabilities,
}
local has_custom_opts, server_custom_opts = pcall(require, "user.lsp.settings." .. server)
if has_custom_opts then
opts = vim.tbl_deep_extend("force", opts, server_custom_opts)
end
lspconfig[server].setup(opts)
end
Hey, could you help me with this problem: when i open a python script the language is detected but pyright is not attached when i look LspInfo, thanks!
Ответитьthanks man
Ответитьanyone getting an "attempt to index a boolean value" about their lsp/init.lua file for the "require("user.lsp.handlers).setup()" line? Can't figure out what's wrong but I assume something with the setup function?
ОтветитьHi Chris,
Any chance of updating this tutorial as nvim-lsp-installer will not be maintained anymore? In my case my diagnostics are messed up (just first occurrence appears). It seems like it is ignoring some parts of the handler file.
Thanks
Really helpful content, subscribed and liked, one questions tho
I found that the Lua Lsp already provides what `cmp-nvim-lua` provides, is `cmp-nvim-lua` providing something more that I don't know of?
Man, this tutorial, playlist, channel.. is genuinely invaluable
ОтветитьMan thank you so much for these videos. Every other resource seems to go down the COC route so it's nice to finally see an alternative setup that happens to match much of what I'd already put together myself so far. This playlist is amazing.
ОтветитьThis is a maddening amount of configuration. The old vimscript plugins just require a couple of variables to be set for each plugin, at most. I don't normally shy away from config work, but these lua plugins are just too much work--they don't seem ready for ordinary usage. The deeper I get into this project, the more unwieldy it gets.
Ответить