Matt Sturgeon
Matt Sturgeon
WIP draft. I've started adding some of the options required and their defaults. Still need to work on the implementation, assertions and add some tests. Source option based on [nix-darwin's...
Currently we rely on a no-default package option when there is no known package in nixpkgs for a none-ls, efmls, or LSP server. This results in a fairly generic error:...
Rather than having each option remove `lua` in their `apply` function, we can do this in the submodule type's `merge` function. Yes, it's a little annoying that we have to...
This is _technically_ redundant, because we patch `either` to be recursive. But I think it is best if `maybeRaw` does this explicitly, without relying on that behaviour.
Things done: - Drop `helpers` in internal useage - Access nixvim's lib via `self` - Access the (un-extended) lib via `lib` While I like the idea of having `lib.nixvim` access...
It would be useful to end-users to be able to apply nixvim's lib extensions themselves, in addition to their own customizations. This PR will rethink the way we extend the...
For example, upstream have a `meta.docs` option that references a module's common preamble documentation. Effectively the same as our `nixvimInfo.description`. https://github.com/NixOS/nixpkgs/blob/814a4e48c4a4a7937c927786164199d985339560/nixos/modules/misc/meta.nix#L47-L55 See https://github.com/nix-community/nixvim/pull/2302#discussion_r1772879064 If we have the module in-tree, we...
WIP draft to fix #1784 - copy-paste the nixpkgs module from nixos - format with nixfmt - strip out irrelevant bits - replace our `defaultPkgs` special arg with `pkgsPath` TODO...
Initial conceptual stub for a CI workflow that can announce new plugins. Pushing this up WIP and unfinished as I find GitHub workflows particularly draining 😅 Hopefully I've stubbed enough...
Currently we expose a few "system module" wrappers for nixvim, specifically for nixos, home-manager, and nix-darwin. We plan to promote the use of an evaluated nixvim config to access a...