@PeterJones Great catch! Thanks Peter!! It works! I didn’t notice the double .XML.

Just noticed your comment about the extensions. I keep it like that because I frequently use the search software Everything and several file conversion programs. I need to know what I’m dealing with while using them simultaneously.

The other reason I keep it hidden is so I don’t accidentally screw up the extension and can’t find the file. It’s happened to me several times. The only way that can happen is when I use Everything, However, it nicely only highlights the file name and not the extension, making it harder to unintentionally change the extension.

@PeterJones said in posting code (by copy & paste) with line numbers:

@Lycan-Thrope ,

If it’s automatically picking the D language, have you looked at Settings > Preferences > New Document > Default Language – does it say D instead of None (Normal Text)? If so, change that preference back, and it will go back to defaulting to normal text. (That setting cannot be affected by UDL, so I don’t see how your dBASE UDLs could be doing anything to influence it…)

@PeterJones ,
Thanks, this was the cause.
Now that I think back, I think I was doing a help in the forum and used that to show the language setting and take screenshots…and forgot to put it back. DOH!!
Back to normal…thanks for curing my forgetfulness. :-)

@guy038 Oui, merci beaucoup!

@MarkusBodensee said:

Highlight the entry in the dropdown and press Del to delete.

To extend this idea, drop down the combobox, then press and hold Del (aka Delete) to remove all entries (ask the key repeats).

So it really was a Scintilla v5.5.6 bug, fix for its next version:
https://sourceforge.net/p/scintilla/code/ci/0364bca4f6d3cb1e1aaffa3baae6a0dfe4b026f2/

@PeterJones Peter, oh sorry - i hadn’t realized it this morning in the hurry, my bad!

@ryangray01 ,

note from moderator: please reply to the original topic, rather than creating a new topic, otherwise readers lose all context. I have fixed this post (and one other), but it’s really better if you just keep the reply in the same topic to begin with.

update: two of your three posts so far seemed like AI nonsense; two of your three posts so far have replied into a separate topic from the post being replied to; it is really looking like you are just here to disrupt communication, rather than participate in community. If your next post is as meaningless as two of yours, or if it requires extra moderator effort to re-connect it to context, I am going to conclude that you are an AI, and thus react according to our forum’s policy on AI nonsense.

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

@rdipardo Wouldn’t a better place to put the action be in the notepad++ repo so when a new version was released it’d do the updates to the template repo automatically?

You make a good point.

The workflow steps would essentially be the same, but in the opposite direction (clone the template repo, update the file tree, validate the build and push if successful). The main difference would be the trigger; ideally you would want to watch for tagged Notepad++ releases, e.g.,

on: push: tags: - 'v*'

This way new template versions can be explicitly tied to a Notepad++ release, e.g.,

# 'refs/tags/vX.Y.Z' -> 'vX.Y.Z' echo "NPP_RELEASE=${env:GITHUB_REF}.Split('/')[2]" >> $env:GITHUB_ENV # ... git tag -a "${{ env.NPP_RELEASE }}" '@' -m "plugintemplate-for-Npp-${{ env.NPP_RELEASE}}" git push --tags --repo=https://github.com/npp-plugins/plugintemplate

But it would be a problem if incompatible changes were made to the template. A failed build would cause a red X to appear beside the tagged Notepad++ commit, giving the false impression the release was a botch.

I think the separation of concerns principle is best observed if the template project looks after its own updates. A little extra churn won’t be a great inconvenience. The majority of plugin authors are still copy-pasting the template files into their source tree, as shown by how many have “C” as their detected primary language, since the template files contain no unique C++ syntax or standard headers, which GitHub relies on to classify header files, unless you manually override the heuristics.

@schnurlos

https://notepad-plus-plus.org/news/v88-we-are-with-ukraine/ gives an Error 404 (link within “F1” Info).

It’s because v8.8 is still in RC state.
It will be on line in few hours.

@Coises

Maybe I just didn’t understand the meaning behind it.

So that’s right. :-)

It looks like I don’t need to do this kind of work that would benefit from a cloned view, or not often enough. In the cases where I need to jump to different places, I use bookmarks, but I understand that you’d rather have the other area in the second view if you need to do that repeatedly.

