@donho said in v8.8.9 and ConfigUpdater plugin:

@PeterJones

It’s already fixed in the GitHub, but I didn’t make the plugin list cutoff deadline.

Are you talking about it?
https://github.com/notepad-plus-plus/nppPluginList/pull/999

It’s in the current PluginList in RC normally.

I ran:

Plugins > ConfigUpdater > Reset Validators Plugins > ConfigUpdater > Update Config Files

The open tab with ConfigUpdater.log no longer shows any errors

@KingRustamus

I’ve encountered such stuff before and it was caused by the Windows ransomware protection “Controlled folder access” in action. (build in Notepad.exe works in such a case because all the Microsoft own signed binaries have a build-in exception).

So check (try to set temporary off or add a new Notepad++.exe exception there) the Windows Settings > Privacy & Security > Windows Security > Virus & threat protection > Ransomware protection > Controlled folder access.

If it doesn’t help, I can prepare a testing build of the notepad++.exe binary showing us exact system error code (and it’s not the ERROR_ACCESS_DENIED for sure, otherwise in the v8.8.6+ you saw the UAC-elevation prompt 1st) leading to this SaveFailed N++ messagebox.

@fml2 said in Set current directory to default if no real file is open:

I’ve created two feature requests: one in Notepad++ and another in the Python Script plugin (and cross referenced them), since I don’t know where this feature would be better impemented.

https://github.com/notepad-plus-plus/notepad-plus-plus/issues/17246 https://github.com/bruderstein/PythonScript/issues/401

I commented to your Notepad++ issue with a UI/design suggestion; hopefully no one will mind me repeating it here.

What would you and others think of this idea?

At Settings | Preferences… | Default Directory, indented beneath the bottom radio button (where you can specify a default directory), add a checkbox labeled Apply only to Open/Save on new tabs; otherwise follow current document.

The behavior when that box is checked would be as follows:

When the active tab already has a file on disk associated with it, behavior is the same as Follow current document: Open…, Save As… and Save a Copy As… open a file dialog in the directory that contains the file, and Save just saves the file in place.

When the active tab is new — does not have a file on disk associated with it — Open… and Save open a file dialog in the designated default directory. Save As… and Save a Copy As… behave as Follow current document does now: they open a file dialog in the directory corresponding to the most recently active tab that was associated with a file on disk.

That way you can still save new files in the directory in which you are already working by using Save As…, or in the default directory by using Save. Opening a file when the active tab has a file on disk would start the open dialog in the same directory, while opening the first file in a session would go to the default directory without the need to modify the Start In property of the Notepad++ shortcut.

@Sinsearach ,

Just updated after quite a long while,

So that means it wasn’t just v8.8.8 that you had the problem with. Please only use the “Notepad++ x.y.z release” announcement topics for changes between immediately-previous version and this version. For example, that v8.8.8 topic should only mention regressions that changed behavior between v8.8.7 and v8.8.8. Any other problems you find when you jump from v8.1.5 (for example) to v8.8.8 should go in “help wanted” (where I put this duplicate discussion), and if can be confirmed as a bug in Notepad++, we will direct you on where to put in the official bug report. But it’s not an immediate regression with v8.8.8, so doesn’t belong in that discussion.

TextFX (NppTextFX2) plugin

mumble mumble… I wish the person who had done the conversion to make it compatible with N++ v8+ had renamed the menu and About box, not just the underlying DLL. (Not your fault, I know… but if someone accidentally just calls it TextFX, we are led to believe it’s the out-of-date incompatible plugin. So thanks for at least putting the real name in parentheses.)

plugin will not work (appear at all), whether installed manually or through plugin admin,

Weird. I just took portable v8.8.8 on my Windows 11 machine, and used Plugins Admin to install NppTextFX2 1.4.1, and it installed just fine. When N++ restarted, the TextFX menu was there, and I tried a couple random commands, and they did what was expected.

I would be very much surprised if this were a Windows 10-vs-11 thing, because NppTextFX2 hasn’t changed recently, and N++ itself is tested on both Win10 and Win11…

Yes I ran as admin.

when did you run as admin? when you installed the plugin? or when you tried to run the plugin? or both? Because if you’ve got a portable Notepad++, it should be in a directory where you have full write access… and you shouldn’t need to Run as Admin (in fact, since v8.8.6, you probably shouldn’t need to Run As Admin for just about anything; it will individually ask for permission when writing files in protected directories). But if you installed it as Admin, maybe it broke the permissions of your portable directory

In your portable 64-bit (you shouldn’t need to use 32-bit in modern OS): please do the following:

go to ?-menu, and share your Debug Info with us show us a recursive directory listing of your portable Plugins directory, so that we can see that the directory hierarchy is correct (dir /S from a cmd.exe prompt, or powershell equivalent)