@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.)

@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.

@Alan ,

TextShaping.dll is not a file that comes with Notepad++, nor is in in the right location for Notepad++ to be trying to load it as a plugin. If your copy of “notepad++.exe” is trying to access that DLL, scan those files and your entire computer for viruses!

@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.

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!