Комментарии:
Can you share your dotfile repo please. Thanks. This was super useful
ОтветитьWould it be better to learn VIM first or can I go straight to learning NeoVIM?
ОтветитьQ: isn't lua embeded in legacy vim ?
ОтветитьThanks a lot for this! Really needed this.
ОтветитьDo you share that config on github? I looked for it but I didn't find it
Ответитьdude thank you i've been looking for a way to config neovim and this was really simple compared to trying to figure it out myself. it was a little confusing and i don't know code but as someone who loves awesomeWM i appreciate lua and you really helped out.
ОтветитьHey, what's your background music? It sounds great
Ответитьuseful
ОтветитьIn the first part of your video, you're spreading a lot of misinformation. Vim9 script is not a new technology. It was already available in vim 8.2 and most of the initial work was done in the vim9 fork of vim, which was merged back later on. It would be far more accurate to say that when significant changes happen in a codebase, more bugs are likely to appear, just like in any other language (including Lua), and that's of course, a very weak argument for dismissing vim9 script in favor of Lua.
Additionally, the claim that your implementation of LSP for the Go language is more readable than the equivalent code in vimscript is extremely subjective. Lua is a great language, very minimal and elegant, but as part of a language binding, it is really verbose, full of indirections with a messy feel due to the use of namespaces. Again, it is not Lua's fault, since the same can be said of the language bindings for python, ruby in vim. I have yet to see a single example of a concrete implementation in which Lua in neovim is more readable than the equivalent vimscript, let alone vim9 script which is even more readable without the quirkiness of legacy vimscript.
lua is like the opposite of java
Ответитьhmm u love to touch a file then open the file in vim when just doing the vim file.txt if u save it at all it makes that. Great video
Ответитьpop-os, my man!
ОтветитьThe typical problem with all those "cool Lua+Nvim" guys is that they never read language tutorials. So I've started to watch this video and, a miracle! I see him opening Lua reference.. but then I notice it's 5.4. Thanks God, my world stays the same as yesterday. They still haven't learnt the difference between Lua 5.1 and 5.4 )))
ОтветитьI just use emacs :V
ОтветитьCan't help noticing you type :wqa every time. Maybe just try :x
ОтветитьYou said vimscript dead... every lua nvim config - vim.cmd([[blablablabla]])
Ответитьgod thank you. I have been looking for a long time and finally got on your video
ОтветитьI'm waiting for helix...
ОтветитьGood video, thank you!
ОтветитьWas just about to comment on the name clashing, took me way to long to figure out what I was doing lol.
ОтветитьThanks man, I got the good habit of wanting to learn everytNice tutorialng before I start sotNice tutorialng (wNice tutorialch is impossible) tNice tutorials quick guide is what I
ОтветитьI’m interested in learning Vim, as it is aesthetically pleasing, but this folder structure thing is such bullshit. Why have all these folders with magical names and not just specify them in require :/
ОтветитьI feel as if Neovim users want Vimscript to die just so they can feel better about their choice of using Lua. These two projects are separate for a reason and I wish Vim will remain minimal and avoids the hype around Neovim. I picked vim over Emacs just because I wanted my editor to remain minimal and not include every new stupid technology (i.e whatever vscode brings to the table). The Neovim user base is one of the most toxic ones out there and I wish they would just leave us alone
ОтветитьCan you do a video on how to incorporate go debugger with nvim-dap-go? I really liked this video as I'm switching to Astro Vim and would really know how to set up a debugger. Thank you.
ОтветитьWOW! Thank you man, just getting into neovim and this was what I was looking for to get going!
ОтветитьThank you! This was really helpful! ❤
ОтветитьLoL cool explnation instead of reading a bunch of line of text
ОтветитьVery awesome! Tyvm ❤
ОтветитьThanks!
ОтветитьLua changed my life.
ОтветитьMay I ask what boom arm you are using for your mic? It looks really cool!
ОтветитьReally awesome/productive/efficient explanation/video, big thank you!
ОтветитьGreat explanations with even better documentation.
Good job mate
I just started learning lua today, but lua to me felt like (perl+javascript+python)/3. Thank you for the amazing tutorial!
ОтветитьI wonder why Vim developers didn't simply use Lua, too.. They break backwards compatibility and waste this once-in-a-lifetime opportunity by introducing a stupid single purpose made-up scripting language instead of an already established, widely used and documented embedded programming language.
ОтветитьThank you for this resource
ОтветитьWhy do you call the API "endpoints?" That doesn't make any sense, you're not making RPCs or sending data through a network, you're just calling library functions.
ОтветитьI am still getting errors with packer after renaming
ОтветитьWe use packer to install plugins. But how do we install packer? Does it come shipped with neovim?
ОтветитьI appreciate the "slow" tempo and the basic approach to this topic. I have previously watched ThePrimagen and his nvim setup, and even though i prefer his approach in general, i really do appreciate your video more as it is more basic and more explanatory. Thank you!!!
ОтветитьAny name or reference to the music running in the bg?
ОтветитьNice one!
ОтветитьThe title is just ... boom!
This is the last month of 2024, and Vimscript isn't dead yet, in fact, some maintainers of Neovim like justinmk still use Vimscript to configure Neovim