Wrong expansions when using Alacritty on Linux

[YakBarber]

OS: Ubuntu 20.04
Version: snap package, 0.7.3

When matching in my terminal (alacritty, with both zsh and bash), once in a while the replace text output comes in the wrong order. Examples I've seen:

:espanso -> Hi t!here
:espanso -> !eHi ther
:espanso -> Hi thereespanso detectHi there there (Note, espanso detect was the most recent command, so there was a scroll up in my shell history)

I am not able to reproduce the issue outside of the terminal (eg, in this text box in my browser it works right 100%).

[federico-terzi]

Hey @YakBarber,

I'm sorry you experienced this problem!
I've seen this happening when multiple processes are running at the same time. Could you please try running killall espanso && espanso start and see if that helps?

Keep in mind that 2 processes are expected in version 0.7.3, so don't worry if you see two processes running :)
(for future readers, the new v2 uses 3 processes by default)

Edit: I've just realised that this is unlikely to be the cause if it's happening only in the terminal, perhaps there is some interference with alacritty. Does that happen also with other terminals?

Cheers :)

[YakBarber]

I tried the same test in another terminal (Kitty) and got a different behavior. In Kitty it reliably acts as though the "shift key" wasn't added, meaning the output is: hi there1

EDIT: I also tried your struck comment about processes, and as you expected the problem persists.

[federico-terzi]

@YakBarber Interesting, thank you for trying! I'll investigate :)

[YakBarber]

No Problem. I'm familiar with Rust and its toolchain, so if my testing anything deeper would be helpful, just let me know. If I can find some time to go spelunking I will, but it's unlikely.

[federico-terzi]

Sounds good! Although It's likely we'll have to fiddle with Espanso parameters rather than Rust code :)

The way we'll probably handle it is by creating a specific patch for it and bundle it into Espanso itself

[federico-terzi]

Hey @YakBarber,

I was able to reproduce the issue, and a fix will be included in the next alpha version (v2.0.4-alpha).
In the meantime, you should be able to get it working on Alacritty by adding a file $CONFIG/user/alacritty.yml with this content:

filter_class: "Alacritty"

backend: Clipboard

Cheers :)