As for notifications, I’d have to look in my notes, which I don’t have access to at the moment, but from what I remember it was about both npp and scintilla notifications. I suspect this will be one of the issues that will be addressed when everything else is working and the plugin is officially released.

30000 vs. 32767

I’ve no idea where 30000 originates. A quick search of the Notepad++ source code won’t find it literally. So… apologies to @mkupper about the “sloppily” thing; I did think you were speaking in “ballpark” terms.

@Coises : My thoughts about the topics:

“IsDialogMessage” (“standard Windows way of separating messages that are directed to a non-modal dialog or any of its child controls from the normal flow through the message loop”) and “WM_GETDLGCODE” (“If keyboard focus is in a control, that control will decide which keys it wants and which keys should be processed as container navigation”):

Basically the Lazarus component library (LCL) acts as a fully qualified message loop system that is able to react on nearly each message and notification within a windows message loop, nearly all WM_, eg. WM_KEY(down,press;up;…) can be detected and processed (*).
Normally it’s hard to detect any lacks here imo. However i initially looked into that hierarchy, as here, like everywhere else in the programming world, some business rules might have been come into play for to negate a message (like eg. an app can do when it nulls out an Enter Key for to suppress a beep; Key := #0).

(*) At least in the win32 “widgetset” as one within all those platforms: all-interfaces win32-interface
It depends a bit on whether someone compiles “cross-platform” or for an OS-specific build, ie. “win32”):

But - right, maybe that is it what matches your pointing! - there is no explicit call of “IsDialogMessage” itself within the LCL hierarchy (i grepped here)!
But it is a function that is known and predefined in the free pascal compiler system (FPC) though. And, so, there really low-level based apps can be written (and do exist) without the LCL, using basic TranslateMessage, DispatchMessage etc. which are calling “IsDialogMessage” explicitely.
“Matches your point” in so far as it makes understandable why without NPPM_MODELESSDIALOG (which calls “IsDialogMessage”) “most shortcut keys will be intercepted by Notepad++” - with other words, let NPP act as a gate-keeper for messages here.

In sum, with your explanations it’s much more understandable now for me what’s going on (hope so).
And why “RegisterForm” (-> the NPPM_MODELESSDIALOG-Send) in the docking formcreate now lets work again F2 (and Ctrl-c, Ctrl-v & co.) by the plugin. Otherwise the NPP gate-keeper would decide itself and won’t pass messages to the plugin that it claims for own usage, e.g as defined in the shortcut mapper.

I hope I’m somehow on the right track here :-)
I’d use this solution, it does indeed remove the issue :-)
(i have to sort out a few subsequent flaws now, but those are assumingly outside the current thread)

@dr-ramaanand said in need help to look for a word:

simply because it is easier

That’s apparently a matter of opinion. To me, negative lookbehind, where it’s telling you “look behind the current position, and make sure it’s not XYZ” is a lot easier to read/understand than “match something, then say, wait no, I don’t actually want to match that, let’s fail this whole path and move on to the alternation”. (And, from what I can tell, that’s not really a good explanation of skip+fail, because it takes our regex guru pages of text to explain it, whereas I can successfully convey the meaning of a negative lookbehind in one sentence.)

Since your first version of the skip+fail post was wrong, and you couldn’t tell this immediately, even after it was pointed out to you that it was wrong, I am not convinced that it’s truly as “simple” – even for you – as you are implying.

I am going to stick with recommending solutions that i could explain if necessary; I will only personally link to the skip+fail formula if I know of no other way to do something (and I wouldn’t tell anyone it’s “simple”)

But if it truly makes more sense to you than a negative lookbehind, that’s great for you; everyone is different.

@peklei said in UDL: Folding with Alt-0 no longer works correctly:

It would be interesting to know how this is implemented there and whether it can be recreated in a UDL definition.

In a UDL definition? No. Each built-in lexer has dedicated code for deciding where to fold (if that lexer has folding). The source code for UDL has a separate set of code, that is purely keyword-based.
From the “UDL definition” point of view, all you can do is set the open/middle/close keywords; you cannot change the logic from the UDL interface or config file. If you wanted to change the logic, it would require a change to the UDL source code, which requires a feature request

