Replies: 9 comments
-
If I save your diff from #1309 and then do
it looks normal. It looks like you might be trying to use
delta's pager should be |
Beta Was this translation helpful? Give feedback.
-
So, I double-checked. The PAGER variable was not set at all. It works on my local computer, too. But not on the GitHub Actions logs. |
Beta Was this translation helpful? Give feedback.
-
Hm, my guess is the automatic terminal width detection. If you felt like more investigations (!) you could look into things like |
Beta Was this translation helpful? Give feedback.
-
By default, the environment of a GitHub Actions step is almost completely empty. This means also COLUMNS is missing. Tput output: |
Beta Was this translation helpful? Give feedback.
-
If you check the screenshot, you will see that it works for lines with no changes and lines that were completely added/removed. |
Beta Was this translation helpful? Give feedback.
-
Why would it need to do that in the fixed "--width 150" case? |
Beta Was this translation helpful? Give feedback.
-
I just realized not only side-by-side is affected! It does not print any leading whitespaces in added lines. Note: I had to switch to |
Beta Was this translation helpful? Give feedback.
-
Setting:
as expected, does not help either. It shows correctly with |
Beta Was this translation helpful? Give feedback.
-
Hm, maybe a bug in ANSI sequence handling by the terminal emulator being used by the Github Actions log UI? If you can't reproduce this in a standard terminal emulator then it seems like there's no evidence of a delta bug here, right? |
Beta Was this translation helpful? Give feedback.
-
see #1309 for the diff
https://github.com/OpenMS/pyopenms-docs/actions/runs/4234240051/jobs/7356257942#step:7:152
Am I missing a setting?
Beta Was this translation helpful? Give feedback.
All reactions