-
Notifications
You must be signed in to change notification settings - Fork 0
Unexpected file auto-reformatting when 'Automatically decode entities' is checked #12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Never mind; the real issue was a too-greedy backtracking loop: 6e3800c |
Should be fixed now: https://app.circleci.com/pipelines/github/rdipardo/nppHTMLTag/18/workflows/05a1cc7f-a1a8-4f9d-b3a3-cf7ca31db307/jobs/19/artifacts Note: build artifacts expire in 30 days |
Tested - ok. |
Eee, no, I spoke too soon. In the
is no new Edit: Only arm64 zip contains the binary. |
Yep. The x86 Intel builds were targeting XP. It seems at some time in the past two weeks the XP v141 toolset was pulled by Microsoft (with no announcement 🤔?) and then Circle CI upgraded their image to pull in the newest VS Studio release. No plans on reverting to Free Pascal for the sake of XP, though. Plugin versions 1.4.4 and older will even run on NT 4.0, yes, but Pascal's memory model is broke-ass and the code looks like a dog's breakfast. No harm done since my earlier "fix" actually had a major regression in it. Newest builds are here: https://app.circleci.com/pipelines/github/rdipardo/nppHTMLTag/19/workflows/42899453-91c3-4c69-8496-c2287fb12936/jobs/20/artifacts |
@rdipardo |
Issues without a patched version on the Plugin List can stay open in case other users come here to report the same thing. |
Fixed in HTML Tag 1.5.2, available via Plugins Admin, if you are using Notepad++ 8.7.6 or newer. |
I was bitten by the following, when updating my translation file.
IDK if it is a feature or bug and can be prevented somehow(?).
STR (using fresh x64 N++ portable v8.7.4):
.\localization\english.xml
<Item id="6910" name="Minimum Size for Auto-Checking "In selection":"/>
)The text was updated successfully, but these errors were encountered: