Darren Schroeder

let's close this if the problem doesn't exist any longer. thanks!

I'm not sure how to reproduce this. Do I need to change my right prompt to something special?

Thanks for the information. 1. I'm not sure it really matters but the default newline sequence in windows is `\r\n` instead of `\n\r`. 2. I'm not really clear why one...

I only notice this on the Windows version of WezTerm. The Mac version works great. Does this still happen with shell_integration set to false in the nushell config.nu?

It's sad that WezTerm behaves this way to our ansi escape sequences. I have no idea why it repeats the prompt with every character typed. It's not like we're sending...

@wez Thanks a bunch for chiming in and giving us your perspective!! > Earlier comments indicate that this isn't a wezterm issue and that it manifests in other windows terminals....

@wez Here's the Windows one [wezterm-recording-hX0ZFK.cast.txt](https://github.com/nushell/nushell/files/9444548/wezterm-recording-hX0ZFK.cast.txt) Here's one from my m1 MacBookPro [wezterm-recording-paeqle.cast.txt](https://github.com/nushell/nushell/files/9444559/wezterm-recording-paeqle.cast.txt)

@wez That matches with what we're seeing. If people turn off shell_integration in nushell this behavior doesn't show up in WezTerm. However, if we remove `OSC 133` and friends in...

Tests would be awesome for this. We've struggled with the implementation of this feature so much.

I'm thinking you're going to have to add flags to your custom command signature, like: ``` > def test [name, ...args, --verbose(-v)] { echo $"name=($name) args=($args) verbose=($verbose)" } > test...