You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you used the debugging guide to try to resolve the issue?
Have you checked our FAQs to make sure your question isn't answered there?
Have you checked to make sure your issue does not already exist?
Have you checked you are on the latest release of Pulsar?
What happened?
When looking at a git diff visualization basically (in unstaged or staged changes), if the line number is too big, then the padding has no effect. So there ends up being no gap between the numbers.
Pulsar version
1.102.2023021606
Which OS does this happen on?
🪟 Windows
OS details
Microsoft Windows 10 Pro, 10.0.19045 Build 19045
Which CPU architecture are you running this on?
64-bit(x86_64)
What steps are needed to reproduce this?
This occurs when viewing changes about a git repository, and the file you change must have a lot of lines.
Based on this screenshot, the lines are right-aligned. So idk how long it actually needs to be. My bug originally occured with 6 digits, but maybe fewer is ok.
I was editing the file set.mm from https://github.com/metamath/set.mm which you can git clone, which easily satisfies the above requirements (700k+ lines and is git repo).
Change whatever long file you choose, and save.
Hover your mouse around the right center portion of the window. A right arrow should pop-up. Click on it to open the git tab.
On the .git tab, click on the corresponding file. It doesn't matter if it's in "unstaged changes" or "staged changes". You might have to change the branch or repo or something in the dropdown.
Observe visual bug:
Additional Information:
I'm technically not on the latest rolling release of pulsar
Astonishingly, I can't really find this issue on the archi atom repo. I guess no one edits hundred-thousand-line files.
The text was updated successfully, but these errors were encountered:
Thanks in advance for your bug report!
What happened?
When looking at a
git diff
visualization basically (in unstaged or staged changes), if the line number is too big, then the padding has no effect. So there ends up being no gap between the numbers.Pulsar version
1.102.2023021606
Which OS does this happen on?
🪟 Windows
OS details
Microsoft Windows 10 Pro, 10.0.19045 Build 19045
Which CPU architecture are you running this on?
64-bit(x86_64)
What steps are needed to reproduce this?
set.mm
fromhttps://github.com/metamath/set.mm
which you cangit clone
, which easily satisfies the above requirements (700k+ lines and is git repo).Additional Information:
I'm technically not on the latest rolling release of pulsar
Astonishingly, I can't really find this issue on the archi atom repo. I guess no one edits hundred-thousand-line files.
The text was updated successfully, but these errors were encountered: