lazy.nvim explained

[@VovaY]

TJ you are the content factory. A great topic to get more Neovim cult followers

[@christopherwood6514]

So he inherits from abstractcontentbuilderfactory?

[@Kane0123]

He's the teacher with a heart of gold that never gives up on us. He us the entire manual but still puts out new videos to try and make us better by converting. It's an obvious movie, we just need to figure out which A list celebrity could pull it off

[@KellyBrower]

He has ASO. Attention Surplus Order.

[@pesterenan]

I just forked the kickstart.nvim repo, and made some thinkering and was done with it, but knowing how this works is helpful to understand the 'magic' behind it. Nice video TJ!

[@innocentVince]

Love this series. (: Structured really well. Maybe create a playlist?

[@vincenzocalabretta6009]

Hey TJ thank you for what you do, this series is really great and exactly what I was looking for. I really like how you explain things without assuming previous concepts. Thank you and happy new year 😄!!

Thank you for this series TJ, really appreciated!

[@lucasefe]

TJ is a good person. Never hate. Making our lives better every day. That's great karma right there.

[@achimdomma2171]

Danke!

[@SimonM90]

Thank you. I finally got around to configure some stuff using Lazy. I love this series. It offers an on point instruction to a topic with no bs. The videos should show up in all relavant search results.

[@friendliness1337]

Really enjoying this series, thanks for making it! :) Learning a lot even as someone who's used neovim as main editor for a fair while now

[@infinitivez]

TJ, you jump around so much, trying to follow this from a beginner's perspective, even intermediate, is difficult to decipher. What even is this screen @7:07 that you're yanking the config from for Tokyonight? This config line doesn't look much like the one the repository uses. (edit: I realize I could grab the config from the github and use that, just curious what that Packages 4/5 screen you grabbed from, is)

[@patricorgi]

the final remarks are truly something every newcomer should listen to.

[@thiagolopes4978]

downloaded all the videos, watching locally on VLC, but came here to press the like button and give this comment, thanks TJ!

[@jesse9999999]

would be great to see hot reloading in Lazy for local plugin dev during this series, if possible!

[@abuk95]

Thanks a lot for this series! It really removes the block to properly setup Neovim for me ❤

[@radoslavgeorgiev428]

That was actually a good explanation. The idea that you specify what you want to install via lazy + you can keep the configuration in one lua file is great. I just moved a bunch of `after/*` configurations to the config function for every dependency. BTW, it'd be great if you can do a new video about the `after/*` folder, because there are a bunch of videos + tutorials, that are using it for config.

[@teej_dv]

what do you want me to mention besides that it runs after other stuff though? haha I did cover it in part in some of the series though

[@radoslavgeorgiev428]

@@teej_dv Thanks for replying! I haven't watched all series yet (will do over the holidays). Perhaps, a summary of "all the ways you can configure your plugins", including the after directory, would be really helpful, so people can make sense of everything they find on the internet 👍

[@korney4eg]

This gives great level of understanding of lazy plugin

[@avramukk]

Finally I will understand whether I have been using it for so long) Thank you)

[@Theosibo]

Another great and enlightening session. Thank you!

[@nottheengineer4957]

It took me a while to figure this out at the start, great explanation!

[@Jishanthegodev]

I loving this series, thanks TJ 😘

[@ryancastner6200]

14:01 🤣 loved the joke at the end

[@NicolasJoye]

You crack me up TJ!!! "Bad strategy for nvim is to not ready anything..." you really should do some stand up

[@geoblk3000]

Your teaching skills are waaaay underrated

[@ChristopherVanDerWesthuizen]

At 12:40 TJ gives the rationale that, with the separate file-per-plugin style, we could easily enable/disable plugins one at a time. Unless I'm missing something, that seems to also be true for the style in which each plugin is specified in the lazy.lua file. Please feel free to correct me if that's not the case. I somewhat feel like it's more straightforward to find all plugin specs in one place instead of having to open up several files.

[@the_yugandharr]

these videos are very useful man

[@olearydj]

Great series, TJ. Keep after it!

[@sidreddy7030]

I love this. I haven't and I am not gonna a miss a single day of this or AOC

[@lpanebr]

Really really really excellent video! ❤ Thank you!

[@aibui3087]

really love those videos like this

[@vikaspoddar001]

More power to TJ, more power to neovim

[@kleanse]

You’re the best, TJ. Awesome content

[@avivbaltsan7583]

Thanks! This helped a lot :)

[@gmosworld]

TJ, your Nvim content brings me such joy. Please don't :wq!

[@callmetyler]

Great series so far!

[@smibssmibs]

