~akspecs

/dev/null

gemini://akspecs.srht.site

i like pragmatic minimalism

~akspecs/example

Last active 3 months ago

~akspecs/numbeo-scraping-dev

Last active 6 months ago

~akspecs/aqoli-dev

Last active 6 months ago

~akspecs/bancroft-1906-discuss

Last active 1 year, 2 months ago

~akspecs/public-inbox

Last active 1 year, 2 months ago
View more

Recent activity

Re: [PATCH aerc] filters: colorize: use solarized colors 2 months ago

From akspecs to ~rjarry/aerc-devel

On Thu Mar 10, 2022 at 1:23 AM PST, Robin Jarry wrote:
> Shaleen Jain, Mar 10, 2022 at 10:17:
> > Hi,
> >
> > While it is reasonable to expect users to further customise the
> > colors of their preference by copying the script, I just wanted to
> > provide sane defaults that work in the broadest scenario, that is
> > user having both a dark and light background.
> >
> > In any case I'm fine if you decide not to include this patch.
>
> That is a fair point. I will think some more about this. Directly
> editing the script is probably not very user friendly.

Re: [PATCH aerc v2] readme: add more details about the review process 2 months ago

From akspecs to ~rjarry/aerc-devel

On Mon Feb 28, 2022 at 1:22 PM PST, Robin Jarry wrote:
> ---
> v1 -> v2:
>  * removed the real name requirement.
>  * added precisions about who is allowed to ack or review patches.

lgtm!

Acked-by: akspecs <akspecs@gmail.com>

Re: [PATCH aerc] readme: add more details about the review process 2 months ago

From akspecs to ~rjarry/aerc-devel

On Sun Feb 27, 2022 at 4:35 PM PST, Robin Jarry wrote:
> * All patches must be signed-off using your real name.

Maybe this can be elaborated on?  There are many reasons why a dev would
prefer to use a pseudonym, especially considering we are using a
platform with a community that generally respects user and developer
privacy.

> * All patches must receive at least one independent review and approval
>   before being applied.

Makes sense.  However, if you could elaborate on one thing: say in a
situation where I agree with a feature a new patchset introduces, and I
go as far as testing said patch(es), but I haven't truly reviewed the

Re: [PATCH aerc v2] pipe: allow piping multiple marked messages 2 months ago

From akspecs to ~rjarry/aerc-devel

On Thu Feb 24, 2022 at 4:15 PM PST, Robin Jarry wrote:
> When messages are marked, pipe their contents into the specified
> command. The messages are ordered according to their respective
> Message-Id headers. This allows applying complete patch series with
> a single command.
>
> When piping more than one message, make sure to write them in the mbox
> format as git am expects them to be.
>
> Link: https://en.wikipedia.org/wiki/Mbox
> Link: https://github.com/git/git/blob/v2.35.1/builtin/mailsplit.c#L15-L44
> Signed-off-by: Robin Jarry <robin@jarry.cc>
> ---
> The bug I encountered with v1 should be fixed by this other patch:

Re: [PATCH aerc v3] threading: implement on-the-fly message threading 3 months ago

From akspecs to ~rjarry/aerc-devel

On Thu Feb 24, 2022 at 2:15 AM PST, Robin Jarry wrote:
> inwit, Feb 24, 2022 at 11:02:
> > It works beautifully. Thanks!
>
> Can I add the following to the committed patch?
>
> Tested-by: inwit <inwit@sindominio.net>

i've also been running and testing said patch as soon as it landed in my
mailbox, if having more than one Tested-by: trailer is desirable.

Re: [PATCH aerc v3] threading: implement on-the-fly message threading 3 months ago

From akspecs to ~rjarry/aerc-devel

On Wed Feb 23, 2022 at 3:41 PM PST, Koni Marti wrote:
> implement message threading on the message store level using the
> jwz algorithm. Build threads on-the-fly when new message headers arrive.
>
> Use the references header to create the threads and the in-reply-to
> header as a fall-back option in case no references header is present.
>
> Does not run when the worker provides its own threading (e.g. imap
> server threads).
>
> Include only those message headers that have been fetched and are
> stored in the message store.
>
> References: https://www.jwz.org/doc/threading.html

Re: [PATCH aerc] search/filter: display in extra status 3 months ago

From akspecs to ~rjarry/aerc-devel

On Tue Feb 22, 2022 at 12:23 PM PST, inwit wrote:
> On Tue Feb 22, 2022 at 8:21 PM CET, Robin Jarry wrote:
> > Set that extra status after a successful :search or :filter. Remove it after
> > :clear.
> Thanks, Robin. However, after a quick test, the status message is cleared
> completely for both filter and search immediately after any key is pressed.
> This might be fine for search, but, as I said, I believe it's a good idea to
> retain some visual indication that the folder we're seeing has been filtered.
>
> Also, as messages, I'd go for "Filter cleared." and "Search cleared." instead
> of "Clear complete."

i've also just tested this patch and it will clear the filter status
line after running the :clear command.  very nice!

Re: search/filter: remove from status bar after 20 seconds 3 months ago

From akspecs to ~rjarry/aerc-devel

On Mon Feb 21, 2022 at 5:03 AM PST, inwit wrote:
> [...] the patch I was referring to:
> https://git.sr.ht/~rjarry/aerc/commit/e3842033904af9f4fc0e829b6f23de0579453052

> > Robin Jarry wrote:
> > > The status is not cleared. It is annoying.

it is annoying, especially when the filter has been cleared
(using :clear), but the statusbar still has the old filter
displayed.  that is what happened prior to the referenced commit.

> > Imho, clearing the search from the status bar is mostly ok since the
> > message list doesn't change, but there's an issue with removing the
> > info after a filter has been applied: with no information, the user

Re: aerc 0.8.0 3 months ago

From akspecs to ~sircmpwn/aerc

On Sun Feb 20, 2022 at 5:01 PM PST, Paul Vixie wrote:
> Robin Jarry wrote:
> > I have replaced that filter with a python script. I did not think
> > about people pointing directly to it with awk in their config.
> > 
> > I should probably restore the original awk script and rename the new
> > python filter to preserve backwards compatibility.
>
> it's odd to me to depend on python in any form, in an app written in 
> golang, for the command line. i don't have python installed except on my 
> mailman server, and i may be the norm for once.
> others and possibly myself from having an unwanted python dependency.

Robin restored the original awk script and renamed the new python filter

Re: aerc 0.8.0 3 months ago

From akspecs to ~rjarry/aerc-devel

On Sun Feb 20, 2022 at 5:01 PM PST, Paul Vixie wrote:
> Robin Jarry wrote:
> > I have replaced that filter with a python script. I did not think
> > about people pointing directly to it with awk in their config.
> > 
> > I should probably restore the original awk script and rename the new
> > python filter to preserve backwards compatibility.
>
> it's odd to me to depend on python in any form, in an app written in 
> golang, for the command line. i don't have python installed except on my 
> mailman server, and i may be the norm for once.
> others and possibly myself from having an unwanted python dependency.

Robin restored the original awk script and renamed the new python filter