On Tue Oct 29, 2024 at 10:51 PM CET, Jason Cox wrote:
> On Tue Oct 29, 2024 at 1:24 PM EDT, prowess-alarm-much@duck.com wrote:
>> OK, the issue remains with the latest version, I'm not sure if it is
>> allowed to post here screenshots as imgur links
>
> Yep, you can post screenshot links.

Note: normally I'm using tmux in alacritty in WSL2 (Win11... ofc)

I will do so, here are a couple screenshots. Note: blockiness due to
privacy. The shots below serve to illustrate graphical issues and errors
trying displaying message header info in the main aerc window (msglist).

1- Possible threaded mode view issue → https://imgur.com/a/hqWdBMP

2- Whether using alacritty 0.14 or Windows Terminal (both Win11), aerc
will be B&W if launched straight from the linux prompt, but will render
color when launched from tmux. I've checked $TERM and $COLORTERM and
both are set to xterm-256color and truecolor in aerc.conf, .bashrc, and
.tmux.conf. I made a small video to illustrate this, but it is too big.

3- Glitches in the msglist when scrolling past a problematic message,
which I hope the following screenshots can show the glitches:
→ three screenshots here → https://imgur.com/a/bYk1mnh

>
>> I get an error with the :echo command, as per log:
>> ERROR 2024/10/29 18:20:29.699919 status.go:133: Unknown command echo
>
> The :echo command may only be in the latest master, not in v0.18.2.

I'm now running the latest compiled version, and can confirm that indeed
:echo works. I'm thinking how to pass color coded messages, as well as
make those messages ephemeral. I'm familiar with terminal color codes in
escape form like: Red: \033[31m, Green: \033[32m, Yellow: \033[33m, what
is the main idea behind the :echo command so I can adjust my
expectations accordingly?

thx!

On Thu Oct 31, 2024 at 17:35,  <prowess-alarm-much@duck.com> wrote:
> On Tue Oct 29, 2024 at 10:51 PM CET, Jason Cox wrote:
>> On Tue Oct 29, 2024 at 1:24 PM EDT, prowess-alarm-much@duck.com wrote:
>>> OK, the issue remains with the latest version, I'm not sure if it is
>>> allowed to post here screenshots as imgur links
>>
>> Yep, you can post screenshot links.
>
> Note: normally I'm using tmux in alacritty in WSL2 (Win11... ofc)
>
> I will do so, here are a couple screenshots. Note: blockiness due to
> privacy. The shots below serve to illustrate graphical issues and errors
> trying displaying message header info in the main aerc window (msglist).
>
> 1- Possible threaded mode view issue → https://imgur.com/a/hqWdBMP
>
> 2- Whether using alacritty 0.14 or Windows Terminal (both Win11), aerc
> will be B&W if launched straight from the linux prompt, but will render
> color when launched from tmux. I've checked $TERM and $COLORTERM and
> both are set to xterm-256color and truecolor in aerc.conf, .bashrc, and
> .tmux.conf. I made a small video to illustrate this, but it is too big.
>
> 3- Glitches in the msglist when scrolling past a problematic message,
> which I hope the following screenshots can show the glitches:
> → three screenshots here → https://imgur.com/a/bYk1mnh

Well, you are a victim of conpty. WSL is great, considering it's Windows, but
still :)

You need to experiment setting these:

    export VAXIS_FORCE_LEGACY_SGR=1
    export VAXIS_FORCE_UNICODE=1

I have some WSL specific settings in my zshrc and these are there:

https://github.com/ferdinandyb/dotfiles/blob/f96e0ca94b087c18a3bed1859ba1bfe7b92138b8/.zshrc#L153

Although I only use contour and wezterm on Windows, so you might have other
issues with alacritty.

Best,
Bence