Hi Chris, > Interestingly, I've just been able to reproduce it even with 0.73.99-1:
This makes sense. I was wondering how a patch that supposedly only touches a11y (how the contents are read out loud) could have an effect on the actual emulation behavior. Can you try under xterm or other non-VTE-based terminals? I suspect you'll see the same behavior there. It could be a bash issue, or a misconfigured prompt. In fact, I _think_ the culprit is that inside command substitution stuff, a.k.a.. $(...), nonprintable characters need to be enclosed within the raw bytes 0x01 and 0x02, rather than the two-character sequences \[ and \]. Not entirely sure, though. If you can't locate the problem, and if it's specific to VTE, then you should record the traffic using `script` and it should be manually, step-by-step verified what the terminal does for that, e.g. compared against xterm to see where it goes different. But I'm almost entirely certain that it'll be a bash issue rather than a VTE one. Nevertheless, the crash you encountered might be the same caused by the currently debated a11y patch. e.