~tachi

Italy

https://andrea.pappacoda.it

Faccio cose

~tachi/public-inbox

Last active 1 year, 4 months ago
View more

Recent activity

Re: Relicensing aerc to GPL 1 year, 3 months ago

From Andrea Pappacoda to ~rjarry/aerc-devel

On Mon Feb 20, 2023 at 6:59 PM CET, Robin Jarry wrote:
> Could you please respond to this message stating whether you accept or
> refuse the change of license from MIT to GPL[2] for the aerc project.
> This will only affect future versions of aerc. Existing releases will
> remain with their original license (MIT).

Hi Robin, I don't know if I was Bcc'd or if I received this because I'm
subscribed to aerc-devel, as I only sent a really small patch.

In any case, you're free to relicense my small contribution under the
GPL2, or under the terms of any license of the GPL family if you so
wish.

I look forward to notmuch integration out of the box! Thank you very

Re: [PATCH aerc] colorize: use a more colorful default theme 1 year, 3 months ago

From Andrea Pappacoda to ~rjarry/aerc-devel

On Sun Jan 29, 2023 at 5:36 PM CET, Robin Jarry wrote:
> Moritz Poldrack, Jan 29, 2023 at 17:14:
> > I think it is better to use the terminal palette by default, as it is 
> > more compatible and more configurable. It might be preferable to add 
> > this as a separate styleset (called "old-awk" or something).
>
> I personally don't care much. The old-awk theme is already part of the 
> blue and pink stylesets.
>
> The argument was to be more appealing to new users:

Yeah exactly. The old-awk theme has the advantage of being quite nice
without having to configure anything, while the terminal theme, as you
say, can be configured. As configurability is an advantage of the

Re: [PATCH] filters: make colorize URL regex more strict 1 year, 3 months ago

From Andrea Pappacoda to ~rjarry/aerc-devel

On Sat Jan 28, 2023 at 11:11 PM CET, Robin Jarry wrote:
> I removed the paragraph and added your Signed-off-by line myself. I hope 
> that is OK.
>
> Acked-by: Robin-Jarry <robin@jarry.cc>
>
> Applied. Thanks!

Perfect, thank you!

> I'll submit the patch myself, we'll see if someone has anything to say. 
> The new filter has not been released yet, I would be surprised if 
> bleeding edge users did mind at all ;)

Re: [PATCH] filters: make colorize URL regex more strict 1 year, 3 months ago

From Andrea Pappacoda to ~rjarry/aerc-devel

Hi Robin, thanks for the quick reply!

On Sat Jan 28, 2023 at 6:42 PM CET, Robin Jarry wrote:
> > awk script: https://imgur.com/1vlnxnD.png
> > colorize.c before: https://imgur.com/wvYLvwi.png
> > colorize.c after: https://imgur.com/GDKPFAs.png
>
> Are these screenshot URLs guaranteed to be valid in 5 years? If not, 
> I can apply the patch but remove that last paragraph (if that is OK with 
> you).

Yeah, I too think that those imgur links kinda suck, but I couldn't
think of a better alternative. Realistically speaking, I'm quite
confident that imgur will still be available in 5 years, but they do not

[PATCH] filters: make colorize URL regex more strict 1 year, 3 months ago

From Andrea Pappacoda to ~rjarry/aerc-devel

The previous URL regex was too lax, allowing all "[:graph:]" characters
after the protocol:// part. This caused the script to mark as part of an
URL also things like ">", which is commonly used as a URL delimiter in
plain text and Markdown; the url() function tried to account for this
with some heuristic to remove trailing characters, but it didn't always
work (see the screenshots below).

As RFC3986 specifies the list of allowed characters in URLs, we can
simply make our regex stricter and only mark characters as part of an
URL if they match the allowed set. As the number of allowed characters
has been reduced, the aforementioned heuristic has been slightly
simplified.

I've also removed the backslash escapes from the bracket expressions,
[message trimmed]

Re: [PATCH] Implement b_coverage 1 year, 4 months ago

From Andrea Pappacoda to ~lattis/muon

Il giorno mer 18 gen 2023 alle 16:28:03 +00:00:00, ermine 
<mustela@erminea.space> ha scritto:
> +	COMPILER_ARGS({ "--coverage", "-fprofile-abs-path" });

Hi ermine, thanks for the patch. Meson doesn't seem to pass 
-fprofile-abs-path when enabling b_coverage; why are you passing it 
here by default? What benefits does it provide?

[PATCH] simplify .reuse/dep5 1 year, 5 months ago

From Andrea Pappacoda to ~lattis/muon

The Files field supports multiple file paths, so there's no need to
create a stanza per path when the Copyright and License fields are the
same.
---
Also note that only the Format field is required in the header, so
you're free to remove Upstream-Name, etc. if you want. Some people find
them redundant.

 .reuse/dep5 | 24 ++++--------------------
 1 file changed, 4 insertions(+), 20 deletions(-)

diff --git a/.reuse/dep5 b/.reuse/dep5
index 5a34bf72..17621240 100644
--- a/.reuse/dep5
[message trimmed]

[PATCH useplaintext.email v2] State that Geary supports bottom posting 1 year, 5 months ago

From Andrea Pappacoda to ~sircmpwn/public-inbox

Geary supports bottom posting, but only if you highlight the portion of
the message you want to quote. See
<https://mail.gnome.org/archives/geary-list/2016-July/msg00013.html>.
---
 index.html | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index dca4ef3..ec52198 100644
--- a/index.html
+++ b/index.html
@@ -293,7 +293,7 @@
    <div class="breakdown">
      <span class="green">Compose in plaintext</span>
[message trimmed]

[PATCH useplaintext.email] State that Geary supports bottom posting 1 year, 5 months ago

From Andrea Pappacoda to ~sircmpwn/public-inbox

Geary supports bottom posting, but only if you highlight the portion of
the message you want to quote. See
<https://mail.gnome.org/archives/geary-list/2016-July/msg00013.html>.
---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index dca4ef3..d32e37b 100644
--- a/index.html
+++ b/index.html
@@ -293,7 +293,7 @@
    <div class="breakdown">
      <span class="green">Compose in plaintext</span>
[message trimmed]

Re: Implement semantic versioning for easier packaging 1 year, 9 months ago

From Andrea Pappacoda to ~lattis/muon

Replying here after seeing [#67].

I'm looking into packaging muon for Debian, and all the issues found 
while packaging (i.e. the bootstrap phase ignoring {CPP,LD}FLAGS and 
some minor typos) have been already fixed.

The only issue left is not something that can be fixed here, and is the 
fact that the "muon" name is already used by [another package], KDE 
Muon, for both the package name and /usr/bin/muon.

I've briefly [discussed] this conflict on the debian-devel mailing 
list, and the only possible solution would be to ask the Qt/KDE package 
maintainers to rename the current /usr/bin/muon to something else, 
possibly muon-kde, as the program is likely launched by a .desktop file