broot: ANSI codes inserted into the prompt after starting broot (causing "No matching verb")
After starting br or broot in my terminal, I see the following ANSI codes inserted immediately:
It says: 11;rgb:2828/2a2a/3636
This happens regardless of whether I run the command in zsh, bash (with the default bash prompt), inside or outside tmux.
The only difference is that when I run it outside tmux, broot does not say “No matching verbs”, but it behaves as if the sequence was not there:
I am not sure what is causing this. I would appreciate any tips to debug this issue.
About this issue
- Original URL
- State: closed
- Created 4 months ago
- Reactions: 3
- Comments: 15 (4 by maintainers)
Commits related to this issue
- version 1.36.1 Fix #854 — committed to daniejstriata/broot by Canop 4 months ago
The fix has been released with version 1.36.1 @CarterLi @zeenix @Gelio
I just upgraded and the problem no longer exists for me on Kitty (both in and outside of tmux)
Thanks @Canop and @zeenix for delivering a quick fix 🚀
Same issue for iTerm in macOS
Nice! Thanks so much for testing.
That’s just the Terminal app being silly AFAICT. If you revert the commit to before my recent changes (
git checkout abfb5aae9e7539cb9cd3c8b3fcc98a7dfa5e6276) and run the example, you’ll still see those. I’d just say do what everyone does on Mac: stick to iTerm2. 😃No worries. I can verify that at least kitty worked fine before my recent changes. My own app (
gimoji) didn’t work correctly though when launched from a git hook. In any case, I think we’ve now a fix for all that is fixable. 😃I understand you wanted me to run
cargo run --example kittyfrom that repo.Here is the output in kitty in tmux:
Here is the output in kitty outside of tmux:
The extra codes in my prompt were inserted automatically. The screenshots contain the state right after the command finished
You are right, this problem does not occur on 1.32.0
https://github.com/Canop/broot/assets/889383/e52dfa21-c868-4f8a-83ad-029f273e9b9a
For reference, I am using kitty 0.32.2