-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
bat (and less) output containing "^G" after clickable texts (ArchLinux-Alacritty) #3013
Comments
This reminds me a little of another problem with |
also, just to check - which version of |
|
It's actually quite inconsistent, it only happens with some files (and only with those that have more lines than my terminal emulator can show).. |
Would it be possible to provide a sample file where this happens? I'm not able to reproduce the issue on my setup. |
It was an error in my files, it has nothing to do with bat/less (I thought that was it because this didn't happen in other pagers). |
When I try to use
bat
orless
to display a file that contains clickable text (using the ANSI code \x1B]8), the characters "^G" are always displayed at the end of these texts, this only happens with the "links", the bold and italic texts are displayed correctly, I managed to solve this using the--raw-control-chars
flag ofless
but this brought another problem , in which some lines of the displayed file simply disappear, and when I scroll down and then up, these lines start to appear, but in place of others (it's difficult to explain, but it's like that)For the other ANSI formatting to work I needed to export one variable using
export LESSUTFCHARDEF=E000-F8FF:p,F0000-FFFFD:p,100000-10FFFD:p
so I imagine the problem is that something else is missing within this variable, but what exactly?more
can display everything correctly but I really like howbat
+less
does things and I wanted to be able to work around this problem and use it.To use this
less
flag inside thebat
I launch the command like this:echo "$FILE" | bat --pager="less -raw-control-chars" --plain
($FILE
=file contents)The text was updated successfully, but these errors were encountered: