The default commands list and search keywords are provided as examples, can be edited, added, or removed according to your needs.

The new version submitted to the NppList today.
You also can access at
https://sourceforge.net/projects/androidlogger/files/v1.4.2/

@PeterJones said in When is there going to be a release of NPP plugintemplate with a definition of NPPM_ADDSCNMODIFIEDFLAGS:

Would it be possible to create the action so that it only runs if it is running in “nppplugins/plugintemplate” and would otherwise do nothing (unless the creator of the new repository changed it)?

Actually, I think you can.

An outline of such a workflow would be:

Run the build on the schedule trigger event, as already suggested in the issue thread, e.g.: on: schedule: - cron: "0 0 1 * *" #< first day of every month at 00:00 UTC

Use the checkout Action to fetch the Notepad++ trunk

Use a diffing tool or action to compare the file paths of interest. If something changed, copy the upstream files into the template’s file paths and feed the project to MSBuild

If the build passes, push the changed files and create a release

@rdipardo , @PeterJones ,
Don’t know if this question can be answered. But besides that i was wondering, why at all - as underlying reason for the question itself - the rendering of the same toolbar bitmap looked so different: in funap’s explorer plugin fine, in my test project being grayed backgrounded in dark mode.

After some thoughts & trials i found the solution:

// -- Replace: HTbBmp := LoadImage(Hinstance, 'TB_BMP', IMAGE_BITMAP, bmpX, bmpY, 0) // -- by: HTbBmp := LoadImage(Hinstance, 'TB_BMP', IMAGE_BITMAP, bmpX, bmpY, LR_LOADMAP3DCOLORS);

No more need for to provide two different bitmaps …

(There’s still a difference between both: in my case the bitmap shows a kind of ‘focus rectangle’ around when the plugin is active, whereas the other has not. But i don’t find it disturbing at all, and it’s presumably by a different setting. But maybe anybody knows why, simply for understanding).

plzz add koltin guys , i love notepad ++ everything i’m writing in it , pluzz doit :3

Nice. It’s progressing fast.

Now which will come first, https or authentication?

@Bas-de-Reuver

Issue and PR made.

@Chris-Fesko using vs 2022 doesn’t mean the code is using .net. My code certainly isn’t. It’s standard c++ throughout (though it is c++20 so i’m not sure how well that work with vc++ 6.0)

@Coises,

How do you go about testing the ARM64 version? I’ve left that out of all my plugin work so far, because I haven’t a clue how to verify that it works at all.

I don’t. I’m following the time-honored tradition of releasing software untested, and hoping that any users will find edge cases for me. :-)

Given that it works as 32b and 64b on Intel processors, and I’m not doing anything that is out-of-the-ordinary, I am hoping that there aren’t any ARM64-specific bugs

@Joe-Bruns-0 said in Single click to open file in workspace:

Enhancement request.

FAQ: Feature Requests aren’t tracked in the forum. If you want the developer to see your request, you’ll have to follow the instructions in the FAQ. But we can talk, and get ideas/feedback from other users here.

Similar to single clicking on a file in document list panel to open it, can we do the same on folder as a workspace? It would appear that in folder as a workspace, a person has to double click on the file to open it.

The two interfaces have a slightly different mindset, so, IMO, it would be a bad idea. In the Document List panel, you are dealing with files that are already open in Notepad++; in that mindset, then you’d want it to behave more like the tabbar, where a single click activates that already-open file. But in the Folder As Workspace (FaW) panel, the interface is much more like Windows Explorer: in Explorer and explorer-like interfaces, the user’s expectation is that single-clicking a file will select it, not launch it; and breaking that expectation in an explorer-like interface of the FaW panel will cause confusion on the part of many users, even though for some, it might be desired. If it were an option, I’d be okay with it; but unexpectedly forcing your preferred interface on everyone, especially on people who have been using Notpead++'s FaW for years (given how old the feature is, maybe even more than a decade) would be a bad experience for a large portion of the users.

@Terry-R

Fair enough. I thought I’d give it a shot.

Thanks for your time and suggestions.

@Mark-Olson and @Terry-R

Thank you for your answers and sorry for the late response.
I checked if there are unseen characters but there are none.

I’m sorry for not translating the error text - I just made the screenshot and never thought about it. The google translation offered by @Terry-R is correct though.

As for the mentioned lack of information:

I’m using Notepadd++ 8.7.9 with XML tools 3.1.1.13.

The XSD files are from the german tax offices and can be downloaded here:
https://www.bzst.de/SharedDocs/Downloads/DE/Handbuecher/fs_XSDs_ab_20240401.zip?__blob=publicationFile&v=3

A valid xml file which produces the mentioned error is:

