[hrez]

I didn't have as positive experience. Granted I commented on a closed issue. In any case it was closed as "won't do" and my comment was ignored. I didn't feel like opening a new issue for the same that was already dismissed. https://github.com/wez/wezterm/issues/4706

[eredengrin]

The way you phrase that makes it sound like you had a negative experience, was that your intention? For all we know he didn't even see it, there's thousands of issues and PRs and it's not like this is his full time job, so missing a message sounds like a pretty expected and neutral interaction to me. There's a reason they used the word "shockingly" to describe his response time, it's because it's amazing that Wez can respond to even a fraction of all the messages as quickly as he does.

Also in case you wanted to bump up the priority of that bug, he does have github sponsors enabled.

[hrez]

The showstopping bug (or misfeature?) reported by others was brushed off, and my comment was ignored. It didn't seem like the path forward would be a pleasant one, so I've uninstalled Wez and gone back to a terminal that works for me. So yes, you could say it was a negative experience. I gave Wez a try as my daily driver, but it just didn’t pan out despite my efforts.

[naikrovek]

Yeah Wez is limited by tmux behavior. If tmux breaks up one line into many, wezterm can’t undo that.

Wes is right about wezterm domains though. The native domains feature and pane support I think will meet the needs of most.

[hrez]

It's the same with no tmux. And it's fine with other terminals. See my comment in the issue.