| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
polymake: 4.8 -> 4.9
|
|
gromacs: 2022.4 -> 2023
|
|
torq: build frontend
|
|
|
|
gfold: 4.2.0 -> 4.3.0
|
|
oxker: 0.2.1 -> 0.2.3
|
|
|
|
|
|
git-machete: 3.14.3 -> 3.15.0
|
|
callaudiod: 0.1.4 -> 0.1.7
|
|
yquake2: 8.10 -> 8.20
|
|
folly: 2022.11.28.00 -> 2023.01.30.00
|
|
zita-alsa-pcmi: 0.5.1 -> 0.6.1
|
|
geekbench: 5.4.5 -> 5.4.6
|
|
snabb: 2022.10 -> 2022.12
|
|
python310Packages.pyisy: 3.1.11 -> 3.1.13
|
|
r-ryantm/auto-update/python310Packages.py-synologydsm-api
python310Packages.py-synologydsm-api: 2.1.2 -> 2.1.4
|
|
graalvm*-ce: wrap native-image to pass -H:CLibraryPath, misc improvements
|
|
mvapich: 2.3.6 -> 2.3.7
|
|
r-ryantm/auto-update/python310Packages.azure-mgmt-datalake-store
python310Packages.azure-mgmt-datalake-store: 0.5.0 -> 1.0.0
|
|
r-ryantm/auto-update/python310Packages.browser-cookie3
python310Packages.browser-cookie3: 0.16.5 -> 0.17.0
|
|
nixos/envfs: use configured environment.usrbinenv and environment.binsh, add extraFallbackPath options
|
|
|
|
yubico-piv-tool: 2.3.0 -> 2.3.1
|
|
|
|
|
|
oh-my-posh: 13.8.0 -> 14.2.3
|
|
|
|
|
|
mariadb_1010: init at 10.10.2
|
|
this is mainly useful for restricted platforms like wsl which require
some extra entries in /bin/
|
|
zoom-us: 5.13.5.431 -> 5.13.7.683
|
|
Diff: https://github.com/jandedobbeleer/oh-my-posh/compare/refs/tags/v13.8.0...v14.2.3
Changelog: https://github.com/JanDeDobbeleer/oh-my-posh/releases/tag/v14.2.3
|
|
python310Packages.pontos: 23.2.0 -> 23.2.4
|
|
|
|
now that the renderer produces the output we want to keep for the future
we can add a test that checks all of its features. this test notably
does not include markdown headings since we don't want to have those in
manpages (at least right now), but tests for other converters may add
headings for themselves.
|
|
for the longest time we completely dropped link targets in
configuration.nix.5. let's stop doing this now and instead provide a
footnote for each link in a given option, numbered locally per option.
we will currently duplicate the link for <labelless-links> because it
makes it easier to get the collection of all links in a given option.
this may not be useful enough, so over time we might decide to drop the
footnotes for such links.
|
|
this matches what html outputs do more closely, and feels like it'll be
easier to read because it looks less like just another paragraph.
|
|
indent the entire list by 4, just like each definition is already
indented by 4. this matches rendering in html, which indents terms once
and indents definitions twice.
|
|
similar to inline code these were indistinguishale from other text.
render then in italic font instead, like mdoc .Pa does.
|
|
other output types already have markings for inline code, manpages do
not. this can be somewhat confusing, so we'll do the least intrusive
thing: surrounding inline code blocks in ‘’. doing so separates inline
code from the rest of the text and is unlikely to collide with the
quoted contents. it's also what mdoc does with its Ql macro.
|
|
this is a holdover from docbook stylesheets. not really sure why they
did that.
|
|
no reason to differentiate between links by source of their label. this
feature seems to be mostly used to change labels of links to other
options, but this should ultimately be done by auto-linking from
{option}`...`. at some point we may want to introduce a warning when
this pattern is encountered, but there's a lot to work out still before
we can do that.
|
|
most of the lists in option docs are actually compact, but docbook to
manpage processing always rendered them as non-compact. compactifying
these lists improves readability somewhat since most lists and their
contents are pretty short.
|
|
mdoc is just too slow to render on groff, and semantic markup doesn't
help us any for generated pages.
this produces a lot of changes to configuration.nix.5, but only few
rendering changes. most of those seem to be place losing a space where
docbook emitted roff code that did not faithfully represent the input
text, though a few places also gained space where docbook dropped them.
notably we also don't need the compatibility code docbook-xsl emitted
because that problem was fixed over a decade ago.
this will handle block quotes, which the docbook stylesheets turned into
a mess of roff requests that ended up showing up in the output instead
of being processed.
|
|
|
|
Token.attr is a dict[str, str | int | float], meta has no restriction on
the value type. attrs is ostensibly meant for html attributes, meta for
any information whatsoever.
|
