Notepad++ v6.9.2 released

Claudia Frank

@Daniel-Carter

did you try if the local file to monitor isn’t in the root directory?
Maybe a similar test with mapped shares?

Cheers
Claudia

donho

The npp monitoring didn’t work if the file to be monitored was located in the root directory.

Indeed. I will try to fix this one.

The monitoring doesn’t always work due to Windows cache system.
I will see what I can I do about it.

leo stone

Character Encoding Detection Bug I call it the Single-ö-Bug

Hi all, I’discovered a bug concerning character encoding detection.
This bug is not specific to v.6.9.2, I don’t know since what release this bug is present.

Reproduce:

Make sure encoding for new file is set to UTF-8 without BOM
and ‘Apply to opened ANSI files’ is checked.
Settings->Preferences->New document->Encoding
Open new file
Enter the character ö, or use Hexeditor and create two bytes 0xc3,0xb6
Save the file
Close the file
Reopen the file

Result:

รถ

or Hex

0xe0 0xb8 0xa3 0xe0 0xb8 0x96

and the information in status bar is showing

Dos\Windows | TIS-620

Expected result:

ö

or Hex

0xc3 0xb6

and the information in status bar is showing

Dos\Windows | UTF-8

Remarks:

Other Umlauts like ä or ü work properly
As soon there is another UTF-8 character present, this bug does not show, eg. öö works as intended.
But this bug shows also if there are other ascii-characters present, so “Let’s test the ö bug” will also cause a wrong encoding detection result.

tx for this great editor
leo

Chris Cheatwood

I am seeing an issue when writing PL/SQL in Notepad++ on a Windows 10 workstation. When we attempt to run the saved .sql file on our database server (AIX) we get errors. We feel there are some additional characters being added when the file is saved. When we copy/paste from Notepad++ to Notepad all the line returns are missing. The only workaround we could find was to copy/paste from Notepad++ to SQL Developer then Copy/Paste that into Notepad and save.

Claudia Frank

@Chris-Cheatwood

AIX = unix, means you have to set Edit->EOL Conversion to UNIX. Did you double check this?
In addition, did you test that the sql file created has really only LF’s by using an hex editor?

Cheers
Claudia

Gilad Denneboom

I’m experiencing a very critical and worrying bug with this version, which forces me to downgrade to an earlier one. I can’t quite put my finger on when this is happening, but it has happened to me multiple times already. I’ll try to describe it.
Basically what happens is that I edit a file, save it, close it and then the next time I open it the file reverts to a previous saved version! So I lose all of my recent changes to that file… It doesn’t always happen, but it did happen several times already.
I’m happy to provide any additional information that is required, but I haven’t been able to find the exact steps to duplicate this behaivour so far…
I really hope this issue can be resolved, as I rely on NP++ for my daily work, and this issue is a major concern for me.

Thanks, Gilad.

Claudia Frank

@Gilad-Denneboom

reminds me of the filesystem redirector, can this be??

Cheers
Claudia

Gilad Denneboom

@Claudia-Frank

Not sure I see the connection… What makes you think my issue is related to that one?

(Unfortunately I can only post once every 20 minutes… And I don’t seem to be getting a notification when someone has replied to my message. What an annoying feature!)

Claudia Frank

@Gilad-Denneboom

as of version 6.9.2 npp is only available as a 32bit version.
New npp 7 offers a 64bit version.

With npp <7, if one tries to edit a file in system32 and this file
has a copy in SysWOW64 it get’s redirected as MS thinks
this is the file which should be edited instead of the one you
might have chosen.

So the edited file isn’t the one expected which could lead to the issue you’ve reported.
There are workarounds like sysnative alias or links available but because npp offers
a 64bit version I would go this way. Unfortunately the new version hasn’t all plugins
available yet but I assume this will change over time.

Cheers
Claudia

Gilad Denneboom

@Claudia-Frank

Thanks for the explanation. So the solution, in your opinion, is to wait for version 7 and then get the 64bit version of it?

PeterJones

@Gilad-Denneboom, From a 32bit app in a 64bit Windows OS (Vista or above), you can access the actual 64bit System32 file (%windir%\System32\filename) using the alias %windir%\Sysnative\filename: see File System Redirector at MSDN. (FYI: The Sysnative alias only works from a 32bit app; a 64bit app cannot see that alias.)

Claudia Frank

@Gilad-Denneboom

So the solution, in your opinion, is to wait for version 7 and then get the 64bit version of it?

I don’t know because you didn’t state if this is your issue.
And if it is, you don’t have to wait as the rc version is already out.
I use it already, in the way I use npp - no extensive tests, and didn’t came across any problems yet
and, as already stated, there are workarounds for earlier versions like sysnative alias and links.

Cheers
Claudia

Gilad Denneboom

PS. This is a very serious issue, I think (work being lost without notification or a way of restoring it). Maybe it’s a good idea to make a note of it on the download page, so that others don’t have the same issues I did… Or even withdraw this version altogether until a solution can be found for it.

Claudia Frank

@Gilad-Denneboom

(work being lost without notification or a way of restoring it)

?? - maybe you wanna reread my explanation of this.

Cheers
Claudia

Gilad Denneboom

@Claudia-Frank

Sorry, but your explanation was not very clear. I’m a fairly technical person but I really don’t feel like having to mess around with all of these settings just to get the application working correctly, as it did until recently. I think I’ll just stick with the older version until a more reliable one comes out. Thanks for your time, though.

PS. My OS is Windows 7. There is no %windir%\Sysnative\ folder on it.

Claudia Frank

@Gilad-Denneboom

My OS is Windows 7. There is no %windir%\Sysnative\ folder on it

Because it is an alias, not a folder.
Open the file dialog of npp and put it %windir%\Sysnative, press enter
and you will see the files and folders.

Sorry, but your explanation was not very clear

I’m always eager to improve my English, so you are welcome
to let me know what I’ve done wrong.

Cheers
Claudia

Gilad Denneboom

@Claudia-Frank said:

Because it is an alias, not a folder.
Open the file dialog of npp and put it %windir%\Sysnative, press enter
and you will see the files and folders.

What do you mean by “the file dialog of npp”? Do you mean the npp executable? The entire application folder? Some dialog from within the application itself? Please be a bit more specific.

PeterJones

The file dialog is reached in Notepad++ by clicking on the File menu, then the Open menu item
In either the top folder bar, or the File Name box, type %windir%\Sysnative

(the image shows the typing in both; it’s only needed in one or the other)
Select your file in the usual manner
Hit Open

Gilad Denneboom

@PeterCJ-AtWork

That does not work for me. And I’ve already downgraded to 6.9 and am still getting the same behaivour. This is getting really troubling…
What version can I downgrade to where this issue is not present?

Gilad Denneboom

I completely erased NP++ and then re-installed 6.9 (before I just installed it over 6.9.2 and the problem persisted). Hoping for the best…
If the issue still happens I will have to stop using NPP, which is a real shame since I love it, have used it for years on a daily basis, and have donated multiple times to the developers for their hard work on it.