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
i was running a dev build because i was testing the new changes i requested when i encountered the following issue:
this does not happen in the current master build. a very quick glance at the recent commits makes me think commit b84b793 might have broken this view. I haven't had time to go into detail. i probably was way to quick and that commit might totally not be the cause
Reporting this issue so this can be fixed before a new release happens, if this is considered not an issue as it is only in dev, feel free to close it immediately.
I will try to, at first glance i did not see a pattern as it was only in about half of the files. I'll use the dev build again today and see if i can get something consistent.
Hi @mithom, your first idea was right: My commit b84b79 (#1996) introduced the regression bug you've seen. I've fixed it in #2015. You may have seen this bug only sometimes, since it is only triggered for files with CR/LF as newlines (I suspect you're using Windows). With LF as newline this bug is not triggered (even on Windows).
Activity
love-linger commentedon Dec 23, 2025
Can you find a way to stably reproduce it?
mithom commentedon Dec 23, 2025
I will try to, at first glance i did not see a pattern as it was only in about half of the files. I'll use the dev build again today and see if i can get something consistent.
fix: extra empty lines in diff (Windows)
sina-hide commentedon Dec 29, 2025
Hi @mithom, your first idea was right: My commit b84b79 (#1996) introduced the regression bug you've seen. I've fixed it in #2015. You may have seen this bug only sometimes, since it is only triggered for files with CR/LF as newlines (I suspect you're using Windows). With LF as newline this bug is not triggered (even on Windows).
fix: extra empty lines in diff (Windows) (#2015)