Build Your Own Neovim Modules Library: A Step-by-Step Guide

[@mylesmontclair]

Awesome tutorial. I finally understand the basics of creating lua functions and modules. Much appreciated!

[@wojciech-kulik]

I created my own autocmd, which inserts a skeleton based on a filename. It also replaces some predefined placeholders like date, author, etc. :)

[@cloud-native-corner]

That's cool, can you share code or dotfiles?

[@wojciech-kulik]

@@cloud-native-corner YT is very annoying with removing comments, I can't post it here :).

[@farzadmf]

I'm always confused as to what "namespace" in Lua I need to use for a command/function I find in the help. Sometimes, I see it's in vim.fn, sometimes in vim. etc. I wish in the help, they would mention where something comes from As an example: If I do :h expand, how would I know it should be called like vim.fn.expand?

[@cloud-native-corner]

Agree, this is confusing. I usually use `helpgrep` and than quickfix list to filter and open various help topics (you can see screencast here: asciinema.org/a/ejRvWJG6zZniVUCiRMY4uWpql). This doesn't solve the issue of knowing which API belongs where. Hope this helps a bit. Plugin used for the quickfic list is: github.com/kevinhwang91/nvim-bqf

[@farzadmf]

Sorry for the late reply, but the asciinema link gives a 404