Notepad++ release 8.9.3
-
@M-Andre-Z-Eckenrode said in Notepad++ release 8.9.3:
Possible bug/shortcoming, or maybe just incorrect online manual info:
One of each. But neither are unique to v8.9.3.
In general, when replying to the Announcement posts, make sure that the issue you are brining up really started in the version you comment on: if it started earlier, it really belongs in a separate discussion, and if it’s confirmed, as a normal bug report.
Quick responses to each:
The “Column Editor” dialog has actually been renamed to “Column/Multi-Selection Editor” since v8.5.4 in 2023 (in the Changes, it was lumped as part of the “GUI Enhancements”). It’s true that the manual doesn’t use the text of the “/ Multi-Selection” for the dialog title, but the screenshot in the UM has included the more recent dialog for some time. But yes, the manual does need to mention that all those dialog features work in multi-selection mode, too. (You can actually create issues in the user manual repo directly (https://github.com/notepad-plus-plus/npp-usermanual/issues) to point out things like that. {edit: fixed in PR#863}
For not being able to leave Column Editor entries blank: there was a change to
ColumnEditorDlg::getNumericFieldValueFromText()in v8.9.2 where it no longer handles the empty field the same as it used to, creating a regression in v8.9.2 (which carried into v8.9.3). (I will create an issue for this one momentarily. {edit: issue #17912}) -
-
@xomx said in Notepad++ release 8.9.3:
v8.9.3 (Scintilla) EOL regression: #17920
Thank you for the heads up.
It’s indeed a regression, but not a critical one.
Let’s wait one more week, if no critical regression or issue is reported, the auto-updater will be triggered for the release v8.9.3. -
FYI, auto-update is triggered for v8.9.3.
-
With EOL regression, I better stay on 8.9.2.
The EOL mismatch often happens when copying and pasting between different apps and web pages. In this situation, the text editor must be a reliable tool of fixing all these mismatches. -
@Vitalii-Dovgan said in Notepad++ release 8.9.3:
With EOL regression, I better stay on 8.9.2.
The EOL mismatch often happens when copying and pasting between different apps and web pages. In this situation, the text editor must be a reliable tool of fixing all these mismatches.For you, and anyone else, who needs to fix EOLs in the meantime, even with v8.9.3: regular expression FIND =
\r\n|\r|\nREPLACE =\r\nReplace All will do what you want (and can be easily recorded as a macro) -
Hello, we got an issue with the MSI file - trying to go for the gpo installation path - adding the MSI to the softwaredeployment complains that the deployment information can not be read from the package.
(we got 8.9.2, 8.9.1 already deployed sing GPOs)
any advice is appreciated (or if someone could give the MSI the required information)
-
adding the MSI to the softwaredeployment complains that the deployment information can not be read from the package.
Could you provide more detailled info?
-
@donho tryin’ - as usual with a lots of other MSIs we take to the softwareinstallation in the GPO editor, then select “new - package”, select the current npp.8.9.3.Installer.x64.msi file from our GPO deployment path, open it, then select to deploy the package in a customized version (German: Erweitert), but tried all three options in the meantime, all end with the GPO editor reporting that adding the package to the GPO went wrong because the deploymentinformation can not be read (from the package) and we should check if we got the correct softwarepackage…
(german screenshot)
-
@hknet said in Notepad++ release 8.9.3:
as usual with a lots of other MSIs we take to the softwareinstallation in the GPO editor, then select “new - package”, select the current npp.8.9.3.Installer.x64.msi file from our GPO deployment path, open it, then select to deploy the package in a customized version (German: Erweitert), but tried all three options in the meantime, all end with the GPO editor reporting that adding the package to the GPO went wrong because the deploymentinformation can not be read (from the package) and we should check if we got the correct softwarepackage…
It’s likely that Windows has placed a “Zone.Identifier” alternate data stream on it, marking it as untrusted.
If not, please check the network share where npp.8.9.3.Installer.x64.msi is stored has Read permissions for both “Domain Computers” and “Authenticated Users” (or at least your specific admin account).
