| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
This includes a revert of the recent indentation changes which introduce
more problems than they actually solve.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
The current master contains a few fixes with indentation which I
regularly hit while writing Nix expressions.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
The default is 50, which is a bit small for my taste.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
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>
|
|
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>
|