| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
calling `execlineb -c` has unfortunate quoting issues, cause for
cornercases like arguments that contain spaces or `"` the result would
be a completely broken command line.
Instead, let’s do our own block construction in a small rust
program (for speed). I tried implementing it in bash first but even
prepending spaces to a string is a complete waste of time in that
language.
|
|
|
|
| |
Interesting take on an `nmap` replacement.
|
|
|
|
|
| |
I'm really happy to have found `mnamer`, it's a bit like `beets`, but
for TV series and movies.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm already using this config since a few months and since I'm slowly
getting used to it, let's try to make it the default for my workstation
profile.
Unfortunately, libgit2 uses the Git configuration from /etc, but our
configuration is directly patched into Git and not in /etc but in
"${pkgs.git}/etc", so we need to patch libgit2 to use the right
configuration file.
Another goof is that we can't use ${pkgs.delta} directly in our Git
configuration because it would introduce a circular dependency between
Git itself and delta (which uses libgit2 which in turn refers to
"${pkgs.git}/etc"), so for the time being I'm relying on $PATH for
delta.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
Duh.
This reverts commit 2d8ad8d8d158f5c4d1e3085062ec4619a18416c9.
|
|
|
|
| |
There's really no need to keep this exposed on the internal network.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
I don’t remember why I set that limit, but it’s kinda silly since nix
uses all cores by default.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The output is a bit cleaner and overall it seems to execute faster.
|
| |
|
|
|
|
| |
Neat `ps` alternative.
|
|
|
|
| |
Seems that it suffered the same fate as `pastel`, for now.
|
|
|
|
|
|
|
| |
- `rq` is similar to `jq` but works with more types
- `watchexec` is neat to execute stuff on file change
- `wuzz` is a bit like burpsuite, but on the commandline
- `xsv` is just for CSV and has it's own specific functionality
|
|
|
|
|
| |
Always loved this font a little bit. Not as cool as the ultimate
oldschool fonts, but still.
|
|
|
|
| |
I don't know why, but I enjoy testing new tools replacing old tools.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
I'm not interested in shadows on everything.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regression introduced in 709e45c2a8c231201d3f67c6a954021ca2a5f796.
With that commit I renamed the "config" option to be called "settings",
but not only that, the actual config *file* is now to be found in the
"configFile" option.
Unfortunately I forgot to change that reference, which caused an
evaluation error.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
While ncurses already has support for detecting direct color terminals,
a lot of applications out there do not yet query terminfo but instead
rely on some shady COLORTERM environment variable. While I don't really
like that approach, patching XTerm to set that variable currently is
better than patching all the applications to query terminfo.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far, we have passed self instead of super to our custom package set,
but this makes it very hard when overriding other packages and refering
to one of these packages in Vuizvui.
To fix this, I not only used mkBefore to make sure that the overlay
comes before every other overlay but also using super makes sure that
whenever we do overrides in Vuizvui, the package *before* the current
overlay is selected instead of possibly running into an infinite
recursion.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
This makes it hard to do static analysis on the code and it's really not
needed here, so let's use lib.X directly.
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>
|
|
|
|
|
|
|
|
| |
I haven't used the alias since a long time as it is probably apparent
due to the hardcoded "14.04" version of NixOS and given that I didn't
update the alias also speaks volumes about how useful it is altogether.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using vimdiff3 as the merge tool for a long time, but while it
has worked fine for most conflicts, using diff3 makes the original lines
visible which I always viewed in a separate shell rather than inline in
the editor.
Switching this to diff3 should hopefully make merge conflicts more
convenient to solve from now on.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In RFC-0042[1], the structural settings are exposed via a "settings"
attribute, while in our module it's called "config". To make this less
ambiguous (since there is already a "config" attribute passed to
modules) and more in line with best practices, I renamed it accordingly.
Additionally, the configuration file is now generated via *defining*
another (read-only) option, which can be used by other modules to
reference the path. The previous way this has been done was using the
apply attribute to mkOption, which makes it really hard to access the
original attributes for these settings.
[1]: https://git.io/JcXmU
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
This gets rid of bringing all of the lib attribute into the scope of the
whole module and also refactors a bit of ugliness, for example we're now
using overrideAttrs instead of overrideDerivation.
In addition I've simplified the type for the configuration, which should
now make it possible to mix subsubsections with normal subsections.
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 `colorizer` plugin doesn't produce accurate results, so I'll try
`vim-css-colors`. It's also looking more maintained than the previous
plugin.
|
|
|
|
|
|
|
|
|
| |
I know that both `nixops` and `blender/expat` fixes are in staging, so
I'm just reverting this one to ensure that eventually there will be
fresh build. Currently `pastel` isn't building, so there's little point
in trying to skirt around this.
This reverts commit 4f73711332cc2220333dcf3eaccdd74c8cc61e10.
|
|
|
|
|
|
| |
The dependency issue has been fixed, so back to using Blender! Whoop!
This reverts commit 41cc1ddf2c2c0f69737bfe9ca144f0d0d2f3a26c.
|
|
|
|
| |
I've gotten used to delta enough to not need the diff alias.
|
|
|
|
| |
I need something sane to control application/file handling.
|
|
|
|
|
| |
Without this, the kernel tries to use `mq-deadline` for gunnr. The
invocation for eir was wrong anyway, so this should fix it.
|
|
|
|
|
|
|
|
|
| |
The user shouldn't have direct access to the /dev/snd/* but go through
things such as pulseaudio or pipewire. I added the user to that group
back then as a workaround to quickly get something[TM] working, but
nowadays it's not needed anymore.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
Both, `herja` and `gunnr` have no spinning rust in them, and so they
won't need bfq anymore. According to this old benchmark, the `none`
scheduler works overall better for most workloads than other
schedulers[1].
[1]: https://www.phoronix.com/scan.php?page=article&item=linux-56-nvme&num=1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Hopefully more sane than `element-desktop`.
|
|
|
|
|
| |
So, `xh` is really great, but I was wrong in thinking it's a perfect
drop-in replacement for `curl`.
|