Notepad++ v6.9.1 is out there
so you are saying you used Find in Files (CTRL+SHIFT+F) dialog and result window doesn’t show up, correct?
Did you open the dialog via the menu or by using one of the shortcuts and selecting the appropriate tab?
F7 is used for toggling between result window and editor. This only works if search result window was once created.
So question is, why don’t you get the result window, isn’t?
Sergey Den last edited by
I have the same problem:
when I download the file using NppFTP, the encoding has changed from UTF-8 to ANSI, and the EOF also change from “UNIX” (default in my Npp configuration), to “Dos/Windows”.
I have tried both using the pull down menu and the shortcut sequence. Neither has an effect. A search for multiple instances in a file also does not result in the window opening at the bottom as I expect. It appears the result window is never created.
I have found a “solution” in another site which addressed this same issue. It mentioned the config.xml file in the \user"account"\Appdata\roaming\notepad++ folder as being the culprit. I renamed this file, restarted the application and the behavior went back to normal.
Peter McIlroy last edited by
Any chance of bringing back the online documentation? All links appear dead.
good to see that you found the cause of your issue.
By any chance, can you compare the “renamed” config.xml with the new one created,
to see what the differences are?
It happened already a couple of times where unexpected behavior was solved by deleting/renaming
%APPDATA% directory or config files. So I’m curious to see what could have caused it.
Thank you and cheers
I can provide a beyond-compare output file if you tell me how to deliver it to you.
Roger Tannous last edited by
While closing Notepad++ I’m now forced to close/save/discard one of many unsaved files (like for example new 5).
I used to be able to close Notepad++ and leave unsaved files and restore everything back as I left them when I closed the app!
This feels to be a bug because Notepad++ is forcing only one of the unsaved files to be closed/saved/discarded.
looks like automatic backup is disabled.
Please check the following
check remember current session for next launch
check enable session snapshot and periodic backup
Roger Tannous last edited by
I had version 6.9, so the complaint concerns that version. Yes, I have those check boxes checked, but it doesn’t matter, I just updated to 6.9.1 and till now, there’s no problem.
Very very happy to see Fortran free format support.
However, the changelog writes “FORTRAN 77", which is actually fixed format. It should be “Fortran 90” (not all CAPS) or newer.
More on Fortran:
the old fixed-form FORTRAN highlight is now broken. All Fortran source files are now highlighted in free format style.
So sorry… old fixed form FORTRAN highlighting was not working for me because my cloud settings folder was not updated. The configuration files in the install folder are correctly setup. Once I copied these files, fixed-form FORTRAN highlighting works properly.
About default extensions:
by most common convention, “.f” is used for fixed-form FORTRAN, not free format.
David Rocco last edited by
I continue to obtain this problems… if i use FTP access and download some file for edit (like a txt file or xml) from a server if this same files it’s changed on server i don’t obtain the ask for reload and if i reload manually i don’t see the modification.
For obtain i need to re-download the file… this functions it’s very usefull when you stay to read, for example, a log file from a server… if you want to read you need every time to redownload the file.
I have also tryed to use Filezilla or use the FTP plugins of notepad++… please fix.
ftp protocol doesn’t provide any “file has changed functionality”
If the file has been changed on the server you won’t get any information,
if you would like to have such functionality you need to use something like samba.
(assuming the server is a unix host)
Basically, you need to mount the share to your filesystem so that the filesystem
gets a chance to detect file changes.
Anirudh Aima last edited by
v6.9.1 crashes some times. It erases the file that I am coding on.It has happend quite a few times now…please fix this bug immediately as i love coding on notepad++
Frank Théo last edited by Frank Théo
I just upgraded to 6.9.1 and noticed the following new behaviour:
- Open several files (2 for this test) in Notepad++
- Close Notepad++ without closing the files.
- Rename only one of the files.
- Open Notepad++
- Notice that the renamed file is not available in the open tabs, except the other file.
Before the upgrade, there was a window displayed at launchtime, asking if the file that is no longer available should be kept in Notepad++ or removed.
In 6.9.1, the window does not appears anymore.
Is there an option to recover this feature or is this per design ?
Thanks for any suggestion.
guy038 last edited by
I’ve just done a test with 4 versions of N++ :
All of them behave the same way, as for the renaming of a file, previously opened in N++
Indeed, if you haven’t closed N++ yet, then, as soon as you rename, from OUTSIDE N++, a file , which is presently opened in N++, a pop-up window appears, saying :
The file " C:\.............." doesn't exist anymore. Keep this file in editor? Yes No
But, referring to your point #2, once N++.exe is CLOSED, how Notepad++ could know, that you modified a file, in the meantime, although it was previously opened in N++ ??!!. For the four versions tested, the tab, of the renamed file, has logically disappeared !
To my mind, as the file, with its previous name, doesn’t exist any more, the N++'s reference to that file is wrong, by now and N++ can’t open it, in a tab !
Frank Théo last edited by
Hi @guy038! Thanks for your reply and the testing.
However, after further tests, a similar expected behaviour could be reproduced by modifying one of file at step #1 without saving the changes.
Close N++. Rename (or Delete !!) the file you changed. Open N++. The file is still displayed in the same state as it was when closing N++.
– At this stage, I think that this behavior for unsaved files is important, useful and should never be reconsidered :) I was rather worried about these unsaved changes than about reopening deleted (but saved) files.
I had the feeling that this was the case before the update, so I was wondering if it changed some settings that I have not seen in the preferences. (This is technically possible with a cache, I do not expect that N++ find the renamed file by itself, but load it from the cache instead, like with an FTP and partially with the unsaved changes to the files).
Anyway, the last update works like a charm! Thanks again for your time, and thanks to N++ team/contributors who are doing a really great job.