This implementation is still very basic. For reference, e.g. mozilla has
published a more fleshed out variant of such an algorithm:
<https://github.com/mozilla/unicode-slugify>.
Change-Id: Id3d76a4f9e976952dd3c98835df0de7c4f86c3bc
Reviewed-on: https://cl.tvl.fyi/c/depot/+/13108
Autosubmit: sterni <sternenseemann@systemli.org>
Reviewed-by: sterni <sternenseemann@systemli.org>
Tested-by: BuildkiteCI
We can use ! in R to display the error instead.
Change-Id: Ib7f6e559014e3f99a9f99c159a31a45a7a0e65a5
Reviewed-on: https://cl.tvl.fyi/c/depot/+/13105
Reviewed-by: sterni <sternenseemann@systemli.org>
Autosubmit: sterni <sternenseemann@systemli.org>
Tested-by: BuildkiteCI
The array listing was pretty nice for debugging, but having arrays where
every element has a different meaning as an interface between different
parts of the code is not great. Refactoring will be less frustrating if
we just store everything using a key-value scheme in namespaces.
Change-Id: I806fea247b6f996dbdd93df24f3fdb762340f043
Reviewed-on: https://cl.tvl.fyi/c/depot/+/13017
Autosubmit: sterni <sternenseemann@systemli.org>
Tested-by: BuildkiteCI
Reviewed-by: sterni <sternenseemann@systemli.org>
We can actually get all the headers we are interested in just one call
of mhdr(1) since it can query multiple headers in multiple messages in
just one call. With BQNs reshape / two dimensional array facilities it
is easy to group the lines of headers by their originating message and
append the original path to the result array.
We still use a separate mhdr(1) call for the Date header since we rely
on the -D option for parsing the header.
Change-Id: Iaaf8f21fa22ab3e32e6900df4ae164e72c722cd3
Reviewed-on: https://cl.tvl.fyi/c/depot/+/13016
Reviewed-by: sterni <sternenseemann@systemli.org>
Tested-by: BuildkiteCI
Autosubmit: sterni <sternenseemann@systemli.org>
Currently, blërg is an incomplete reimplementation of
//users/sterni/mblog that uses mblaze(7) and //users/sterni/mn2html to
process the backing mail notes.
Now, why start from scratch again?
- mblog is depressingly slow at the moment which is due to
//third_party/lisp/mime4cl. The performance problems are
(probably) solvable, but this would require carefully
redesigning the library's use of streams. I'm not motivated
to look into that at the moment, unfortunately.
- I had an idea for intergrating additional storage backends
for entries into an mblog like software. I've found experimenting
with this in BQN to be quite pleasant as the backends can
easily be expressed as namespaces.
Change-Id: I90c8ff7b5f7235d6fd7b0619338b553be8742e49
Reviewed-on: https://cl.tvl.fyi/c/depot/+/13015
Autosubmit: sterni <sternenseemann@systemli.org>
Tested-by: BuildkiteCI
Reviewed-by: sterni <sternenseemann@systemli.org>
