| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
A simple text letter formatter (A4) for printing.
|
| |
|
|
|
|
| |
The concept of a transparent handler wasn’t actually used anywhere and
now that we want to generate the firefox json as well, it just hinders
us from doing that in an easy way.
|
| |
|
|
|
|
| |
The type string would blow up too much if you can’t reference any
dhall file in the sources list. This all feels a bit hacky, but at
least semantically it seems to work out?
|
| |
|
|
|
|
|
| |
No use in passing through the mime type now that we can just directly
render the commands in the protocol handlers.
This gives us the base for generating the Firefox handlers.json.
|
| |
|
|
| |
Removes the duplication of command handlers.
|
| |
|
|
|
|
|
|
|
| |
This diff is a bit bad cause of whitespace changes, but effectively
this copies all handlers into the mime handler definitions and
duplicates them for now.
We want to use the same config to generate a firefox mime handler
file.
|
| | |
|
| |
|
|
|
|
| |
testRustSimple wouldn’t work with all the rust functions, so let’s
just use it internally and expose the tests via the conventional
`doCheck` attribute instead.
|
| |
|
|
| |
Just to prove I can.
|
| |
|
|
|
|
|
|
| |
The -T flag is GNU coreutils specific, for s6-ln and POSIX ln, the equivalent
seems to be -L which mandates behavior like linkat(3) with the AT_SYMLINK_FOLLOW
flag.
cc @Profpatsch
|
| | |
|
| |
|
|
| |
It was unused and required a broken hnix pin.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We had a bunch of instances of
https://github.com/NixOS/nix/issues/2176,
where nix would exit with a “killed by signal 9” error.
According to Eelco in that issue, this is perfectly normal behaviour
of course, and appears if the last command in a loop closes `stdout`
or `stdin`, then the builder will SIGKILL it immediately. This is of
course also a perfectly fine error message for that case.
It turns out that mainly GNU coreutils exhibit this behaviour …
Let’s see if using a more sane tool suite fixes that.
|
| |
|
|
|
|
|
|
|
|
| |
Port of <https://cl.tvl.fyi/c/depot/+/2657>. Original message:
`forstdin` iterates over the tests in the test directory, and by
default it does *not* fail if an inner loop returns an error, unless
`-o okcodes` is given, a list of exit codes that indicate success.
Now it fails if a loop returns ≠ 0.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These are the scripts I used to print my gpg private key onte a bunch
of A4 papers, as QR codes of the paperkey output.
It also contains an example of how to automatically read it back in
with a ScanSnap „Einzugsscanner“. I think there also was a test that
checks that the full roundtrip works :)
The QR codes generation was designed in a way that they contain the
highest amount of data when printed on A4 paper, while still being
high-redundancy enough that you can destroy about 1/4th of them before
they become unreadable.
The key was also printed as plain paperkey format, so in the worst
case when I don’t have a scanner I can type it in by hand.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I think nman is of general interest, so general pointers on setting
it up may be useful for others.
|
| |
|
|
|
| |
Should give the user more information about what exactly went wrong in
the event of a store path being garbage.
|
| |
|
|
|
|
|
|
|
|
| |
Instead of generating n hypothetical filenames for the man page we
search for and checking if one of them exists, we now iterate through
the files in the man dir we are checking and match each of them against
our desired man page and section.
I feel like this makes the code more cumbersome, but on the upside it is
now more unit-testable.
|
| | |
|
| |
|
|
|
|
|
| |
This is parsing and rendering of stuff currently mostly, since our main
logic is relatively interwoven with IO stuff (to avoid copying stuff a
lot). This is fine however as the application logic is tested using the
nixos vm test we also have!
|
| | |
|
| |
|
|
| |
Now shortest is listed first.
|
| |
|
|
|
|
|
|
|
| |
This relieves us of the burden to print the error message and lets the
user see what's going on, for example why they have to wait for years
when running `nman duplicity` (we have to fetch all transitive python
dependencies). We also print the exit status in case of errors and
the signal that killed a process (in the case of SIGKILL, SIGSEGV and
maybe more?).
|
| | |
|
| |
|
|
|
|
|
| |
In the Profpatsch universe, execline reigns surpreme. Therefore we must
bow to its (understandable) rejection of POSIX and use 100 as the user
error instead of the 64 of sysexits.h. This makes a lot of sense, as we
are already using execline conventions for the other exit codes.
|
| |
|
|
|
|
|
|
| |
We want to discourage scripting with nman, as we may want to tweak the
user interface or internal behavior of nman in the future without
maintaining backwards compatibilty.
In other words: You have been warned.
|
| | |
|
| |
|
|
| |
(as suggested by Profpatsch)
|
| | |
|
| |
|
|
|
| |
Just copy path instead of having a harder to maintain reset mechanism.
Copying strings is not really a performance concern in this case.
|
| |
|
|
|
|
|
| |
We reuse std::io::Error's Display trait to print precisely the error
that occurred to the user as well. This will probably help a lot if an
IO error should ever occurr, as they will only ever occurr in very weird
situations (mktemp(3) failed or share/man is not a readable directory).
|
| | |
|
| |
|
|
| |
Proof-reading would be very welcome!
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes share/man contains directories that are not of the form
man<section> which we are checking in build_man_page. However, this
check can't deal with directories that are shorter than 3 characters due
to the use of split_at() which panics if the index is out of range (for
somer reason…).
In nixpkgs it is relatively common to have directories like "de" in
share/man.
This has been resolved.
|
| |
|
|
|
|
|
|
|
| |
The path field wasn't used in DrvWithOutput as we only ever needed
rendered. rendered however is a bit of a confusing name as it is not in
fact fully rendered in all cases. Since we can pass rendered to
nix-store --realise without preprocessing in all cases we rename it to
path and add a note in the documentation. The old path field is removed
for this without replacement.
|
| |
|
|
|
| |
* parse_drv_output → DrvOutput::parse
* parse_drv_path → DrvWithOutput::parse
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, we would always assume section 1 was requested if no section
was given on the command line. Now the section is treated as if it was
unknown and we search for a matching man page by looking through the sub
directories of $output/share/man.
This means the following invokation works as expected:
nman libunwind unw_getcontext
instead of requiring
nman libunwind 3 unw_getcontext
|
