> I can repro, alacritty + tmux. That first emoji (🤦‍♂️)) seems to be really
> breaking tmux + alacritty and I am not sure why yet.

I got another email with a different set of emojis that breaks drawing
the similar way. The raw subject header is:

Subject: =?UTF-8?B?UlFIViA4REwgRTM5IPCfkanwn4+74oCN4p2k77iP4oCN8J+Si+KAjfCfkanwn4+9IENvbQ==?=
        =?UTF-8?B?cGxldGVkPyBTdGF0dXMgb2YgUGxhbiBFeHRlbnNpb24gSW5hZGVxdQ==?=

Hope this helps.

-- Vitaly

> > Here's the subject from the message headers "as is":
> >
> > Subject: =?UTF-8?B?8J+kpvCfj7vigI3imYLvuI8g8J+NuiByZWNlaXB0IGNvbXBsZXRlZCB2ZXJpZmllZCBwcg==?=
> >         =?UTF-8?B?b2Nlc3NlZCBjb25maXJtZWQgc3VjY2Vzc2Z1bGx5IDAuIE9NWVRG?=
>
> Is this the verbatim subject, as displayed in aerc? If not - could you send the
> decoded version?

That's what aerc's "show headers" option shows - the source of the
subject. I can't copy that line with emojis that is displayed by aerc
with the built-in tmux function - it is not copied properly.

Here's the minimal message that reproduces the problem:

Use a dedicated filename function for getting a name of the attached
file instad of analyzing its mime type. Some attachments have file name
in `Content-Disposition` rather than `Content-Type`, the new method
handles both cases.

Signed-off-by: Vitaly Ovchinnikov <v@ovch.ru>
---
 commands/msg/forward.go | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/commands/msg/forward.go b/commands/msg/forward.go
index cb2cab35..7c491a06 100644
--- a/commands/msg/forward.go
+++ b/commands/msg/forward.go
[message trimmed]

Hello Tim,

I get aerc crashing when trying to pipe the whole message to nvim. This
mostly happens to emails with multiple (mostly PDF) attachments, but not
all of them.

Here's the crash report:

======================================================================
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x11b pc=0x10435ed5c]

goroutine 407 [running]:
git.sr.ht/~rockorager/vaxis.(*Vaxis).CanReportBackgroundColor(...)

Hello Tim,

> > Does it mean we no longer need VAXIS_FORCE_UNICODE=1?
> That is correct.

I got another (spam) email with a subject that ruins TUI pretty much the
same way as the previous one and again only in TMUX (tested with
alacritty on mac).

Here's the subject from the message headers "as is":

Subject: =?UTF-8?B?8J+kpvCfj7vigI3imYLvuI8g8J+NuiByZWNlaXB0IGNvbXBsZXRlZCB2ZXJpZmllZCBwcg==?=
        =?UTF-8?B?b2Nlc3NlZCBjb25maXJtZWQgc3VjY2Vzc2Z1bGx5IDAuIE9NWVRG?=

> - Fix dropping of events during large pastes

I can confirm the pasting works after this update. Thank you!

-- Vitaly

> - Add quirk for tmux 3.4 to turn on unicode width measurements

Does it mean we no longer need VAXIS_FORCE_UNICODE=1?


What about the problem with pasting of large blocks of text? Any ideas
when this can be fixed?

-- Vitaly

> > I don't see any difference to the built-in image preview. It is of about
> > the same width with and without the patch. Even if I put a specific
> > number instead of the terminal width, like 200 - the picture don't
> > change.
>
> Do you have an image I can test with?

Actually any image works. The wider ones are better as they benefit more
from having more columns. I'm using a built-in vaxis/aerc preview with
less as a pager.

-- Vitaly

> Previously filters received a COLUMNS value of 80 no matter the width
> of the terminal.

I don't see any difference to the built-in image preview. It is of about
the same width with and without the patch. Even if I put a specific
number instead of the terminal width, like 200 - the picture don't
change.

-- Vitaly

Hi Tim,

> Could you try recreating this in all of those terminals but with
> `VAXIS_FORCE_UNICODE=1` set? I was able to reproduce in all terminals I have
> installed + tmux, and when setting this it goes away.

I can confirm this fixes the glitch for me (tmux + alacritty at mac).

I used to have a similar problem with other emojis in email subjects,
but it never was that stable to report. Hope it was the same stuff.

Meanwhile, is is OK to use that environment variable as a daily driver?
Any possible issues with it? Extra logging? Slowdowns? Anything?