| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
* Delete patched mandoc derivation and documentation.mandoc module from
the tree, both have an equivalent upstream now.
* Activate upstreamed documentation.man.mandoc module in my machines.
|
| |
|
|
|
|
| |
forgot to commit this the first time around
|
| |
|
| |
|
|
|
|
| |
This should do the trick.
|
|
|
|
| |
Argh
|
| |
|
|
|
|
|
|
|
|
| |
The hydra still doesn’t like the import:
error: "\u001b[31;1merror:\u001b[0m\u001b[34;1m --- RestrictedPathError --- hydra-eval-jobs\u001b[0m\naccess to path '\u001b[33;1m/nix/store/b6ba70kcrvnxq165h791l71wvmdj2qy1-prepare-tvl\u001b[0m' is forbidden in restricted mode"
So let’s try this.
|
| |
|
| |
|
|
|
|
|
| |
We don’t want any builtins.fetchgit stuff from random domains,
hopefully this will fix the current eval error.
|
|
|
|
| |
All relevant patches have made it into a release finally!
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This pulls in tvl, since the blog ist mostly over there.
It uses `fetchGit`, so caveats may apply. It shouldn’t increase
evaluation times very much, since the blog only uses a small subset of
tvl.
https://github.com/openlab-aux/vuizvui/issues/50 might apply.
|
| |
|
|
|
|
|
|
| |
Also make sure libreoffice is only installed/pulled when clicking on
the link (although there could be a popup of sorts if it has to do
stuff …).
|
|
|
|
| |
This makes it usable outside of the module; should be a pure refactor.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This uses the system monospace font to generate a PDF. Before the
printer would be sent a .txt, and it varies from printer to printer
how plain text files are typeset (if at all). Now it only depends on
the system monospace font, which is SourceCode Pro in my case (obvious
TODO is to fix that sometime, or make it configurable).
|
| |
|
|
|
|
|
| |
Sync the calendar every 15 minutes with a user service, and add ics
file support to xdg-open.
|
|
|
|
|
|
|
|
|
|
| |
This has been renamed[1] to reflect the upstream name and since there is
no alias for the old name, we need to rename it as well to avoid
evaluation errors.
[1]: https://github.com/NixOS/nixpkgs/commit/41574158a07f3c6ab5853b316c2fe7ed18e6354b
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
It is quite useful. Nice to see there is a good one around for vim.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
Still not giving up on a sensible markdown plugin.
|
| |
|
|
|
|
| |
The READ_ALLOWED_PATH patch was applied 🥳
|
|
|
|
| |
https://inbox.vuxu.org/mandoc-tech/c9932669-e9d4-1454-8708-7c8e36967e8e@systemli.org/T/#m445439360d5fbe71849001e39ce1e78a8a7d024f
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|
|
|
| |
Looks useful, let's see.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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 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 `colorizer` plugin doesn't produce accurate results, so I'll try
`vim-css-colors`. It's also looking more maintained than the previous
plugin.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
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.
|
| |
|