Notepad++ v8.1.2 Released
-
@donho
I experienced the same issue reported by @David-Sperduto, however I’m using Windows 10 Pro.
I’m using 8.1 for now (same issue in 8.1.1). Fingers crossed the fix @mere-human linked will address the issue in both Vista and Win 10, but thought I should flag this issue as being present in a more recent OS than Vista. -
This post is deleted! -
@Justin-Westacott said in Notepad++ v8.1.2 Released:
Fingers crossed the fix @mere-human linked will address the issue in both Vista and Win 10
The @mere-human fix is in v8.1.3-ReleaseCandidate, so you can try it for yourself… and if it doesn’t fix it for you, reply in the RC thread with your ?-menu Debug Info
-
@David-Sperduto said in Notepad++ v8.1.2 Released:
Save As
Hi. I have the identical issue with Win 10 Pro x64.
It is annoying and recurring. Most of new files have this issue, namely no way to change the file name before saving it through “Save As”. -
With dark mode enabled, when I print, the line numbers are in black as expected but the actual text is light-grey and almost unreadable. When I switch dark mode off everything prints in black as expected. This is from Windows 10 to a HP M479dw.
-
The issue can be reproduced:
- create a new file
- work on it
- Save as… then:
if you don’t change the folder from the current one, you are able to modify the file name
but as soon as you change the folder, the file name cannot be edited anymore.
-
@Bojan-R said in Notepad++ v8.1.2 Released:
The issue can be reproduced:
The issue, cannot be reproduced by that sequence by everybody – many users (like me) have never seen that problem, despite saving files on an hourly basis for weeks or months with versions like 8.1.2 that show the issue.
That said, with older Windows, the developers were able to reproduce the problem more reliably, and fix it. As I have said many times, that fix is in the next release of Notepad++. Telling us “I also have the problem in v8.1.2” won’t help. What would help is if you read my post from 4 days ago – literally, the post just before yours – and followed those instructions: the most recent v8.1.3 release candidate 3 is found here.
-
Please let us know if the issue you encounter has been fixed in v8.1.3
-
@donho
Yes, I confirm, the issue has been fixed in v8.1.3 RC. Thanks a lot !Another feedback concerning this Save As issue in v8.1.2: a colleague of mine noticed that it doesn’t happen if you create a new file then use just “Save” instead of “Save as” and change the file name. It can be used as workaround before updating to v8.1.2. But you probably found it out, as you fixed the issue. Thanks again !
-
@Bojan-R
I meant before updating to v8.1.3 -
P PeterJones locked this topic on
