Notepad++ v8.3 release
-
@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
-noPlugin
to 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++.) -
Hope this is the right forum for this, but I notice since the last update the auto-complete function is no longer working on Enter. Previously, if I typed in a function (language == .js) and that function was already in the file I was writing, it would show me that function and I could hit Enter and it would complete the line. Now, when I hit enter, I get a carriage return. Really inconvenient. Is there a new setting required to get the auto-complete on Enter? Thanks.
-
@nickie-albert said in Notepad++ v8.3 release:
Is there a new setting required to get the auto-complete on Enter?
Yes, please examine Settings => Preferences => Auto-Completion. It’s a pretty obvious checkbox on that setting page.
Cheers.
-
@michael-vincent Perfect, thanks! It was set to complete on Tab, but not Enter.
-
@nickie-albert said in Notepad++ v8.3 release:
Perfect, thanks! It was set to complete on Tab, but not Enter.
The next update will enable ‘ENTER’ by default, it was considered a bug so the functionality to manually enable was added and by default removed. I personally prefer the new way. It has taken some getting used to, but I vastly prefer using only ‘TAB’ to autocomplete in Notepad++ the same as I do on the command line in PowerShell, in Bash, etc.
Cheers.
-
@michael-vincent said in Notepad++ v8.3 release:
next update will enable ‘ENTER’ by default,
To be more precise, it will enable both
Enter
andTab
by default… but only if your config.xml has not already made a setting forinsertSelectedItemUseENTER
insertSelectedItemUseTAB
.If you have set those two entries the way you want them in Notepad++ in v8.2.1-v8.3, but then upgrade, your settings will remain the same without being changed. If you have upgraded to v8.3, and the 8.3-default got written to config.xml, and then you immediately upgrade to a new version (8.4 or whatever it’s called), it will keep the default state from 8.3, and not overwrite it with the default state from 8.4. This is intentional, as the “defaults” only get applied on new installations, when a specific setting is missing from the existing config.xml (for example, an upgrade from v8.0 to v8.4 or whatever it’s called), or when config.xml is missing/deleted and needs to be regenerated from defaults.