Daniel Egger

> semver isn't a thing in the Python ecosystem like it is in Rust. And also people do break things accidentally. Fair. But your assertion was that this is also...

Thanks for the PR. This looks like a great step into the right direction as it is similar to a lot of other projects which have taken the gettext route....

> after staring `nvim --clean`, try clearing the default TermResponse handler: > > ``` > :au! nvim.tty > ``` > > does that fix it? Nope, problem persists.

Doesn't work either. BTW: I can see that some processing is happening to the terminal tab when switching away.

> I can only replicate this when iTerm2 is full-screened. When switching back to iTerm2, the count `2844` appears in the status line, which is then applied to the following...

I can confirm that I can't reproduce on iTerm2 nightly. Still might be interesting to know what changed between nvim 0.10 and 0.11 that triggered this and maybe come up...

> Neovim is actively querying more terminal capabilites in 0.11 to enable more features. If iTerm doesn't handle this specification correctly, then issues are to be expected (and need to...

BTW: This has some other "interesting effects", too. If you try to exit nvim after a switch, it will go on a looong CPU revving detour chasing its own tail......

iTerm2 3.5.12 is out, fixing at least the original problem, so I'm happy considering my problem addressed and this issue closed.

`cargo-binutils` only provides a nice frontend to find and call the `llvm-tools` binutils which are installed as a separate component to the rust compiler. It's (pretty much, unless the some...