| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
It’s hard-coded as the default case in our script already, this was
breaking that functionality.
|
|
|
|
|
|
|
|
|
| |
The way store paths are queried has changed significantly in Nix 2.4, so
we need to completely refactor nix-query.cc. However, I currently have a
lot of other things to do and the store protocol is compatible so let's
pin Nix to version 2.3 for the sandbox implementation for now.
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>
|
|
|
|
| |
I'm using org mode for these kinds of things now.
|
|
|
|
|
|
| |
If you want to use multiple binaries (e.g. via `pkgs.symlinkJoin`),
this will work via PATH instead of magically tranforming the first
argument instead.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Takes an additional argument and looks that argument up in the
respective nix build result directory bin dir.
Also add some documentation.
|
| |
|
|
|
|
|
| |
It’s always a mistake to forget a block here, so this will give a
better error message.
|
|
|
|
| |
It’s not worth the indirection.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* 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.
|