@PeterJones said in Is the shortcut mapper dialog box broken?:

Could you download the appropriate artifact for your installed Notepad++, and see if this build fixes it for you?

I’m now using both the MSVC.x64.Release and MSVC.Win32.Release Notepad++.exe files. The shortcut mapper issue has been fixed. Thank you @PeterJones

Hello, @collingsjj, @peterjones, @alan-kilborn and All,

@collingsjj, if you don’t mind to study a simple plain text, just send me, by e-mail,

An example of your code containing the ESC sequences and similar codes. If possible, a text between 20 and 100 lines !

A snapshot of your corresponding code on your terminal

I’ll try to find out a regex search which could delete ALL these codes

For example, as a first approach, the following regex :

FIND (?-i)\x1b\[\d*(;\d+)?m

REPLACE Leave EMPTY

Would modify this INPUT text, taken from your GitHub issue #16437 :

 | Cannot find path 'E:\SharedData\jDownloader\cfg\downloadList4838991.zip' because it does not exist. Get-ItemProperty: P:\Backup\BackupScripts\ArchiveAttributeUpdate.ps1:3 Line |  3 |  . es -ea SilentlyContinue -value ((Get-ItemProperty $_.fullname).Attrib .  | 

Into this clean OUTPUT text :

| Cannot find path 'E:\SharedData\jDownloader\cfg\downloadList4838991.zip' because it does not exist. Get-ItemProperty: P:\Backup\BackupScripts\ArchiveAttributeUpdate.ps1:3 Line | 3 | . es -ea SilentlyContinue -value ((Get-ItemProperty $_.fullname).Attrib . |

My temporary e-mail address is :

Too late !

Best Regards,

guy038

@rinzwind5 said in Notepad++ whitespace autocomplete define:

bgColor is hard-coded in each UDL and cannot be set to ‘inherit/default’ (as in use the NPP theme setting’s background).

Nitpick: you said "Cannot be set … "; but the reality is that it would be better to say “can be set in exactly the same way as you do in the NPP theme setting’s background” – ie, by right clicking the color or toggling the checkbox for Transparent

Here’s a screenshot of a UDL defined with keywords one two three in red-on-transparent (and that UDL’s “Default” styler set to black-on-transparent – not shown in screenshot), when originally set up in Default (stylers.xml):
ef38e661-4a15-4182-94c0-b4ef82b6cddc-image.png

And here, all I did was change the theme to Solarized - Light: the background changes with no change to the UDL:
fe093247-e6bf-41d0-8ac6-2a345d36eaff-image.png

“default style” is working fine for my purposes.

I will propagate these configuration changes to any other old installations I may have.

Thanks to all for the very effective help!

-Phil

And now - whilst i was a bit irritated why i should not have seen during my tests that indeed ‘LR_LOADMAP3DCOLORS or LR_LOADTRANSPARENT’ would remove the ‘looks like focusing’ effect too, i repeated the steps for a check. And what do i see? Hello again, the ‘focusing effect’ is back:
marked_active.jpg

Crazy & curious … and not severe, indeed. But not understandable neither …
as i only became aware of this because this did NOT happen with other plugins, eg. the explorer plugin.
But meanwhile i think it’s ‘normal’ for an active (loaded) plugin to show up with a kind of ‘active’ marker.
Is it as such, and i simply was misleaded by, eg., the explorers bitmap rendering?
At least others like JSONViewer or the HelloWorldPlugin itself use the active indicator too:
HelloWorld_active.jpg
So, maybe a simple misunderstanding … but is the marker done from the NPP core itself, or by a statement from a plugin?

Btw: yes, NPPM_SETMENUITEMCHECK had been called indeed (in the plugin’s “FormDock” procedure).
But it doesn’t make a difference if i either omit this call, or use ‘false’ for the “doCheck” parameter:

SafeSendMessage(self.Npp.NppData.NppHandle, NPPM_SETMENUITEMCHECK, self.CmdID, 0);