Originally created by @DrKJeff16 on GitHub (Sep 13, 2025).
## Description
I maintain [`DrKJeff16/wezterm-types`](https://github.com/DrKJeff16/wezterm-types), a project that provides extended LuaLS annotations to [wezterm](https://github.com/wezterm/wezterm) configuration.
[It includes Neovim support](https://github.com/DrKJeff16/wezterm-types#neovim), and has reached pretty much a complete state.
My question is: in what category would it go, if at all? I'm attempting to make a PR for it if so, but I'm unsure as to where should I place it.
> [!NOTE]
> That repository has also been mentioned in [`michaelbrusegard/awesome-wezterm`](https://github.com/michaelbrusegard/awesome-wezterm), if it changes anything.
Considering it extends and uses lazydev and it's mainly about configuration and lua development it could fit in Neovim lua development nicely.
Also "Utility" is a good catch-all if you're not 100% sure of the correct section.
@Penaz91 commented on GitHub (Sep 15, 2025):
Hello!
Thanks for the question.
Considering it extends and uses `lazydev` and it's mainly about configuration and lua development it could fit in `Neovim lua development` nicely.
Also "Utility" is a good catch-all if you're not 100% sure of the correct section.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @DrKJeff16 on GitHub (Sep 13, 2025).
Description
I maintain
DrKJeff16/wezterm-types, a project that provides extended LuaLS annotations to wezterm configuration.It includes Neovim support, and has reached pretty much a complete state.
My question is: in what category would it go, if at all? I'm attempting to make a PR for it if so, but I'm unsure as to where should I place it.
@Penaz91 commented on GitHub (Sep 15, 2025):
Hello!
Thanks for the question.
Considering it extends and uses
lazydevand it's mainly about configuration and lua development it could fit inNeovim lua developmentnicely.Also "Utility" is a good catch-all if you're not 100% sure of the correct section.
@DrKJeff16 commented on GitHub (Sep 15, 2025):
Thanks!