Closed dfs- closed 4 years ago
f705a9674b2ad75702f2c1e8c989558d45a7d243
Unfortunately, the issue still persists, even with the new build.
Please check the version number in the upper left corner to make sure that you have updated the executable.
Hi lhmouse, the top left corner states "v4.9-4-g5929ad7c". Is this the correct version?
The lastest build is v4.9-168-gccf508e2
.
Thanks for bearing with me. The issue now doesn't appear anymore, but the top status bar still shows another GIT short hash: v4.9-168-gae369e71
The 168
in the version string denotes it was 168 commits ahead of the v4.9 tag, so as long as this number is correct, it shouldn't matter. Probably it was caused by another rebase operation.
Exiting nano will print the above text to console. Older versions, tested with v3.1-68-ga86a9b1a will not do so.
You can see a screenshot here: https://imgur.com/a/UWVc7XX
System specs: Windows 10 x64 Version 1909 (Build 18363.778)