Hey there. It's a bit weird, I can *no* longer reproduce it.
I have now (and everything else except libheif* at the current versions of unstable): libvte-2.91-0:amd64 0.74.0-2 gnome-terminal 3.50.0-1 If I use my original PS1 and the command I've mentioned before, go back with the Up key and then remove the "2"... everything seems fine. @Samuel, could you please also try whether you can still reproduce it? If not, I'd say we might close the issue. @Egmont, sorry, I hadn't seen you reply to the bug (Deb BTS is... well...). I now tried with xterm (where the issue doesn't appear, but as I've said, I cannot even reproduce it with gnome-terminal anymore. > 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. That's interesting... why do you think so? The command substitution should also be bash, and I'd have thus expected \[ and \] inside it have therefore the same representation as outside and should thus be identical? Cheers, Chris.