~renerocksai

Nuremberg, Germany

https://renerocks.ai

Software and electronics engineer turned AI & robotics researcher.

~renerocksai/aercbook

Last active a day ago

~renerocksai/telekasten.nvim-devel

Last active 1 year, 4 months ago

~renerocksai/vib

Last active 1 year, 6 months ago

~renerocksai/telekasten.nvim-discuss

Last active 1 year, 6 months ago

~renerocksai/come-to-sourcehut

Last active 1 year, 7 months ago

~renerocksai/GH-to-SH

Last active 1 year, 7 months ago

~renerocksai/telekasten.nvim-announce

Last active 1 year, 7 months ago

~renerocksai/ssh-docker-cr

Last active 1 year, 7 months ago

~renerocksai/real-prog-qwerty

Last active 1 year, 7 months ago

~renerocksai/slides

Last active 1 year, 7 months ago
View more

Recent activity

Re: [PATCH] Fix parser crash on header lines shorter than 5 characters 2 days ago

From Rene Schallner to ~renerocksai/aercbook

Thank you for your patches!

Will apply and release probably in the evening
(local, German time).

Yeah, assuming line length was a bad idea. Thx for the quick fix!

19.02.2024 11:05:26 Max Schillinger <max@mxsr.de>:

> This crash happens at header lines like
> 
> X-Provags-ID: V02:K0:jLG+n5RvqvXDfnaT86MCMCzjw0nIUzH7tOoFF3O0git
> nBPsfi4RZ56LhzW8NuyICLlpqUs+VgNKykpfuZo5jHVjY53Qw=
> =

Release v0.1.5 3 days ago

From Rene Schallner to ~renerocksai/aercbook

Thanks to Max Schillinger pointing out some shortcomings,
aercbook now handles more line-continuations, and
base64-encoded (rfc1341) utf-8 names.

Short-Log:

Rene Schallner (2):
      Parser: allow line-continuations with space char
      support rfc1341 utf8

AW: Problems with parsing 3 days ago

From Rene Schallner to ~renerocksai/aercbook

> 2. Line continuations are ignored (only for wrapped contacts?).
> 3. Sometimes contacts are added in a broken way.

> See this example for all three issues at once:

> $ echo 'To: =?UTF-8?B?5byg5LiJ?= <zhang.san@example.com>, "John Doe"
> <john.doe@web.de>, "Schillinger, Max"
> <maximilian.schillinger@example.com>' \
>    | aercbook /tmp/aercbook-test.txt --parse --add-to
>
> Warning error.FileNotFound: /tmp/aercbook-test.txt --> creating it...
>
> Added "John Doe -> "John Doe
> Added =?UTF-8?B?5byg5LiJ?= -> =?UTF-8?B?5byg5LiJ?= <zhang.san@example.com>

AW: Problems with parsing 3 days ago

From Rene Schallner to ~renerocksai/aercbook

> $ cat /tmp/aercbook-test.txt
>
> "John Doe : "John Doe
> =?UTF-8?B?5byg5LiJ?= : =?UTF-8?B?5byg5LiJ?= <zhang.san@example.com>
>
> Searching also has some issues:
>
> 4. Based on `/tmp/aercbook-test.txt`, I get the same output, no matter
> what I search for:
>
> $ aercbook /tmp/aercbook-test.txt zhang
> $ aercbook /tmp/aercbook-test.txt example
> $ aercbook /tmp/aercbook-test.txt xxx
> $ aercbook /tmp/aercbook-test.txt '*'

AW: Problems with parsing 3 days ago

From Rene Schallner to ~renerocksai/aercbook

Thx for bringing that to my attention.

Aercbook is in a "works for me" state.

I will try to update it when I have time, where finding time is the biggest issue, as I am super busy and my need to update is low.

When writing aercbook, I did check out the RFC, trying to cover all relevant cases, and have never had to deal with that weird re-encoding of utf8 names.

But great that you came up with an alternative, so now there are options!

