Jarkko Sakkinen
Posts
4887Following
324Followers
491OpenPGP: 3AB05486C7752FE1
Jarkko Sakkinen
jarkko
i wanted to change the name of my html mail tool multidepart as it is used by some funding organization or similar:
https://www.eiturbanmobility.eu/projects/multidepart/
the new name is mailweb as it is a tool that literally does that i.e., it converts text/html mail to a static website (despite archaic) ;-)
https://crates.io/crates/mailweb
also bumped the minor to add clarity for the change.
https://www.eiturbanmobility.eu/projects/multidepart/
the new name is mailweb as it is a tool that literally does that i.e., it converts text/html mail to a static website (despite archaic) ;-)
https://crates.io/crates/mailweb
also bumped the minor to add clarity for the change.
0
0
0
Jarkko Sakkinen
jarkko
Through some indeterministic process that I don't understand from time to time I have to "warn up" gpg to not fail on "git tag -s" like this:
❯ git tag -s ihatemylife
error: gpg failed to sign the data
error: unable to sign the tag
The tag message has been left in .git/TAG_EDITMSG
~/work/codeberg.org/jarkko/multidepart main ⇡
❯ gpg -s README.md
After the latter command, tag signing suddenly works.
#git #gpg #yubikey
❯ git tag -s ihatemylife
error: gpg failed to sign the data
error: unable to sign the tag
The tag message has been left in .git/TAG_EDITMSG
~/work/codeberg.org/jarkko/multidepart main ⇡
❯ gpg -s README.md
After the latter command, tag signing suddenly works.
#git #gpg #yubikey
0
0
1
improvements with less confusing lifetimes for async is definitely a thing for me. i've been doing about 2.5-5 k line systemd daemon for a lttile while and there's a few places where i need to weird shit for compiler. i'm only now learning 2024 features but this was that i was hoping for. in some (luckily rare) cases it is not really about not grabbing borrow check, lifetimes or whatever. i need to check if i simplify some locations :-)
0
0
0
Jarkko Sakkinen
jarkko
i've been using 2021 edition of rust up until now because i only now realized that i need to run rustup update occasionally :-)
i was wondering for months shouldn't 2024 be out and why i'm stuck with 2021 edition lol.
rust starts to be mature enough that probably once next version is debian is out i start to use distro toolchain (if kernel requires newer my [buildroot](https://codeberg.org/jarkko/linux-tpmdd-test) shenanigans will provide me a toolchain :-) ), which is like where any native language should evolve.
this is what i do with python i.e., work in the limits of distribution packaged stuff. it makes software translate more easily and your upstream is in a way always ready for packaging.
i was wondering for months shouldn't 2024 be out and why i'm stuck with 2021 edition lol.
rust starts to be mature enough that probably once next version is debian is out i start to use distro toolchain (if kernel requires newer my [buildroot](https://codeberg.org/jarkko/linux-tpmdd-test) shenanigans will provide me a toolchain :-) ), which is like where any native language should evolve.
this is what i do with python i.e., work in the limits of distribution packaged stuff. it makes software translate more easily and your upstream is in a way always ready for packaging.
1
1
1
Jarkko Sakkinen
jarkko
great now the deps are in the reasonable level for this type of tool :-) (and meson replaced with plain make).
using cjson was not a great idea in the first place as when doing json output for small and trivial low-level tools like this instead of dumping big continuous json string is also really the best option (vs pretty printing).
maybe i soon tag a release and put this debian packaging pipeline :-)
using cjson was not a great idea in the first place as when doing json output for small and trivial low-level tools like this instead of dumping big continuous json string is also really the best option (vs pretty printing).
maybe i soon tag a release and put this debian packaging pipeline :-)
0
0
0
Jarkko Sakkinen
jarkko
@cehteh @codrusofathens i don't think i have any use for these trait tutorials (just saying). i've disassembled enough rust binaries by now what kind of assembly code those construct generate. having a de-facto choice is not same as ultimate choice or a choice that could not change (based on testing that brings to light actual performance regressions not theoretical language spec based).
2
0
0
probably in the ballpark :-) https://codeberg.org/jarkko/multidepart/src/branch/main/README.md
0
0
0
Jarkko Sakkinen
jarkko
Edited 3 months ago
I’m using mutt so need to ask this before updating readme.
This what I have for mutt:
macro index F10 "<pipe-message>multidepart --browse\n" "View HTML in browser"
macro pager F10 "<pipe-message>multidepart --browse\n" "View HTML in browser"
This is what I presume would be correct for aerc (in ~/.config/aerc/binds.conf):
[messages]
F10= :pipe -p multidepart --browse<Enter>
[view]
F10= :pipe -p multidepart --browse<Enter>
Does that look about right?
1
0
1
@gregkh I think softer recommendations/practices would go a long way. I would not want to use machine readable tokenized system for log messages. For that something like eBPF is probably a better idea :-) And using klog "as instrumentation protocol" (or that kind of picture I got from your description) is scary idea from security standing point.
1
0
0
This is like continuation to https://github.com/puavo-org/lsiommu i.e., mainly goal is to rip off random scripts :-)
1
0
0
Jarkko Sakkinen
jarkko
This is along the lines clone of viewhtmlmail (popular among #mutt users).
https://codeberg.org/jarkko/multidepart
It's pretty much done for crates.io at least :-)
#email
https://codeberg.org/jarkko/multidepart
It's pretty much done for crates.io at least :-)
1
1
0
Even in kernel log messages are total chaos. It would be also bad if they were forced to be some weird tokenized structure (aka machine readable) and they loose their purpose, and you can store that type of history data elsewhere tuned for the application.
The middle-ground would be to define recommendations choice of words, vocabulary and grammar to apply in broadly defined scenarios. This would especially help in projects such as kernel where non-native speaker might have difficulties to figure out the "right language" by instinct.
Thus, it would relax the project ecosystem more than it would make it more constrained, as you don't have to spend too much energy in such a low priority topic, and focus on important matters.
The middle-ground would be to define recommendations choice of words, vocabulary and grammar to apply in broadly defined scenarios. This would especially help in projects such as kernel where non-native speaker might have difficulties to figure out the "right language" by instinct.
Thus, it would relax the project ecosystem more than it would make it more constrained, as you don't have to spend too much energy in such a low priority topic, and focus on important matters.
1
0
0