Notepad++ v8.3 release
-
@microka said in Notepad++ v8.3 release:
I create txt files with different encoding (including ANSI, UTF-8, UTF-8-BOM, UTF-16 BE BOM, UTF-16 LE BOM), all files reproduce this problem.
I could not reproduce this problem using a fresh folder with just unpacked “npp.8.3.portable.7z” from https://notepad-plus-plus.org/downloads/v8.3/
Is it reproducible for you in the same situation?
If it’s reproducible, could you share your “session.xml” file?
If it’s not reproducible, could you try to identify what needs to be done to reproduce the problem? (Please note that the portable version does not use any additional plugin that might be previously installed for a non-portable version of Notepad++. In such case, the problem may be actually caused by some of plugins that were previously installed for a non-portable version. To test if it is so, you may rename the file “doLocalConf.xml” in your portable Notepad++ folder to make it non-portable). -
@vitalii-dovgan said in Notepad++ v8.3 release:
@microka said in Notepad++ v8.3 release:
I create txt files with different encoding (including ANSI, UTF-8, UTF-8-BOM, UTF-16 BE BOM, UTF-16 LE BOM), all files reproduce this problem.
I could not reproduce this problem using a fresh folder with just unpacked “npp.8.3.portable.7z” from https://notepad-plus-plus.org/downloads/v8.3/
Is it reproducible for you in the same situation?
If it’s reproducible, could you share your “session.xml” file?
If it’s not reproducible, could you try to identify what needs to be done to reproduce the problem? (Please note that the portable version does not use any additional plugin that might be previously installed for a non-portable version of Notepad++. In such case, the problem may be actually caused by some of plugins that were previously installed for a non-portable version. To test if it is so, you may rename the file “doLocalConf.xml” in your portable Notepad++ folder to make it non-portable).It’s weird, using npp.8.3.portable.x64.zip cannot reproduce this problem. Even i rename the file “doLocalConf.xml”, still not reproducible.
I have renamed my N++ subfolder “plugins” to “plugins.bak” and deleted all files under “C:\Users[username]\AppData\Roaming\Notepad++”, the non-portable version still have this problem.Now i figure out something. When i double-click a file to open it, this problem occur, but if i open a file using NPP’s menu “File -> Open” doesn’t have this problem.
-
It’s weird, using npp.8.3.portable.x64.zip cannot reproduce this problem. Even i rename the file “doLocalConf.xml”, still not reproducible.
To be clear, i am dragging a file to the portable NPP to test.
-
NppTaskList 2.3 plugin (the latest) causes Notepad++ 8.3 x64 to shut down on start, including when the only file open is a new blank.
All other plugins I use seem to be fine, it’s probably down to the plugin author to update it but I thought I would report it in case others are struggling to find why the application is closing. -
@yakumo-unr said in Notepad++ v8.3 release:
NppTaskList 2.3 plugin (the latest) causes Notepad++ 8.3 x64 to shut down on start, including when the only file open is a new blank.
All other plugins I use seem to be fine, it’s probably down to the plugin author to update it but I thought I would report it in case others are struggling to find why the application is closing.Thanks - and please open a ticket on the appropriate place for that plugin (which seems to be here) and reference https://community.notepad-plus-plus.org/topic/22471/recompile-your-x64-plugins-with-new-header
-
@michael-vincent
NppTaskList probably here: https://github.com/Megabyteceer/npp-task-list -
@microka
I am able to reproduce the problem now.As you have already stated, it is visible only in an installed N++, not in a portable one. I can trigger this behavior e.g. by right-clicking on a text file and choosing “Edit with Notepad++” from the popup menu.
The previous 8.2.1 installation does not show this positioning on 2nd char.
-
-
@xomx Thank you!
-
@xomx said in Notepad++ v8.3 release:
As you have already stated, it is visible only in an installed N++, not in a portable one.
It can be reproduced with a portable NPP by using the command line: “NPP Path” “File Name”.
-
auto-complete is broken in this release
-
@james-walker-hall said in Notepad++ v8.3 release:
auto-complete is broken in this release
It’s not. You just don’t read releases notes.
See here:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/11073#issuecomment-1020541332Cheers.
-
@michael-vincent ok well the new behaviour sucks
-
@james-walker-hall said in Notepad++ v8.3 release:
ok well the new behaviour sucks
Then change it back.
-
This post is deleted! -
Since version 8.2.1 and also in 8.3, when autocomplete pops up, pressing Enter no longer completes it, I get a newline instead.
Please fix this. -
Reading the links that @Michael-Vincent posted a few posts above will tell you what you need to do to configure it as you desire.
-
Per this post, you have won. Congratulations. The next release will go back to reserving two keys to perform the same action by default, and those of us who want only one key will have to change settings.
-
@donho
After update from 8.2.1. When I open N++ (new document or edit some file), after ~10 seconds editor shutdown. -
@marcin-sawiak said in Notepad++ v8.3 release:
@donho
After update from 8.2.1. When I open N++ (new document or edit some file), after ~10 seconds editor shutdown.Then you probably have one of the plugins mentioned previously. Try running with
-noPluginto confirm. (v8.3 has changed the interface on one of the commands that plugins can use to talk with Notepad++, and until that plugin is updated to the new interface, it will not work with Notepad++.)