I briefly checked out your solution and its readme. There, I found the statement about the lines of code a bit surprising. I'll probably get rid of the vendored-in args parser and its tests, which would cut sloc in half and we're just a shortcut. If you argue less lines of code are better, e.g. for maintainability (?), you'll probably find that the actual aercbook code is quite straight-forward, explicit, and manageable. Not like an "over 1000 lines of fragile code mess".

But 150 lines of posix shell I find a bit misleading as well because of the sed, awk and even perl dependencies (decoding re-encoded utf8 names). I deliberately didn't want to write aercbook in python (re-using python's lines of code to reduce mine) to avoid dependencies. If you compile aercbook with musl, you get a static executable: 0 runtime dependencies, not even glibc - which I value a lot, using tools like aerc and aercbook in isolated nix (as in NixOS) environments. Such static executables (for baseline CPU architecture) can also be released and copied to other Linux systems and will work there, too, no matter what is installed.

Re: [PATCH] fix zig-v0.11 breaking changes 5 months ago

From Rene Schallner to ~renerocksai/aercbook

Hi Coco,

Amazing work! Thanks a lot! This is what I was just about to attempt -
and then I saw your flagged message in my aerc 😊. This is just what I
needed! Now I can hack away trying to fix that potential bug I
encountered with commas within FROM names.

Thanks a lot for this great contribuiton!
-Rene
_______________________________________________________________________
On Wed Sep 6, 2023 at 10:30 AM CEST, Coco Liliace wrote:

> ---
> README.md | 6 +++---

Re: Fwd: Re: aercbook build 5 months ago

From Rene Schallner to ~renerocksai/aercbook

_______________________________________________________________________
On Thu Mar 16, 2023 at 5:21 PM CET, Coco Liliace wrote:

> On Wed Mar 8, 2023 at 4:55 PM EST, Coco Liliace wrote:
> > On Wed Dec 28, 2022 at 7:55 AM EST, Rene Schallner wrote:
> > > I just pushed the `zig-0.10` branch which is a tiny back-port of
> > > `zig-master` for the latest "stable" release of zig: zig-0.10. I
> > > downloaded the binary zig-0.10 and verified that it works.
> >
> > Thank you for the work! Can you also make it into a new release please?
> > I'm trying to publish this on the Alpine Linux package repository
> > (aports), and the request just got rejected for not using an actual
> > release:
> >

Re: aercbook build 1 year, 1 month ago

From Rene Schallner to ~renerocksai/aercbook

Hi,

Sorry, my bad! Zig currently is in heavy development and not everything
is stable yet. Regarding aercbook, I used to get away with pointing to
zig-0.9 as being the latest release but this doesn't work anymore.

A few days ago, I pushed the `zig-master` branch to the aercbook
repository which works with the current zig-master (zig-0.11).

I just pushed the `zig-0.10` branch which is a tiny back-port of
`zig-master` for the latest "stable" release of zig: zig-0.10. I
downloaded the binary zig-0.10 and verified that it works.

I'll update the README soon and probably also merge `zig-0.10` into

Re: Migration status 1 year, 4 months ago

From Rene Schallner to ~renerocksai/telekasten.nvim-devel

> > Will check out how to give you write access to issues.

I just checked. todo.sr.ht says I gave you access to everything: browse,
submit, comment, edit, triage two months ago. So I don't know why you
can't edit labels. Maybe that's an oversight at SourceHut? I access the
labels in the `labels` tab, next to `closed tickets`. There, on the left
hand side, I can `Add label`, for instance.

This applies to the telekasten.nvim issue tracker which I am sure you
meant...?

However, I planned to migrate the GitHub issues over to SourceHut before
actually using issues on SourceHut. Now that we've been on SourceHut for
a while, it's understandable that you use the tracker there, too.

Re: Open message in a browser 1 year, 4 months ago

From Rene Schallner to ~rjarry/aerc-discuss

> AERC opens Firefox if I want to read a message in a browser, but I want
> to use Chromium, how do I do it?

I'm sure it's not aerc that associates HTML with Firefox but rather your
system setup.

Anyway, check out the `:pipe` command to pipe the HTML part (needs to be
selected) to another program.

To see an example, you might want to check out vib [0].

[0] : https://sr.ht/~renerocksai/vib/