Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ANSI Escape Sequences Shown in Git Bash #246

Open
adamrodger opened this issue Jul 7, 2020 · 3 comments
Open

ANSI Escape Sequences Shown in Git Bash #246

adamrodger opened this issue Jul 7, 2020 · 3 comments
Labels
windows Windows specific problem

Comments

@adamrodger
Copy link

Describe the bug
ANSI escape sequences shown in Windows Terminal using Git Bash

To Reproduce
Try to run broot within Windows Terminal with Git Bash as the shell

Expected behavior
The output has proper colours

Screenshots
If applicable, add screenshots to help explain your problem.
image

Configuration (please complete the following information):

  • OS: Windows
  • Version Windows 10 x64 1904, broot 0.18.5
  • Installed via scoop install broot
@Canop
Copy link
Owner

Canop commented Jul 7, 2020

It has already been reported that broot (like other crossterm based applications) isn't compatible with git bash. I'm sorry but I can't work on that. Other devs who want to tackle that problem are invited to do so (and maybe talk with Timon on https://discord.com/channels/560857607196377088/560857607196377090)

Thanks for the report, though, and please don't delete it, it's a clear one which may help newcomers.

@Canop Canop added the windows Windows specific problem label Jul 7, 2020
@adamrodger
Copy link
Author

Yep, no problem. I saw the other issue, but just wanted to raise this one specifically because it's about the ANSI escapes rather than generally being incompatible.

For me, once I've fixed my ~/.bashrc to source ~/AppData/Roaming/dystroy/broot/config/launcher/bash/br then I can get the app to run, but it's unusable because it's just a screen full of ANSI escape sequences.

If the escape sequences can be fixed then I think it would work fine in Git Bash for me. You can make out that it has actually worked within all those escape sequences and formatting problems:

image

@3tilley
Copy link
Contributor

3tilley commented Oct 26, 2023

Is this still an issue, or has it been fixed with the Windows Terminal improvements?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
windows Windows specific problem
3 participants