<?xml version="1.0" encoding="utf-8"?> <n1:ELMA xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.itzbund.de/elan ./XSD/ELMA_FSAK_FS-6.1.0.xsd" xmlns:n1="http://www.itzbund.de/elan" xmlns:elan="http://www.itzbund.de/elan/elemente" xmlns:verf="http://www.itzbund.de/FSAK/FS/02.00" xmlns:std="http://www.itzbund.de/FSAK/FSStd/02.00" elmaVersion="2" verfVersion="6.1.0"> <elan:ELMAHeader> <elan:BenutzerkontoID>1006870761</elan:BenutzerkontoID> <elan:Transportweg> <elan:Datenart>FSAK_FS</elan:Datenart> <elan:Umgebung>PRODUKTION</elan:Umgebung> </elan:Transportweg> <elan:Identifizierung> <elan:EingangsID>1e6bb852-e445-47fc-965e-cdd2dc7f251c</elan:EingangsID> </elan:Identifizierung> <elan:Zeitpunkte> <elan:Erstellung>2025-02-28T12:20:25Z</elan:Erstellung> </elan:Zeitpunkte> </elan:ELMAHeader> <verf:FSAKFSRoot> <verf:FSAK_FS UUID="02c2af01-5d0e-1eef-bdb8-d2d5ad5dd1cb"> <verf:Melder> <verf:Daten Bezeichnung="Monster Inc." Zulassungsnummer="12345678" Steuernummer="9120012345678" eMail="mike@monster.inc" Telefon="555-1234567"/> <verf:Adresse PLZ="12345" Strasse="Monsterroad" HausNr="47" HausNrZu="a" Ort="Monsterville" /> </verf:Melder> <verf:MeldungListe> <verf:Meldung freigestellterBetrag="75" OrdBegriff="98765432" Zeitstempel="2025-02-28T12:20:25Z" Meldejahr="2024" UUID="02c2af01-5d0e-1eef-bdb8-d2d5ad5e11cb" xsi:type="verf:Meldeart1"> <verf:Glaeubiger> <verf:Daten Geburtsdatum="1970-06-19" Name="Sullivan" Vorname="James" IdNr="12345678901"/> <verf:Adresse xsi:type="std:AdresseInlandType" HausNr="11" Strasse="Homelandway" Ort="Home" PLZ="23456"/> </verf:Glaeubiger> <verf:Ehegatte> <verf:Daten Geburtsdatum="1979-11-24" Name="Sullivan" Vorname="Jane" IdNr="98765432109"/> <verf:Adresse xsi:type="std:AdresseInlandType" HausNr="11" Strasse="Homelandway" Ort="Home" PLZ="23456"/> </verf:Ehegatte> </verf:Meldung> </verf:MeldungListe> </verf:FSAK_FS> </verf:FSAKFSRoot> </n1:ELMA>

The schemaLocation points to the a directory “XSD” in the same directory as the xml file with the content of the downloaded XSD extracted to “XSD”.

Thanks again and still glad for any help!
Thorsten

@Moratilla said in Black line highlight background after use of compare plugin:

Solution: Alt+F4 & Reopen Notepad++ solves this, not the best solution but not the worst either xd

You need to turn off CSV Lint’s transparent cursor option, or the problem will keep coming back:

csv_lint_settings_panel.png

See https://github.com/BdR76/CSVLint/issues/77

@Martin-Hoppe
Open the tree view and paste your path after the @ symbol in the query box. When you select a node in the tree view, the caret will automatically snap to its position in the document.

I am the JsonTools maintainer, and thus the best person to direct such questions to.

@Coises Thanks. That works fine and have been able to test and update.

It appears that the “shortcoming” has been FIXED and should appear in the next Notepad++ release.
Nice.

@remotemachining ,

First, the user you @-mentioned was just a random user who had commented, and is not the same as the person who announced the plugin. The user you mentioned hasn’t been here since making the post in January 2024; and the user who announced the MarkdownText plugin hasn’t been here sincec 2021 (nor have there been any updates to that plugin since that year). I am doubtful that you’d get a response from either of them.

On to the specifics of your issue:

Where did you download the plugin? Did you use a specific URL (if so, share it), or did you just use Plugins Admin?

I ask, because this discussion is about the MarkdownText plugin, which would show up as MarkdownText.dll, but the error messages you typed out are referencing a plugin directory NppMarkdownPanel (which implies the NppMarkdownPanel.dll) but referencing a DLL in a lib sub-directory called MarkdigWrapper.dll – that’s not the normal way that Notepad++ plugins are set up (unless this plugin has multiple DLLs involved, and it’s just having a problem with one of them).

However, your messages imply you are actually using a different plugin, NppMarkdownPanel which is available in the Plugins Admin inside Notepad++, and has been updated much more recently… Assuming that’s the case, I tried installing that plugin and looking at a simple Markdown file: I, too, get an error message about that MarkdigWrapper.dll sub-library. Looks like there’s a major bug that’s making it incompatible.

I went to the most-recent issue that they said they closed, and the people testing the build were using Notepad++ 8.4.9 to do the testing (which would have been current in early 2023, when the last plugin release was made). And I still get the error with plugin v0.7.3 and NPP-64 v8.4.9. I also tried, with the same error, in the 32bit Notepad++/plugin combo.

However, if I instead grab plugin v0.7.0 (which is the version from Plugins Admin) in the 32bit, it works properly for me. And if I use Plugins Admin in 64bit Notepad++ and download the one there (which says 0.7.1 in the dialog, but the plugin’s About box only says 0.7.0), it also works.

So if you downloaded directly from github, try removing the manual installation of the plugin, and instead install using Plugins Admin, and there’s a good chance it will start working for you.

I personally chose the MarkdownViewer++ plugin (0.8.2) from Plugins Admin, and that one works reliably for me. But I do readily admit it hasn’t been updated since 2018, so is obviously not supported anymore.