about summary refs log tree commit diff
path: root/pkgs/devhell
Commit message (Collapse)AuthorAgeFilesLines
* devhell/vim: add swayconfig-vimdevhell2022-12-231-0/+1
| | | | | It's annoying to have vim complain about sway's config not being i3. This lets vim appreciate sway's config.
* Rename vim_configurable to vim-fullaszlig2022-12-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "vim_configurable" derivation has had a long history in nixpkgs back then when there was no RFC process and where people still were figuring out better ways on how to configure compile-time flags. One of those was a composableDerivation function, which was used for "vim_configurable" and mapped attribute sets to autoconf-flags, so that for example if there was a "--enable-foo" flag you could just use something like: vim_configurable.merge { cfg.fooSupport = true; } You'd then get a Vim with "--enable-foo" passed to configureFlags. However, the composableDerivation feature was too complicated and was ultimately removed at some point. While it does allow for things such as introducing new "edf" (stands for Enable Disable Feature and maps the autoconf flags mentioned above to attribute sets) flags, the complexity that comes with that system is way too large than using something like eg.: vim-full.overrideAttrs (drv: { configureFlags = (drv.configureFlags or []) ++ [ "--enable-foo" ]; }) While this looks more verbose than the above, one can easily follow what's happening, whereas if you'd need to add and enable a new "edf" flag, you'd do something like this: vim_configurable.merge { flags = composableDerivation.edf { name = "foo"; }; cfg.fooSupport = true; } I admit that this does look a little nicer, but even I'm not sure whether it's worth adding so much complexity since in practice I rarely came across a sitation where something like the above would be really beneficial. So back then when "vim_configurable" was introduced[1], it was used as an alternative to the main vim derivation but using composableDerivation instead. Nowadays however, vim_configurable no longer uses composableDerivation and the rename also doesn't change any features, so I think it's safe to rename vim_configurable to vim-full in Vuizvui. [1]: https://github.com/NixOS/nixpkgs/commit/9a4e9e7a3b4014bb3c9f678ec22d254b85c4c98a [2]: https://github.com/NixOS/nixpkgs/commit/4e5ebcc3ed1de9c5c2001c7d5829f4566e0bde3f Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch Cc: @devhell
* vim/default: vim-markdwon -> markdown-preview-nvimdevhell2022-11-281-1/+1
| | | | | | I'm particularly annoyed at the way `vim-markdown` handles folding, so I'm going to give `markdown-preview-nvim` a spin. It's also actively maintained and seems quite powerful.
* Revert "devhell/vim: Re-enable vim-clap"devhell2022-04-251-1/+1
| | | | | | | Nope, never mind, maple is still not building, therefore vim-clap can't build. This reverts commit 4d4f07ef82d8a19587cc450b6d0a198e16acb48f.
* devhell/vim: Re-enable vim-clapdevhell2022-04-251-1/+1
| | | | Apparently this builds again according to `hydra-check`.
* pkgs/vim: Disable vim-clapdevhell2022-04-111-1/+1
| | | | *sigh*
* devhell/vim: Switch to vim-markdowndevhell2022-03-221-1/+1
| | | | | There are some issues with building `mkdx`, but I'm also not really happy with the way it does markdown.
* devhell/vim: Add vim-shellcheckdevhell2022-03-031-0/+1
|
* pkgs/vim: Add minimap-vimdevhell2021-10-071-0/+1
| | | | It is quite useful. Nice to see there is a good one around for vim.
* pkgs/vim: Add mkdxdevhell2021-09-051-0/+1
| | | | Still not giving up on a sensible markdown plugin.
* Revert "pkgs/vim: Add vim-markdown"devhell2021-08-041-1/+0
| | | | | | | Nevermind, I did test it before adding it, but I didn't test everything, and as it turns out it's not what I hoped it would be. This reverts commit 45894282b28ff8dee8ed7f1a31710ddc6ce275a2.
* pkgs/vim: Add vim-markdowndevhell2021-08-041-0/+1
| | | | | I'm working so much with markdown lately that I'd find it helpful if I didn't have to think of every markdown rule myself.
* devhell/vim: Add vim-clapdevhell2021-08-021-0/+1
| | | | Looks useful, let's see.
* pkgs/vim: Replace vim-css-color with vim-hexokinasedevhell2021-07-101-1/+11
| | | | | | | As @aszlig mentioned earlier, this looks like a better plugin. It does everything I need it to. This commit also enables `termguicolors` which wasn't the case prior, and without it `vim-hexokinase` cannot function properly.
* pkgs/vim: Switch to vim-css-color from colorizerdevhell2021-07-081-1/+1
| | | | | | The `colorizer` plugin doesn't produce accurate results, so I'll try `vim-css-colors`. It's also looking more maintained than the previous plugin.
* pkgs/vim: Add mucomplete plugindevhell2021-06-301-0/+7
| | | | | | I've been looking for a good, lightweight, and fast completion engine that also has little or no dependencies. The `mucomplete` plugin seems to fit the bill as I also don't have any fancy requirements.
* pkgs/vim: Add vim-tomldevhell2021-06-271-0/+1
| | | | | | I find myself working more and more with TOML files these days. Unfortunately neither `vim` nor `neovim` upstream have added support for syntax highlighting of TOML files yet.
* devhell/vim: Add colorizer plugindevhell2021-06-201-0/+1
| | | | This helps quite a lot when working with colors.
* devhell/vim: Add packages, remove textwidthdevhell2021-04-151-1/+2
| | | | | | The textwidth limit is getting annoying on certain files, and while I'm sure there's an elegant 'vim-way' of doing this without plugins, I'm just gonna go ahead and see if `vim-sleuth` does the trick.
* devhell/vim: Change vim from module to packagedevhell2020-12-042-0/+85
Recommended by aszlig to switch from module to package.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-01 19:48:52 +0000