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,

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

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.

---
 README.md    |  6 +++---
 build.zig    | 25 +++++++++++++++----------
 src/args.zig |  6 +++---
 src/main.zig | 14 +++++++-------
 4 files changed, 28 insertions(+), 23 deletions(-)

diff --git a/README.md b/README.md
index 8d0b6da..407aee5 100644
--- a/README.md
+++ b/README.md
@@ -261,7 +261,7 @@ suggested as completion.
 # Building it
 
[message trimmed]

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

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

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:
>
> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/44920#note_295168

Just wanted to update that a new release is no longer necessary, as I

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

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:

https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/44920#note_295168

Coco

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