~liliace

https://liliace.dev

that was my first patch. please be gentle

~liliace/public-inbox

Last active 1 year, 5 months ago
View more

Recent activity

Re: <C-h> unbindable in 0.18.0 7 months ago

From Coco Liliace to ~rjarry/aerc-discuss

On Tue Jul 16, 2024 at 10:36 PM CST, Tim Culverhouse wrote:
> So the issue is that tmux is sending Ctrl+h as 0x08 (which is correct). Vaxis is
> translating this to a backspace keypress - because some terminals use 0x08 as
> backspace. *Most* use 0x7F as backspace nowadays.
>
> Tcell was using terminfo to decide which of those two keys was actually
> backspace - which is why it worked there. Vaxis doesn't use terminfo so it isn't
> privvy to this knowledge and assumes that both 0x08 *and* 0x7f are backspace.
>
> I think this might be worthy of changing though. It's very uncommon to find a
> terminal which uses 0x08 as backspace - and they almost universally allow
> configuring this (tmux included).

Hi Tim,

Re: <C-h> unbindable in 0.18.0 7 months ago

From Coco Liliace to ~rjarry/aerc-discuss

On Tue Jul 16, 2024 at 9:09 PM CST, Tim Culverhouse wrote:
> What terminal are you using, and are you inside a tmux session at all?

Hi Tim!

I'm using tmux in the foot terminal.
The bug only exists when I am in a tmux session.
The <C-h> binding works as expected in foot.

Sorry I just realized I forgot to cc the mailing list when I replied the
info above yesterday 😬.

Thank you!
Coco

<C-h> unbindable in 0.18.0 7 months ago

From Coco Liliace to ~rjarry/aerc-discuss

Hi!

I noticed that my <C-h> keybinds stopped working after upgrading to
0.18.0. I've read through the changelog and it didn't look like an
intended deprecation.

I believe it is an issue with the new version and not my terminal
capturing <C-h>, since I tried downgrading to 0.17.0, and the <C-h>
worked again.

I've tried mapping other commands to <C-h> and none of them worked.
The log I got from aerc > aerc.log shows that the mapped commands never
got triggered so I believe it is an issue with capturing the keybinds.

Re: release request 1 year, 10 months ago

From Coco Liliace to ~ghost08/photon

On Wed Mar 29, 2023 at 12:30 PM EDT, Vladimír Magyar wrote:
> Version v1.0.0 released :)

Thank you! It is published now :)
https://pkgs.alpinelinux.org/packages?name=photon*

Coco

release request 1 year, 10 months ago

From Coco Liliace to ~ghost08/photon

Hello,

Thank you for the project. I like it so much I would like to put it on
Alpine Linux's package repository. On Alpine, they usually ask the
package to have a release instead of cloning a random git commit
version. Can you please make a release of photon? Then I can help put it
into an APKBUILD file for alpine and maintain it :)

Coco

Re: Code Span Rendering on man.sr.ht 1 year, 11 months ago

From Coco Liliace to ~sircmpwn/sr.ht-discuss

I'm in support of this idea as well. For those who need this feature as
a reader, you can probably find a browser extension that lets you write
custom css for specified sites. For example, on Firefox, there is
Stylus^[0]. The css below works pretty well for me:

```css
code {
  background: #eee;
  border-radius: 3px;
  padding: 1px 3px;
}
```

However, as a writer, I hope we can still update this, since I cannot

Re: How is Mime-Version set? 1 year, 11 months ago

From Coco Liliace to ~rjarry/aerc-devel

On Sat Feb 25, 2023 at 10:51 PM EST, Coco Liliace wrote:
> I'd like to try submitting a patch for this, though it may take some
> time as I'm still learning Go :)

The go-message developer suggested leaving it as is and fixing it from
the email provider's side. So I will not submit a patch for this after
all. Sorry for the troubles and thanks again for tracking this down.

https://github.com/emersion/go-message/issues/165#issuecomment-1445388235

Coco

Re: How is Mime-Version set? 1 year, 11 months ago

From Coco Liliace to ~rjarry/aerc-devel

On Sat Feb 25, 2023 at 10:11 AM EST, Tim Culverhouse wrote:
> This converts 'MIME-Version' to 'Mime-Version'. It would be difficult to fix
> this in go-message, because it's using the call to
> textproto.CanonicalMIMEHeaderKey in a lot of places, but a wrapper around it
> is probably best, and then replace all the internal calls to textproto to the
> wrapper.

Thank you for tracking this down and providing a helpful starting point!
I'd like to try submitting a patch for this, though it may take some
time as I'm still learning Go :)

Coco

How is Mime-Version set? 1 year, 11 months ago

From Coco Liliace to ~rjarry/aerc-devel

Hello,

The pattern `Mime-Version` only appears in the tests. I'm new to Go and
am wondering where and which module we're using to set this attribute.
I'd like to know so I can propose the upstream to change the casing to
`MIME-Version`, following the RFC1341 convention.

This is important because some email providers automatically change the
casing to the RFC1341 convention, which compromises the integrity of GPG
signatures since MIME-Version is signed with the rest of the email body.

Thank you,
Coco

[PATCH] testing/queercat: new aport 1 year, 11 months ago

From Coco Liliace to ~sircmpwn/alpine-aports

https://github.com/Elsa002/queercat
A version of lolcat with options for some lgbtq+ flags
---
 testing/queercat/APKBUILD | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 testing/queercat/APKBUILD

diff --git a/testing/queercat/APKBUILD b/testing/queercat/APKBUILD
new file mode 100644
index 00000000..f9cfbd0d
--- /dev/null
+++ b/testing/queercat/APKBUILD
@@ -0,0 +1,27 @@
# Contributor: Coco Liliace <chloe@liliace.dev>
[message trimmed]