Notepad++ v8.2.1 Release
-
This post is deleted! -
@donho I have tried again and it works now!
-
This post is deleted! -
This post is deleted! -
I’m sorry you are having difficulty with that. I am not sure whether your second post was meant to say, “nevermind, I got it working” (because it sure looks like you have it working), or whether you were showing a working version from some previous Notepad++ version. If it’s the latter, you will have to be more specific.
I just took a known-working UDL+autoCompletion custom pair of config files from v8.2, and copied those files into a portable v8.2.1 (and a portable v8.2.2-RC) instance. When I first tried to replicate, I wasn’t seeing any auto-completion (or specifically, Function Completion with Ctrl+Spacebar), and I thought I had replicated your problem in both. But I had closed Notepad++, and so when I went to get screenshots to add as evidence, they both started working the same as they did in v8.2 – so my simple UDL with an autoCompletion file with three keywords correctly shows me those three keywords when I Ctrl+Spacebar.
If you are still having difficulty with autoCompletion, you will need to give more details.
-
I don’t wish to discourage anyone but considering the number of issues being fixed or retriggered, should I be using latest versions or just stay on old version like before the x64 transition?
-
@winswgmbh said in Notepad++ v8.2.1 Release:
considering the number of issues being fixed or retriggered
What is this quantity you are talking about?
I am using 8.2.1 for days now; no apparent problems.
just stay on old version like before the x64 transition?
That is something you have to answer for yourself.
-
@alan-kilborn Ok. Quantity is the issues people report here since v 6.9.5. I am following up the community hence the question. I neither mean the things are not fixed(yes they are fixed) nor intend to disrespect the developer if that is what is concluded from my comment however most of the times I prefer “stability” over trying new features and updates. I am using this program for basic notepad tasks and code reading, nothing too complex and I prefer it as my default one always.
-
@winswgmbh
if you use Notepad++ as a replacement for Notepad without doing fancy things, you can always update.
I have never had any issues, since I too use Notepad++ in a similar way. -
I had the same experience as Stefan, until I decided to involve myself in creating a UDL for my community’s language. I even had a screwed up install with my x64 being installed in the x32 directory on windows, etc, and the program always worked for the simple things I did, bar none. So if you don’t want the latest and greatest, don’t upgrade, but don’t be afraid to upgrade for your modest needs. Things like the recent testing of files 2GB in size will not affect your usage and if it does, the testers will most likely find it before it becomes a release. Other than the broken update program a few version ago, I’ve not had one problem with the NPP that I didn’t create myself with my language creation. :)
Lee
-
@Stefan-Pendl and @Lycan-Thrope Thank you so much for clearing my doubts and hesitation to upgrade.
-
@lycan-thrope
I do use some UDLs for data files of a software I am maintaining and also never had any issues.
It is the same for all kinds of software, an update or upgrade always has the risk to break something, this is why software vendors offer test releases.
If you like to make sure your use-case works, use the portable release for testing it. -
It seems v8.2.1 is quite stable.
The auto-updater has been triggered for this release. -
Hi @peterjones
During the auto complete, the suggested words are listed in drop down. However, mouse click or keyboard navigation and selection using Enter key is not working. So, I had to downgrade to v8.2 to keep that auto-complete and keyboard navigation working. -
election using Enter key is not working.
Per the v8.2.1 release notes, above: "3. Add an option for inserting auto-completion selection to fix hitting twice ENTER to go to next line. "
Did you try using that option, or using the alternate TAB instead of ENTER to select it? Because in my experiments earlier, I didn’t just have the pulldown, it worked 100% for me.
-
P PeterJones referenced this topic on
-
It shouldn’t change the default value of ENTER to TAB for auto-complete. I was very confused when it stopped working using the enter key. Only after going to the changelogs and then to options to switch it back from tab to enter it’s working fine again.
-
D donho unpinned this topic on
-
@dobatymo said in Notepad++ v8.2.1 Release:
It shouldn’t change the default value of ENTER to TAB for auto-complete.
Agreed. In general, adding options for alternative workflows is great, but changing default behaviours is a poor implementation strategy - the changes are very frustrating for long-time users, and often come across as regressions at first glance.
As a recent (non-NP++) example: Microsoft revamped the context menu in Windows 11 in an attempt to make certain selections easier to find. In doing so, they appeared to eliminate many of the commonly-used options, but what they actually did was just move them to a sub-menu. For many (most?) long-time Windows users, this was a highly disruptive change - one that was made worse by the method of reverting back to the old style.
In general, the only scenario where it makes sense to have new options and such toggled/implemented by default is if the user is new to the product - such users have no workflows ingrained into them yet, so there isn’t anything to disrupt. So, installations from full installers are likely safe for implementing the new workflows by default, but upgrades should never change current workflows.
That being said, some users (like myself) do fresh installations on new machines surprisingly often (in my case, on VMs used for testing). I already have a system in place for “importing” my preferred configurations post-installation (in fact, the configuration files are updated every time my VMs are powered up), but during the installation process, it would be nice to be prompted for the location of the various configuration files that ultimately get copied over.
-
@mathlete2 said in Notepad++ v8.2.1 Release:
It shouldn’t change the default value of ENTER to TAB for auto-complete.
Agreed. In general, adding options for alternative workflows is great, but changing default behaviours…
I believe the “default behavior” described was considered a bug, so changing it was a bug fix. Keeping the old behavior was nicely made into an option setting with the fix, to give those familiar with the feature a path to return to what they’ve gotten used to.
-
@alan-kilborn said in Notepad++ v8.2.1 Release:
I believe the “default behavior” described was considered a bug
Perhaps we weren’t clear about what “default behaviour” we were referring to. In this case, we were referring to the result of “pressing Enter while the auto-complete menu is open”:
In all previous releases, the default behaviour was to insert whichever selection was highlighted. With the update, the default behaviour completely ignores the menu. Unless the user is aware of the new options (and their default settings), this new default behaviour comes across as a (significant) regression.
Out of curiosity, I looked at the Auto-completion documentation, and it looks like it’s inaccurate:
You accept the suggestion by typing the Enter or Tab key, and the word is completed within your buffer as if you’d typed it all out.
This suggests that TAB and ENTER should both be checked by default, but that is not the case after an update; only TAB is checked in this scenario, which is why “Enter” wasn’t working for us at first. Perhaps there’s a bug in the update process?
-
@mathlete2 said in Notepad++ v8.2.1 Release:
Out of curiosity, I looked at the Auto-completion documentation, and it looks like it’s inaccurate:
It was accurate until that feature was changed. Now it’s being updated. The documentation sometimes lags a few weeks behind new releases, because that gives me a chance to go through the release notes and make sure everything relevant has been updated (because I am the primary documentation maintainer, but not one of the developers, so I don’t get foreknowledge of new features).
Also, when there are a lot of back-to-back NPP releases (like recently), the usermanual sometimes only gets released after a few releases, rather than after every release. It depends on how fast I am, and how often the website owner feels like doing a new release, or I ping him.
If you’re ever curious what changes have been implemented in the docs since the last release of the website, go to the github project for npp-user-manual.org. There, you can see that auto-completion page has been updated to mention the behavior change in v8.2.1.
After checking the github, if you ever feel that there’s a deficiency in the user manual that hasn’t been addressed, feel free to create an issue and submit a PR.
Perhaps there’s a bug in the update process?
No, the two biggest problems are that I’m not prescient, and I am not paid enough by the Community to make maintaining the user manual my full-time job.
