| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | docs/vim.section.md: Add note about nvimRequireCheck (#349864)•••We are trying to use this more often but, at the moment, it's a manual
addition to overrides.nix. Add notes about the benefits of adding it and
how it can help identify missing dependencies. | Austin Horstman | 2024-10-22 | 1 | -0/+13 |
| * | vimPlugins: introduce passthru.initLua for some plugins (#334913)•••* vimPlugins: introduce passthru.initLua for some plugins
as described in https://github.com/NixOS/nixpkgs/issues/172538, some vim
plugins need some configuration to be able to work at all.
We choose not to patch those plugins and instead expose the necessary
configuration to make them work in `PLUGIN.passthru.initLua`.
For now the user can check if plugins have a `PLUGIN.passthru.initLua`
and if yes, prepend it to their own init.lua.
Maybe later we can revisit this to either patch them in a way that is
clear that it's a nixpkgs patch or by having the neovim wrapper pick
those snippets and autoadd them to init.lua ?
* Update doc/languages-frameworks/vim.section.md
Co-authored-by: Marc Jakobi <mrcjkb89@outlook.com>
---------
Co-authored-by: Marc Jakobi <mrcjkb89@outlook.com> | Matthieu Coudron | 2024-08-19 | 1 | -0/+8 |
| * | doc/vim.section.md: fix references to the old update.py script•••Running the `update.py` script directly doesn't work anymore, so instead
replace all usages of it in the documentation with `nix-shell -p
vimPluginsUpdater --run 'vim-plugins-updater'`.
| Thiago Kenji Okada | 2024-07-15 | 1 | -4/+4 |
| * | vimPlugins.nvim-treesitter: fix update.py and update documentation (#321535)•••* vimPlugins.nvim-treesitter: fix update.py and update documentation
| Mango The Fourth | 2024-06-24 | 1 | -1/+1 |
| * | treewide: Fix all Nix ASTs in all markdown files•••This allows for correct highlighting and maybe future automatic
formatting. The AST was verified to work with nixfmt only.
| Janne Heß | 2024-03-28 | 1 | -6/+10 |
| * | vimPluginsUpdater: init•••The nixpkgs documentation mentions how to update out of tree plugins but
one problem is that it requires a nixpkgs clone.
This makes it more convenient.
I've had the need to generate vim plugins and lua overlays for other
projects unrelated to nix and this will make updates easier (aka just
run `nix run nixpkgs#vimPluginsUpdater -- --proc=1` or with the legacy commands:
`nix-shell -p vimPluginsUpdater --run vim-plugins-updater`.
I added an optional "nixpkgs" argument to command line parser, which is the path
towards a nixpkgs checkout. By default the current folder.
update-luarocks-packages: format with black
| Matthieu Coudron | 2023-10-01 | 1 | -5/+6 |
| * | vimUtils: buildVimPluginFrom2Nix renamed to buildVimPlugin•••the `from2Nix` suffix is a legacy from vim2nix but we dont use that anymore. It makes the name of the function unusual and long.
| Matthieu Coudron | 2023-09-27 | 1 | -1/+1 |
| * | use subcommands in plugin updaters (#223164)•••* update.py: introduce subparsers for plugin updaters
This is preliminary work to help create more powerful plugin updaters.
Namely I would like to be able to "just add" plugins without refreshing
the older ones (helpful when github temporarily removes a user from
github due to automated bot detection).
Also concerning the lua updater, we pin some of the dependencies, and I
would like to be able to unpin the package without editing the csv
(coming in later PRs).
* doc/updaters: update command to update editor plugins
including vim, kakoune and lua packages
Co-authored-by: figsoda | Matthieu Coudron | 2023-04-14 | 1 | -2/+2 |
| * | doc: assign ids to many headings•••without stable ids on headings we cannot generate stable links to these
headings. nrd complains about this, but the current docbook workflow
does not.
a few generated ids remain, mostly in examples and footnotes. most of
the examples are generated by nixdoc (which has since gained MD export
functions, and the MD export does generate IDs).
| pennae | 2023-03-27 | 1 | -3/+3 |
| * | vim-full: rename from vim_configurable•••Avoids confusion: `vim-full`'s build-time features are configurable, but both
`vim` and `vim-full` are *customizable* (in the sense of user configuration).
| Naïm Favier | 2022-12-09 | 1 | -4/+13 |
| * | doc: use sri hash syntax•••The nixpkgs manual contains references to both sri hash and explicit
sha256 attributes. This is at best confusing to new users. Since the
final destination is exclusive use of sri hashes, see nixos/rfcs#131,
might as well push new users in that direction gently.
Notable exceptions to sri hash support are builtins.fetchTarball,
cataclysm-dda, coq, dockerTools.pullimage, elixir.override, and
fetchCrate. None, other than builtins.fetchTarball, are fundamentally
incompatible, but all currently accept explicit sha256 attributes as
input. Because adding backwards compatibility is out of scope for this
change, they have been left intact, but migration to sri format has been
made for any using old hash formats.
All hashes have been manually tested to be accurate, and updates were
only made for missing upstream artefacts or bugs.
| Colin Arnott | 2022-12-04 | 1 | -1/+1 |
| * | doc/vim: Clarify buildVimPlugin/buildVimPluginFrom2Nix | Jocelyn Thode | 2022-11-14 | 1 | -1/+3 |
| * | doc/vim: update docs for nvim-treesitter | figsoda | 2022-10-31 | 1 | -3/+5 |
| * | doc(vim): take into account plug non-support•••Apply suggestions from code review
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
| Matthieu Coudron | 2022-09-11 | 1 | -4/+8 |
| * | doc(neovim): remove the mention of plug for neovim•••This was removed to simplify configuration. One could create a function that converts the plug format to vim native package format (only plugin system supported for neovim) and upstream it to nixpkgs if that's an issue
| Matthieu Coudron | 2022-09-11 | 1 | -13/+1 |
| * | doc: present how to create a vim-plugin overlay•••it is possible to maintain an out of tree list of neovim plugins with this method
Update doc/languages-frameworks/vim.section.md
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
| Matthieu Coudron | 2022-09-11 | 1 | -5/+18 |
| * | vimUtils: remove vam support•••having this many (complex) options not only is hard to maintain but I cant see the benefit of these options now that vim supports packages
| Matthieu Coudron | 2022-07-10 | 1 | -97/+1 |
| * | Update grammar in vim section•••Fixed a few grammatical issues. Was uncertain how to address Treesitter, as the homepage itself is inconsistent, using all combinations of Treesitter, Tree-sitter, treesitter and tree-sitter. | Jayson Henkel | 2022-07-08 | 1 | -9/+9 |
| * | vimUtils: deprecate configure.pathogen (#154814)•••pathogen does not bring any value compared to vim native packages so
remove it to ease maintainance burden. | Matthieu Coudron | 2022-06-13 | 1 | -3/+0 |
| * | Merge pull request #164994 from ncfavier/vim-wrapper•••vim wrapper improvements | 7c6f434c | 2022-03-29 | 1 | -1/+4 |
| |\ |
|
| | * | vimUtils.makeCustomizable: rewrite to include more things•••The current wrapper only includes vim, gvim and the man pages
(optionally). This rewrite distinguishes two scenarios, which I expect
cover the majority of use cases:
- standalone mode, when `name != "vim"`, means the user already has a
vim in scope and only wants to add a customized version with a
different name. In this case we only include wrappers for `/bin/*vim`.
- non-standalone mode, when `name == "vim"`, means the user expects a
normal vim package that uses the specified configuration. In this case
we include everything in the original derivation, with wrappers for
all the executables that accept a vimrc.
| Naïm Favier | 2022-03-25 | 1 | -1/+4 |
| * | | docs: replace defunct git://github.com urls with https:// | Lucas Hoffmann | 2022-03-25 | 1 | -1/+1 |
| |/ |
|
| * | Move misc/vim-plugins to applications/editors/vim/plugins | AndersonTorres | 2022-02-24 | 1 | -4/+4 |
| * | doc: fix broken links•••Links in documentation shouldn't point to dead ends.
| Amon Stopinšek | 2021-12-09 | 1 | -2/+2 |
| * | update-luarocks-packages: use pluginupdate.py•••Trying to reuse the update scripts used by kakoune/vim to provide the
user with an unified convergence. Some stuff doesn't work yet (parallel
download, caching) but I (anyone else welcome to try too) will improve
it in other PRs.
| Matthieu Coudron | 2021-08-09 | 1 | -1/+1 |
| * | vimPlugins.nvim-treesitter: document plugins | Guillaume Girol | 2021-07-18 | 1 | -1/+28 |
| * | doc: prepare for commonmark•••We are still using Pandoc’s Markdown parser, which differs from CommonMark spec slightly.
Notably:
- Line breaks in lists behave differently.
- Admonitions do not support the simpler syntax https://github.com/jgm/commonmark-hs/issues/75
- The auto_identifiers uses a different algorithm – I made the previous ones explicit.
- Languages (classes) of code blocks cannot contain whitespace so we have to use “pycon” alias instead of Python “console” as GitHub’s linguist
While at it, I also fixed the following issues:
- ShellSesssion was used
- Removed some pointless docbook tags.
| Jan Tojnar | 2021-06-07 | 1 | -10/+10 |
| * | Include custom package in vim docs (#92811)•••Describe how to package a plugin that doesn't exist in nixpkgs (and also how to include an external file).
Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com> | Adrian Hesketh | 2021-04-20 | 1 | -0/+38 |
| * | doc/languages-frameworks/*: add missing languages to code fences•••convert shell -> ShellSession
| Sandro Jäckel | 2021-04-05 | 1 | -4/+4 |
| * | doc: explicit Markdown anchors for top-level headings; remove metadata•••I used the existing anchors generated by Docbook, so the anchor part
should be a no-op. This could be useful depending on the
infrastructure we choose to use, and it is better to be explicit than
rely on Docbook's id generating algorithms.
I got rid of the metadata segments of the Markdown files, because they
are outdated, inaccurate, and could make people less willing to change
them without speaking with the author.
| Ryan Mulligan | 2021-01-01 | 1 | -6/+1 |
| * | vimPlugins: document update proces | Austin Butler | 2020-10-28 | 1 | -0/+14 |
| * | vimPlugins: Document node-based plugins | Jake Waksbaum | 2020-09-04 | 1 | -0/+2 |
| * | vimPlugins: update auto-commiting based on review•••- Use git.Repo(ROOT, search_parent_directories=True) to find nixpkgs
repo.
- Don't commit overrides.nix.
- Remove "-a" short argument.
- Remove "--commit" flag and commit by default.
- Improve help/error messages.
- Favor closure pattern over classes.Use a closure to wrap the update
function with state rather than a callable class.
- break NixpkgsRepo class into functions
- Optional None-type arguments
- Remove repo checks from update.py. Git is too flexible and permits too
many workflows for my attempt to replace documentation with code to work.
My goal would be to separate the `--add` functionality from the update
functionality in the near term and then there will be no reason for this
usage to create commits anyway.
| ryneeverett | 2020-04-01 | 1 | -1/+1 |
| * | vimPlugins: update.py --add <plugin> argument•••- update.py's new --add argument replaces manual editing of
vim-plugin-names for basic use cases.
| ryneeverett | 2020-04-01 | 1 | -6/+1 |
| * | vimPlugins: automatically commit update | ryneeverett | 2020-04-01 | 1 | -1/+1 |
| * | doc: organize chapters into parts, and reduce toc depth•••Reorganize the chapters into parts and reduce the TOC depth to make the
TOC useful again. The top-level TOC is very brief, but that is fine
because every part will have its own TOC.
Section titles of languages/frameworks are also simplified to just
the name of the language/framework.
| Frederik Rietdijk | 2019-10-20 | 1 | -1/+1 |
| * | Cleanup formatting in Vim plugin docs | Malo Bourgon | 2019-07-14 | 1 | -63/+78 |
| * | Update documentation about adding new Vim plugins to nixpkgs | Malo Bourgon | 2019-07-14 | 1 | -10/+17 |
| * | treewide: Change URLs to HTTPS•••Lots of URLs were HTTP redirect to HTTPS. Changed those and checked them
if there's actual content. Inspired by
https://github.com/NixOS/nixpkgs/issues/60004
| Daniel Schaefer | 2019-04-22 | 1 | -1/+1 |
| * | doc: add neovim-qt configuration | Timo Kaufmann | 2019-01-06 | 1 | -0/+15 |
| * | vimUtils: add dependency logic to nativeImpl•••nativeImpl previously simply ignored dependency information.
| Timo Kaufmann | 2018-12-24 | 1 | -1/+6 |
| * | clarifying `name` arg determines vim command name•••The `name` arg of `vim_configurable.customize` does not only determine
the package name, but also the name of the command/ executable to be
called.
In my opinion this is not documented properly and finding that out took
me several hours.
| Trolli Schmittlauch | 2018-10-24 | 1 | -0/+4 |
| * | doc/vim: remove some vim-plug redundancy | Jörg Thalheim | 2018-09-20 | 1 | -21/+3 |
| * | doc: Add section about vim-plug | Roman Volosatovs | 2018-09-20 | 1 | -1/+49 |
| * | vim-plugins: rewrite updater•••A new python script has been added to replace the aged viml-based
updater. The new updater has the following advantages:
- use rss feeds to check for updates quicker
- parallel downloads & better caching
- uses proper override mechanism instead of text substitution
- update generated files in-place instead of having to insert updated plugins manually
Automatically reading `dependencies` from the plugins directory has been
not re-implemented.
This has been mostly been used by Mark Weber's plugins, which seem to
no longer receive regular updates.
This could be implemented in future as required.
| Jörg Thalheim | 2018-09-09 | 1 | -0/+12 |
| * | doc/vim: improve plugin documentation | Jörg Thalheim | 2018-09-09 | 1 | -8/+62 |
| * | Move all nixpkgs doc files in to the doc directory•••This makes a makefile-driven developer workflow nicer.
| Graham Christensen | 2018-03-25 | 1 | -0/+135 |
