Inconsistent terminal behaviour on windows

[IceSentry]

So I'm having a few issues depending on which terminal I use to run bacon.

In vscode scrolling and copying works fine.

In windows terminal with powershell I can scroll but can't copy any text while bacon is running. I can copy text without issues when it's not running.

In alacritty, I can copy text, but can't scroll while bacon is running. Scrolling works when bacon is not running.

I'm not sure if the issue is with bacon not handling things correctly, or one of those terminal doing something wrong.

[Canop]

You mean you can't copy text from bacon ? Or are copies outside of bacon also impacted ?

[IceSentry]

When I tried copying the file path + line number using my mouse I was unable to highlight any of the text inside the bacon output. And since I can't select the text I can't copy it. I wanted to copy the path/line number to go to an error in my editor but was unable to because of that. I'd be happy if there was a built in way to just copy it without my mouse but I didn't se anything about that in the docs.

Here's a video showing what I mean;

bacon_copy0001-1255.mp4

You can't see my mouse but I was trying to highlight any part of the text like I did before starting bacon and nothing was highlighted. As you can see, it does work as expected in alacritty.

[Canop]

Thanks, that's clear now.

As I don't have a Windows computer, I rely on other devs to help me for the Windows version.

[IceSentry]

If you can point me towards the area of the code that you think could be causing this I would be happy to investigate further. I'm just not sure where to start.

[Canop]

You might start with removing the mouse capture which was specifically added for Windows: ead2e05

Then look at crossterm related things.