Writing Plugins - It's Never Been Easier (NeovimConf 2022)

[@blahblah-rn1ts]

Now we just need to all agree that when you write a plugin you finish it in a way that it's useable instantly upon installation and doesn't require reading through 10 pages of documentation (maybe even from other plugins as dependencies) (I'm looking at you ... entire collection of LSP plugins)

[@devonduty]

Indeed! One should always deliver good default values so that users don't need to set everything up themselves.

[@runtimejpp]

love this guy, theoretical physicist teaching about vim, neovim and lua. the best

[@devonduty]

Thank you :)

[@patriciourrutia2297]

Great! Thanks Dev! I was waiting for this video. I watched live and it was awesome!!!

[@mandos22]

Thanks for great talk, I enjoyed it a lot and ChatGPT looks neat and scary at same time :)

[@Oswee]

This was really great talk!!!

[@FelipeV3444]

Look at teej and Prime being impressed with ChatGPT lmao. Thanks for the video! I've been wanting to write a simple plug-in for learning purposes.

[@devonduty]

Yeah, we've all been impressed by ChatGPT, back then, it was quite new :)

[@liminal27]

Excellent. Thank you.

[@daltonyon]

Great talk, help me to understand how to create a new plugin

[@andrewstone3032]

hilarious, i didn't realize this was you when i was watch the conf

[@Awwe12675]

I love this channel

[@艾曦-e4g]

It is just so cool. I wonder can this use tree-sitter to index the whole project. This is just for finding the todo in comments of the current buffer, can this done by vimgrep along with the tree-sitter to deal with the comment staff. Another thing is can todo be case insensitive, todo flollowed by ":" should be its pattern. :c

[@devonduty]

Hi, it would be possible but probably a bit inefficient to parse all files first. I think for this use case, vimgrep is more suitable (even though it searches for all text, not just comments). The Regex I used is of course very minimalistic, one can enhance it by ":", as you said, or include more words like FIXME, BUG etc. It was just for demonstration purposes.

[@cristobaljavier]

Excellent video thanks!

[@jarjar4780]

What's the difference in creating the plugin file inside your nvim/lua directory, so you can just require it without having to set your runtimepath. Is it just a convention so that it is isolated from the rest of your config? Also thanks a lot for the really insightful video!

[@devonduty]

Thanks, Jar Jar! Yes, that's also a valid option. Personally, when creating new plugins, I like to not change my Neovim config and just add it quickly to the runtime path. What's also possible: Some package managers allow you to specify local plugins, e.g. Lazy.nvim, that's also quite handy.

[@VovaY]

What TODO plugin did you use before writing yours?

[@devonduty]

I haven't used any plugin, but if I would use one, it would probably be github.com/folke/todo-comments.nvim (Folke's plugins are always awesome).

[@iamroot6338]

This is great. Can you share your slides

[@devonduty]

Thanks! Here are the slides and the code: github.com/David-Kunz/NeovimConf

[@shaileshsundram]

Which font are you using?

[@devonduty]

It's Iosevka

[@anasouardini]

nvim defaults are really weird and impractical.

[@devonduty]

Some of them are. At least they are better than Vim's.

[@anasouardini]

@@devonduty confirmed