funny image. And I like the advice "do not spend time on lazy loading, the fractions of seconds saved will not save you any time".

[@elliotalderson6609]

Honestly, one can just create folder under pack/ directory and git clone + checkout plugins by hand when needed. This folder is already in your path so you just require a plugin and configure it.

[@uncertainukelele]

TJ is the new Santa

[@alexandrepereira6522]

If this is not too late, I would love you to cover creating a Neovim plugin!

[@rajdotone]

Thank you, brother (:

[@noahtah1511]

thanks again teej these are great

[@noahtah1511]

teej is definitely the best at diving into a technical topic and making it approachable

[@giansingh4710]

thanks for this. Love it. very helpful

[@volfpe]

Thank you for this series! I have a question about runtime paths and require. What file is imported when calling `require("lazy")`? I dont see any file named lua/lazy.lua in the lazy.nvim repository. Is it importing lua/lazy/init.lua? Is the init.lua file similar to index files in typescript, or am I completely wrong? 4:47

[@_..-_-.._]

TJ plz keep doing Neovim videos, thanks ❤

[@mnk4allcaps]

hell yeah

[@prashlovessamosa]

Thanks for sharing this

[@iukys3889]

Would you recommend moving to lazy for a packer user ?

[@AdityaSingh-uv8uf]

great content as always

[@aloisdeniel]

Thanks! Great explanations!

[@Cloopster]

Went into today's vid thinking "oh just 15 mins" ...2 hours later I am caught up

[@aladinoster]

Before anything thanks for your videos! They are extremely clear! I see that when installing your status bar on your left side I see N / I / C, I am getting the classic Normal, Insert, Change, how could I change this config?

[@klcoder]

That's cool!

[@MichaelDoornbos]

Great series

[@masoudesmaeilian5083]

can you explain also rocks.nvim too? how would you use it? will you use it? will you recommend to use it beside lazy nvim?

[@zachpalmer5538]

Will you make a video of how to setup the debugger for go and maybe javascript with kickstart

[@qwfp]

I think your mic is really sensitive to your position, so as you're moving around, the volume (and quality) is going up and down. Not sure what you can do about it, just some feedback from me. I use nixvim btw (it takes me two minutes to reload my config btw)

[@AntoineamtoineStevan]

TIL `enabled = false`, really nice to avoid removing the whole plugin code 👌

[@MichaelZijlstra]

First comment! Big fan of lazy!

[@josesblima]

Maybe I'd have to rewatch, but what exactly is lazy doing besides cloning the repo into /.local/nvim and adding that new directory to the path?

[@no_name4796]

You can lazy load plugins for faster startup for example. You have an easy interface to update, remove plugins whilst in neovim (:Lazy) Yes, you can manually install the plugins yourself, but why would you? You hate yourself?

[@mscholzdev]

What a miniature! 🔥🔥🔥

[@ingenarelitems]

okay tj somehow knows what i think about.. i've been using vim-plug since the start but i was thinking about switching to lazy.nvim... tj suddenly makes a new video on lazy.nvim...

[@KevinOMalleyisonlysmallreally]

OK, I admit that i'm a stupid person, but, there's some jumps in the installing the colorscheme, that completely through me off.

[@danielwood4786]

Is there any technical reason neovim requires files to be in lua folders? Shouldn't this be configurable?

[@TaiGroot]

commenting just to boost the algo

[@cit0110]

thats cool

[@romankovalov9015]

Actually helped me to understand, dafuq

[@sfryxell]

Please, God, tell me you're going to help us understand Mason, so we can do better than mole rats trying to configure our LSPs

[@yuxiang4218]

I understand more behind the 'magic'

[@sololvlpy]

thanks

[@adamsmolinski6739]

Komentarz dla zasięgu

[@CCHO12346]

Bro thinks hes santa bringing us this presents

[@examinethose]

cool stuff smileyface

[@hobbit125]

Really good, but why does everyone keep advocating that new people break up their script into complicated directory structures. It seems like advocating for just doing everything in init.lua first and then getting into making directory structures, etc. would be easier.

[@z4k_20]

Engineers love abstraction and clean code

[@snowman1185-v]

[@lucidmach]

sounds like the advice you give in the end was for your younger self 👀

[@wayneswildworld]

He does't explain any of the commands or what they do tho

Bruh!

[@sybren-srb]

why you keep calling it "folder"? its directory

[@pookiepats]

Ever use it to build actual applications? Constantly changing your config will rob your momentum.

[@user-ek8cd1gg3f]

Then don't change it.

[@pookiepats]

@ that's absurd

[@MrDujmanu]

Thank you for checkhealth()

[@mnk4allcaps]

bro really wrote :checkhealth ?