Notepad++ 7.7.1 Release
-
-
@gr-hayduk
Hello,
The issue with typing Polish characters in ANSI mode is correctly fixed with npp 7.7.1 (previously I’ve got 7.7, I’ve must have updated on another machine).
But there’s still issue with switching ANSI encoding to Windows 1250 encoding, which changes tab settings for Perl scripts (to 8 chars, I have default 4 and perl style uses default).Regards
-
Dear Notepad++ Community,
I had the same problem, my plugins don’t work after update. I have x64 version, the issue is not the x86 because I have no warning for that.
HexEditor and my own plugin (https://github.com/gaebor/NppPlugin/tree/master/rel/Win_Unicode_x64) both stopped working.
I went back to release 7.5.9 which was the last one working. After that 7.6 and 7.6.1 complained about HexEditor (x64, Unicode https://sourceforge.net/projects/npp-plugins/files/Hex Editor/Hex Editor Plugin v0.9.5/)
After that (7.6.2 and onward) they just stop working (although the dll-s present in the same location)
-
@gaebor This plugin has not been supported for 10 years.
Test this build https://github.com/chcg/NPP_HexEdit -
-
@andrecool-68 that’s the one I used, only an older version.
But HexEditor9.5.19 (https://github.com/chcg/NPP_HexEdit/releases) has the same issue: works for 7.5.9, doesn’t work for 7.7 :( -
From 7.5 to 7.7 there was a change on where / how the plugins are located. Are the plugins in their own directories in the plugins directory, i.e.,
PS VinsWorldcomT@..\notepad++\plugins> tree .\HexEditor\ .\HexEditor\ `-- HexEditor.dll
FYI: I’ve been using HexEditor 0.9.5 in N++ every version since 6.something. I certainly worked for me in all the versions mentioned here, 7.5.9, 7.7 and 7.7.1.
-
@gaebor
HexEditor plugin for Notepad ++ … is a child’s toy!
I use full editors! -
The “silent” installation switch (/s) doesn’t seem to be working anymore.
-
@MichielOverweel For the installer
nsis
, the key/s
has not been canceled!
start /wait setup.exe /s
-
@andrecool-68 I’m using the installer that’s available for download (npp.7.7.1.Installer.x64.exe). When I start that one with the “/s” switch, the installation runs interactively instead of silently. This used to work up to version 7.7.
-
@MichielOverweel Run this:
start /wait npp.7.7.1.Installer.x64.exe /s
Or so:
npp.7.7.1.Installer.x64.exe /s
-
@andrecool-68 Yes, that’s what I’m doing. Have you tried this yourself? Does it work for you?
-
@MichielOverweel
It always works for me!
I can run any installer from the command line! -
@MichielOverweel If this is a big problem for you, then use this utility:
https://www.softpedia.com/get/System/Launchers-Shutdown-Tools/Silent-key-finder.shtml
She can install the installer in stealth mode, and show the keys for a silent installation. -
The menu command Edit->Line Operations->Sort Lines as Integers Ascending broke in this 7.7.1 (64-bit) release. I.e., it does attempt to sort the lines, but the ordering is off. I can’t figure out exactly what ordering it is applying, but while ordered in some fashion, it’s clearly not correct.
It was working in 7.7, and when I reverted to 7.7 from 7.7.1, it began working again. So it’s definitely a regression in 7.7.1. I can provide a longish (140KB) file containing a list of IP addresses that reproduces the issue, if necessary.
Thank you.
-
-
@MichielOverweel said:
@andrecool-68 I’m using the installer that’s available for download (npp.7.7.1.Installer.x64.exe). When I start that one with the “/s” switch, the installation runs interactively instead of silently. This used to work up to version 7.7.
@MichielOverweel, you need to use
/S
instead of/s
flag for silent mode installation. Mind capitalS
here. -
@SinghRajenM That did the trick. Thanks!
-
@MichielOverweel said:
@SinghRajenM That did the trick. Thanks!
@MichielOverweel , Thank you! Glad to know that it helped you. Just for your reference, actually it is not a trick, but nsis installer design behavior.
From Nsis developer reference doc
There are several methods to make an installer or an uninstaller silent:- SilentInstall and SilentUninstall
- SetSilent
- Passing /S on the command line (case sensitive)
However, (from developer perspective) there are ways to make
/S
flag case insensitive (e.g. parse command line parameters and take care of/S
or/s
). Even in most of commercial s/w (at least which I developed or worked upon), command line flag is case insensitive.Once I get time, I will try to create a PR to make command line flag is case insensitive. Hope that may come in next release, if @donho likes.