Thanks @Coises & @rdipardo
I tried this and its working but still not better. You can suggest anything if I can add more styling.

10f9d4ce-57f8-4d4c-a375-a9f4450b524e-image.png

h-jangra/BetterMarkdown/releases/tag/0.1

Ok I see the “Useful References” link under Regex Special Characters for Searches, that explains it pretty well.

Thanks again.

Barry

@pbarney said in PHP Linter PythonScript:

my impression is that Pythonscript ships with 2.8

From Plugins Admin, PythonScript v2.1.0 uses Python v2.7.18 (as far as I am aware, there is no such thing as Python v2.8).

However, if you go to the PythonScript releases page, you will see that there is also an “alpha” track of PythonScript v3.0.x (currently at 3.0.24), which use Python v3.12.xx. This is the route I personally recommend (caveat below).

The maintainer of PythonScript has chosen not to take PythonScript 3 out of “alpha” until it fully supports non-unicode encodings (ie, until it supports the 1980s-style character set encodings), so until that point, to get a maintained version of the Python interpreter for PythonScript, you have to manually install an alpha version of PythonScript – essentially, you have to put up with legacy syntax of Python if you want to deal with legacy non-unicode encodings of text. I personally have no need of supporting 80s technology for file encodings (and I pity anyone for whom their circumstances demand that they deal with file encodings that haven’t been brought into this millennium anytime in the last quarter century), so I use the 2020s version of Python for my PythonScript. (My personal opinion is that PythonScript should start shipping PythonScript 3 as non-alpha, and that they just prominently make it clear that if you have to deal with the old character sets that you should instead install the outdated PythonScript2 version from the releases page. But my opinion on such things holds no weight.)

I seem to recall that there was a bug in the main GitHub repo about this kind of issue, where it was extremely slow to move tabs when a lot of tabs were open.

I also seem to recall that this issue was solved, probably in the last year. I’d recommend that @Wilson-Azambuja-Porto-Alegre-RS install the most recent Notepad++ version and see if that fixes the problem.

@Alan, listen to @PeterJones when he says to scan your computer for viruses. TextShaping.dll is commonly used in DLL sideloading exploits, and if your executables are trying to call it when it resides in a place it doesn’t belong (your Notepad++ directory), then there’s a good chance your computer has been hacked.

That doesn’t mean you should freak out just yet, just take some steps to ensure that you’re not hacked.

@Rick-Kosters, .docx files are compressed files, so unless you’re able to uncompress them first, you’ll never be able to use a third-party program to search them.

For what it’s worth, 7-ZIP, Pkzip, WinZip, WinRAR, etc are all capable of opening those files. If you do unzip them, you’ll find a number of files and folders. What you’re looking for is most likely in word\document.xml.

@Dan-McGovern ,

-openFoldersAsWorkspace works just fine with -settingsDir and -titleAdd and other similar options, in my experiements.

But, as far as I can tell, once -openFoldersAsWorkspace is specified anywhere on the command line, all path arguments are treated under the rule, “if it’s a folder, put it in the FolderAsWorkspace panel, and don’t open any file-paths directly”.

That seems like the intent, because I don’t think it was considered that notepad++.exe myfile.txt -openFoldersAsWorkspace SomeDirectory\ would be a normal use-case (ie, when adding the feature, didn’t think that you’d want to open a file from one location, plus a folder-as-workspace from another, in the same command-line)

If you don’t have the -multiInst argument, and if you don’t have the multi-instance preference set, then you could break it up into two calls of notepad++.exe

"%np%" -settingsDir="..." -openFoldersAsWorkspace "%workspace%" "%np%" -settingsDir="..." "%file%"

In that incantation, the oFAW has to come first, because of the known-and-never-solved issue that oFAW doesn’t work on an already-running instance of Notepad++.

… But since I seem to remember that you do have the multi-instance preference set, that’s not likely to work for you. In which case, until you do a feature request, and it was accepted and implemented and released, I don’t know that you’ll get exactly what you want.

I’ll update the manual to better explain current behavior with the oFAW option.

Hello!

I’m having a similar problem with NPP being slow to open, and I believe it’s related to the fact that I have several “draft” (unsaved) files saved, since I have the options enabled: backup and remember last session.
This has already been reported in another post:

https://github.com/notepad-plus-plus/notepad-plus-plus/issues/14000

In my case, I have an SSD and it takes about 20 seconds to load about 200 files. So it spends about 0.1 seconds per file.

I did some tests using Process Monitor, as shown in the image below.

notepad.png

In this case, it seems that NPP keeps trying to create files in the “Program Files” folder, but it gives a “NAME NOT FOUND” error.
After that, it goes to the “AppData/Roaming…” folder where the backup files are located.

In short, based on this result, does anyone have any idea how to try to solve this delay, perhaps caused by failures or repeated attempts to read/write the backup files?

@PeterJones @guy038 @W-H @Ava-Thompson and everyone

Thanks a lot for checking out NppVim and for all the support. Really appreciate the feedback and the nice words.

Quick updates:

Repo here: https://github.com/h-jangra/NppVim I’m still actively working on the plugin, adding more motions, fixing bugs and making things feel closer to real Vim. More text objects, better repeat for t/f etc all in progress.

I’m glad to hear interest in supporting the project. I’ll set up GitHub Sponsors soon and will update this thread.

Thanks again for trying it out and giving feedback, it motivates me to keep improving it.
Please feel free to open issues on GitHub for any bugs or features you want prioritized.

All the gup.exe does is to check if there is a newer version than specified by the string input parameter is available. It does not handle the update itself. You would have to code it for yourself.

For example like this in Powershell 5.1 for the 64bit version of Notepad++.

[string]$ScriptFolder = $PSCommandPath | Split-Path -Parent $Notepad = Get-ItemProperty -LiteralPath 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\Notepad++' $InstalledVersion = $Notepad.DisplayVersion $UpdateCheck = Invoke-WebRequest -Uri "https://notepad-plus-plus.org/update/getDownloadUrl.php?version=$InstalledVersion" $UpdateCheckAnswer = ([xml]$UpdateCheck.Content).GUP if ($UpdateCheckAnswer.NeedToBeUpdated -eq 'yes') { $Filename = $UpdateCheckAnswer.Location.Split('/')[-1] Invoke-WebRequest -Uri $UpdateCheckAnswer.Location -OutFile "$ScriptFolder\$Filename" & "$ScriptFolder\$Filename" '/S /closeRunningNpp' }

Would it be possible to add a column (or two) to the Plugins Admin? Created and Last Updated sortable columns to be able to find the most recent plugins.

It would also be wonderful to have another column Description that just gives the first line of the longer description that is displayed in the lower box when you click on a plugin.

Hi everyone!

I have some good news and bad news.

The good news is that I’ve finished WebEdit 2.9, which includes several new features: multi-select support, tag recommendations, quick tag addition/editing, and a few other minor upgrades.

The bad news is that I’ve actually finished all the essential features I wanted to implement, so I’m not planning any further developments for the time being. Of course, you can still report bugs/issues and even make minor development suggestions, but the goal remains to keep the plugin fast, lightweight and easy to use.

The overview of the (new) features is also available on the module’s main page: https://github.com/Krazal/WebEdit

What’s next: when I have time, I’d like to return to my own plugin, because it has been full of bugs for months (not my fault!). ^^’

Thank you for letting me contribute to this plugin, which I hope others will find just as great and useful as me!