about summary refs log tree commit diff
path: root/pkgs/aszlig/vim/default.nix
Commit message (Collapse)AuthorAgeFilesLines
* vim: Remove setting g:rustc_pathaszlig2024-03-251-4/+1
| | | | | | | | | | | | Having a fallback rustc executable in my Vim closure at all times looked like a good idea in the first place, but since g:rustc_path is only used for things like :RustRun it is of very limited use (only for standalone Rust files). I had exactly *zero* uses for that since I introduced it, so there is really no need to bloat the closure size for something I don't use. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Don't rustfmt without an explicit configaszlig2024-03-251-2/+4
| | | | | | | | | | | This is getting annoying when contributing to external projects that don't have a rustfmt.toml, because I constantly forget to disable it for a buffer and then get a massive diff that I need to revert. My own projects all have a rustfmt.toml anyway, so there really is no reason to do it by default nor have a custom rustfmt config in Vuizvui. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Update Nix syntax/indent to latest masteraszlig2024-01-091-2/+2
| | | | | | | | Not only were there a lot of smaller fixes in the meantime, but latest master now properly supports the (not so) new (anymore) path interpolation syntax. Signed-off-by: aszlig <aszlig@nix.build>
* vim/markdown: Remove dircolors syntaxaszlig2023-03-311-2/+2
| | | | | | | | | | | | The syntax file in question queries features from the current terminal and will bring editing Markdown files to a crawl, freezing Vim for more than ten seconds. I haven't encountered a dircolors(1) file within a Markdown fenced code block yet and even if this should be the case someday it's not worth the high runtime cost. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add quick-scope pluginaszlig2022-09-181-0/+7
| | | | | | | | | | | | Found this thanks to @fpletz starring the repository and since I constantly use f/F and t/T when navigating, I decided to give it a try. Usually when trying things, I'd just add the Vim version with the plugin to my local Nix profile, but since I'm already irritated when other things than the cursor are highlighted in the current line, I decided to do something completely irrational and just add it to all my machines. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Remove hex and color names highlightingaszlig2022-08-231-0/+5
| | | | | | | | | | | | We only want to highlight #aabbcc-style hex colors and not every damn hex value that happens to be 3 or 4 bytes, which is very annoying when you're doing a lot of bit manipulation. Additionally, I currently have a code base where "gold" is something a player can have, so one doesn't need much imagination on how irritating that is. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Use postFetch instead of extraPostFetchaszlig2022-08-151-3/+3
| | | | | | | | | | | | | | | | We no longer need to use extraPostFetch in order to append stuff to the postFetch phase of fetchzip. Since this got fixed[1], we now get appropriate warnings during evaluation: warning: use 'postFetch' instead of 'extraPostFetch' with 'fetchzip' and 'fetchFromGitHub'. Neither do we like warnings nor do we like to use workarounds from the past that got fixed, so let's fix it on our side as well :-) [1]: https://github.com/NixOS/nixpkgs/pull/173430 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Fix elflord color themeaszlig2022-06-221-7/+40
| | | | | | | | | | | | | I know, I know, people don't like the color scheme I use, but I got so used to it and with the new version generated via ColorTemplates it messes with me being used to elflord with 16 terminal colors instead of the GUI colors. So this patches elflord in such a way that it's consistent with what I want but still uses the new ColorTemplates version, which for example comes with nicer colors for vimdiff. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add rustfmt with custom default configaszlig2022-02-091-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | Since I do have a lot of projects where I use rustfmt, it gets pretty tedious to manually run "cargo fmt". Using g:rustfmt_autosave should make this less tedious but it might annoy me in the future, let's see. In addition to setting rustfmt I also added a default path for rustc, which is used whenever there is no rustc in path. This is because I usually switch between several projects which use different Rust versions and this way it will use the rustc version that is in PATH during "nix develop". For the rustfmt part I also added a small default configuration which represents my opinion on how I think Rust code should be formatted. The file is used whenever a project doesn't have a "rustfmt.toml" or ".rustfmt.toml". Unfortunately, RustFmt is broken in Vim right now[1], so I'm using the upstream project until the issue has been resolved. [1]: https://github.com/rust-lang/rust.vim/issues/446 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Update tlib plugin to latest masteraszlig2021-09-301-2/+2
| | | | | | | | | | | | | Since Vim version 8.2.3141, the following error is raised during startup: Error detected while processing .../share/vim/vim82/plugin/02tlib.vim: line 109: E1208: -complete used without allowing arguments The latest version of the tlib plugin provides a fix for the above error, so I'm updating it to latest master. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Fix color for LightBlue in color schemeaszlig2021-07-271-0/+1
| | | | | | | | | | | | If we use 256 color mode in XTerm, using LightBlue in Vim results in 0x5fd7ff but LightBlue in GUI mode will use 0xadd8e6 which has a low contrast to the default color (0xbebebe). Since my eyes are not getting better with age, I decided to go with the old color code that provides better contrast even though I'm quite happy with the rest of the "more nuanced" colors. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Replace vim-css-color by hexokinaseaszlig2021-07-091-6/+31
| | | | | | | | | | | | | | | | | | So far vim-css-color worked quite well for what I wanted, but after talking to @devhell about possible alternatives, I stumbled upon hexokinase and tried it a bit. One of the gripes I had with things such as colorizer is that it highlights colors regardless of the file types we're in, which in turn will also highlight things where the hash character is not a hex value, for example in Erlang's base notation for integers. Hexokinase also highlights all file types but first of all, it only highlights things separated by word boundary and also it's way less obtrusive because the way I've configured it only the hash character is highlighted, not the whole color value. Signed-off-by: aszlig <aszlig@nix.build>
* workstation: Advertise XTerm true color capabilityaszlig2021-07-091-2/+13
| | | | | | | | | | | | | | | | | | So far, the TERM environment variable has been set to xterm-256color, but in reality newer XTerm versions already supported 24bit colors so setting this to xterm-direct results in using the right terminfo entry for our terminal. To make sure this is really the case, let's explicitly set directColor to true, because while it is enabled in nixpkgs by default it is however a compile-time option and could possibly be disabled. Additionally, Vim is now looking pretty gruesome because my colorscheme so far has used colors for 16-color terminals and I don't particularly like the GUI colors. I added a few fixups for the color scheme to address that. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add highlighting for Markdown code blocksaszlig2021-07-091-1/+116
| | | | | | | | | | | | | | | | | | | | | | While I could have done this simply by setting the g:markdown_fenced_languages variable, I instead decided it would be a better idea to use the same language names that GitHub recognises via their GitHub Flavored Markdown syntax. Since they're using Linguist, I decided to simply import the YAML file and try to match them against existing Vim syntax files. That way, we only need to maintain a blacklist of languages we do not want and should pretty much get highlighting for all supported languages. Unfortunately, the "markdown.vim" syntax file sources all of the syntax files for these languages and so the more languages we include there, the slower it gets when opening a Markdown file. Right now, I mostly use this for editing textareas, so let's see how annoying the slower load time will get and blacklist more languages later if it bugs me too much. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Fix Fish syntax fileaszlig2021-07-091-5/+5
| | | | | | | | | | | | The file in question actually was a ZIP file, which instead of being unpacked got directly moved to syntax/fish.vim and in turn caused errors whenever the filetype was set to "fish". Instead of just fixing up the ZIP file I switched to a GitHub repository that seemed to be maintained a lot more (last commit in 2020) than the one we had so far (last change 2013). Signed-off-by: aszlig <aszlig@nix.build>
* aszlig/vim: Switch to dedicated plugin for Jinja2aszlig2021-07-021-7/+5
| | | | | | | | | | | | | | | | The Vim syntax highlighting plugin file is no longer[1] shipped with Jinja2 version 3.x, so the build fails accordingly with: install: cannot stat 'ext/Vim/jinja.vim': No such file or directory In another upstream pull request[2] one of the project members mentioned another syntax plugin which apparently seems to be more up to date. This is what I'm hereby switching to as a replacement. [1]: https://github.com/pallets/jinja/pull/1196 [2]: https://github.com/pallets/jinja/issues/1007 Signed-off-by: aszlig <aszlig@nix.build>
* programs/vim: Add syntax highlighting for GDScriptaszlig2020-12-041-0/+7
| | | | | | | | | Added this when contributing to a GDScript project and since I know a few persons who implement their games using Godot, I might need to write GDScript at some point in the future again, so the syntax highlighting plugin comes in handy. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add syntax/indent plugin for Fluentaszlig2020-08-141-0/+7
| | | | | | | | | | | | For translations there is a nice web interface called Pontoon[1], which should it make conventient to edit translations. However, for developers like me I'd call this quite inconvenient, so I need a Vim plugin to make it at least more pleasing to look at :-) [1]: https://github.com/mozilla/pontoon Signed-off-by: aszlig <aszlig@nix.build>
* vim: Update Nix addon to latest masteraszlig2020-08-081-2/+2
| | | | | | | | | | | | While being at it, let's bump the Nix syntax/indentation plugin to the latest version, since there are a few quirks that were annoying me since quite a while but I was too lazy to actually fix. I haven't checked whether the latest version fixes these quirks since I don't know them on top of my head, but if it doesn't I surely will stumble on them soon enough. Signed-off-by: aszlig <aszlig@nix.build>
* vim: No longer set termencoding to "ascii"aszlig2020-08-081-1/+0
| | | | | | | | | | So far I had termencoding set to "ascii", because my terminal was only really able to display ASCII characters and nothing else. Since this is no longer the case, we can also get rid of this restriction in my Vim configuration. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add vim-css-color pluginaszlig2020-05-081-1/+12
| | | | | | | | | | | | | This is quite useful in CSS files and others to directly highlight the colours in the actual colour value rather than with the generic colour of the syntax file. To make sure we don't break the after/syntax files for Haskell and HTML, I also changed the way we install those files in the output directory so that if a file already exists, it is appended to rather than overwritten. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Remove file artifacts for ATS syntax pluginaszlig2020-05-081-2/+3
| | | | | | | | | | | We essentially only want to have the ftdetect and syntax files, everything else is just cruft that is not in any way related to Vim. Ideally we want to do a whitelist approach instead of the "remove everything unneeded" we're doing right now, but since I don't want to refactor the whole Vim expression I'll leave it the dirty[TM] way. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add syntax highlighting/indent for PureScriptaszlig2019-10-121-0/+7
| | | | | | | | This probably needs a bit of refinement when it comes to indentation, but at least we get proper syntax highlighting, which is the main point here. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Exempt xt and strace from linelen highlightaszlig2019-08-031-2/+2
| | | | | | | | Both strace and xt are trace log formats, so imposing my own distaste for overly long line length won't make a difference, as they won't change their "coding style" ;-) Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add syntax highlighting for Xdebug tracesaszlig2019-08-031-0/+13
| | | | | | | | Unfortunately these days I have to debug a lot of PHP code, so having syntax highlighting (even though the syntax file is pretty terse) and being able to fold Xdebug traces is quite useful to have. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add syntax highlighting for Jinja2aszlig2019-06-111-0/+9
| | | | | | | Jinja2 seems to be quite popular these days for all sorts of templates, so let's actually use the syntax file from the actual Jinja2 package. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add syntax/indent configuration for PHPaszlig2019-06-111-0/+7
| | | | | | | | | | | | | | Unfortunately, I need to deal with PHP code occasionally, so let's make syntax highlighting less painful. I'm not sure why the option is called PHP_vintage_case_default_indent, but I prefer case statements to be indented. Apart from HTML/SQL syntax highlighting within PHP strings, I also want to prevent short open tags, so that whenever I stumble on code using it I can immediately fix them. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Use flake8 from python3Packagesaszlig2018-10-131-2/+2
| | | | | | | | Constantly getting errors on type hints and "unknown" print() arguments is very annoying, especially because I almost exclusively use Python 3 nowadays. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add syntax highlighting for mesonaszlig2018-10-021-1/+12
| | | | | | | | | | | The upstream project already provides a Vim plugin so we only need to reference that using the existing meson.src attribute. However, I needed to patch out a very annoying thing, which would echom every time the indentexpr is called. Most likely this was left in for debugging. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Update Nix pluginaszlig2018-09-131-2/+2
| | | | | | | This includes a revert of the recent indentation changes which introduce more problems than they actually solve. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add indentation fixes for Nix expressionsaszlig2018-08-171-2/+2
| | | | | | | | | | | | | | This basically switches the source to my pull request with a few fixes for indentation: https://github.com/LnL7/vim-nix/pull/19 The main annoyance was that writing "with ...;\n\nlet" was indented one level deeper and I'm regularly writing small Nix expressions with something like this, eg. to quickly test things or abuse the Nix sandbox for programs I don't want to run unsandboxed ;-) Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add syntax highlighting for Vue.jsaszlig2018-08-051-0/+28
| | | | | | | This is used by Habitica and for maintaining my fork I sometimes[TM] unfortunately have to edit .vue files. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Update Nix pluginaszlig2018-08-021-6/+10
| | | | | | | | | | | | | | | | This is mainly to catch up with the syntax highlighting fixes that were done in the respective plugins. The setlocals in ftplugin/nix.vim from LnL7's plugin are now gone and it's one setlocal with line continuation, so I had to turn the simple grep into a small sed script. Another thing I added while at it is to add the single quote to iskeyword, because it can be part of a Nix identifier. I did that by replacing the dash, because the latter now is part of the setlocal of the aforementioned ftplugin. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Don't autoalign Ledger files anymoreaszlig2018-05-021-2/+1
| | | | | | | | | | | I've introduced this in 45aab49b33ab2cd4c327b996d6924f104b038193. It turns out that autocomplete_and_align when leaving insert mode is more annoying than useful, because first of all I use hledger and it's syntax additions and second I also use different currencies, which then get aligned and autocompleted into "something with EUR". Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Enable folding for Ledger filesaszlig2018-04-231-0/+2
| | | | | | | | My main hledger file already contains a lot of entries even though I just started using hledger, so folding all of that crap away seems to be a good idea. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add a few exceptions for sleuthaszlig2018-04-231-0/+5
| | | | | | | | | | | | | | | | | | | | This has annoyed me for a while now, especially when writing Haskell code. Let's say if I have something like this: foo :: Num a => a -> a foo a = b where b = a + 1 Sleuth will detect that the indentation level is 2 spaces, but in reality what I want is to have it at 4 spaces. So turning off Sleuth will solve that problem, especially because we can still invoke it manually. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add plugin for Ledgeraszlig2018-04-231-1/+20
| | | | | | | | | | | The plugin really is for Ledger instead of hledger, but both should be compatible with the syntax. If we use something that's not compatible we can still patch it in. I also set the default currency to Euro and added an auto-align after leaving insert mode because I'm lazy ;-) Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Remove vimErl pluginaszlig2018-01-091-7/+0
| | | | | | | This one is no longer required and the syntax and indent files are already part of Vim since version 7.4. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add syntax and ftdetect files for ATSaszlig2017-10-061-0/+12
| | | | | | | | | Unfortunately the syntax file is a bit incomplete it's the best that I've found online, so I'll stick with it for the time being. Thanks to @Profpatsch for bringing ATS to my attention :-) Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Clean up autocommandsaszlig2017-09-051-13/+13
| | | | | | | | | | | | I was using set for a bunch of these, but these autocommands are only used for single buffers so let's actually make sure they are set only there by using setlocal. In addition to that I've corrected usage of '==' to use '==#', because '==' actually depends on user settings whether it's case sensitive or not (set ignorecase). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Add sleuth plugin for indent detectionaszlig2017-09-051-0/+7
| | | | | | | | I work with a lot of differente repositories and different indentation styles, so I hope this plugin will help cope with that so I no longer need to set those settings manually. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Add plugin for editing CSV filesaszlig2017-09-051-2/+16
| | | | | | | | | | | I happen to work with CSV files quite a bit lately but it's a major nuisance doing so with a normal text editor and I don't want to use a full-blown spreadsheet programm just for a few CSV files or even write a script every time I need to edit only a tiny bit. So this plugin solves that problem for me. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Be more agressive with including pluginsaszlig2017-09-051-22/+33
| | | | | | | | | | | Originally I only wanted to make sure the ftplugin gets loaded before the syntax file, but while at it I thought just prepending/appending stuff to the runtimepath is not enough for me. So now my version of Vim has all the plugins directly in the standard directories just as if they came with upstream. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Update vim-nix to latest master versionaszlig2017-07-311-2/+2
| | | | | | | The current master contains a few fixes with indentation which I regularly hit while writing Nix expressions. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Add vim-multiple-cursors pluginaszlig2017-07-251-0/+7
| | | | | | | | | While I find visual (block) mode quite useful, it doesn't cope well if you have multiple lines that aren't aligned perfectly. This plugin adds that missing feature. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Switch Haxe plugin to vaxeaszlig2017-07-241-12/+9
| | | | | | | | | | | | | | | | The Haxe plugin(s) I've used so far (vim-haxe and vim-haxe-syntax) are no longer actively maintained since 2014. On the other hand "vaxe" is based on the work on vim-haxe and vim-haxe-syntax, is actively maintained and supports newer language features of Haxe as well. I've patched out syntax highlighting for ',' and ';', because I really get eye cancer with this and reminds me a bit about the annoying bold colons when using nickname completion back in the days where BitchX users were widely seen on IRC. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Wrap lines at 79 chars instead of 80aszlig2017-07-241-4/+4
| | | | | | | | | | The reason is that for terminals that have a width of 80 characters, having a line with exactly 80 characters will wrap it. I've wrapped most of my code in 79 characters since a while manually, so it's time to enforce this by the editor. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Set history size to 500 linesaszlig2017-07-241-0/+1
| | | | | | The default is 50, which is a bit small for my taste. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* pkgs/vim: Add flag to skip defaults.vimaszlig2017-07-241-0/+1
| | | | | | | | This one is annoying because it enables mouse mode and it's sourced *after* our defined configuration. Setting skip_defaults_vim disables this behaviour. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/aszlig: Make vim module a plain packageaszlig2017-07-241-0/+376
I don't use anything that's machine specific within my Vim configuration (and even if, we can pass it via the callPackage arguments) so it's kinda pointless that it's a module instead of a plain package (override). This makes it also easier to nix-build the package without the need to go through the module system. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-01 12:08:15 +0000