@Ahu-Lee

Instead of generically stating it doesn’t work, you will have to provide more details to even attempt to figure out why it isn’t sorted for you. Because I’m using v7.4.2 and it is working fine for me.

@MAPJe71

I’ve finally uploaded some <parser>-elements to the Matlab File Exchange.

I think I may have solved my own problem.

I had several (6 or 8) files in the Notepad++ editor. Some of the files had been open inside the editor for several weeks.

I closed all of the files, uninstalled Notepad++, then did a clean installation. It seems to be working okay now.

Evidently, leaving open files in Notepad++ for weeks caused something to get clogged up.

One of the mods can mark this thread resolved if they like.

@陳同

does this happen also if no plugins are installed?
To test you might run npp with -noPlugin switch or temporarily rename plugin directory.
If this doesn’t help, please post you debug-info which is available under ? menu.

Cheers
Claudia

@Dickie-Davies

check if another language has occupied the .js extension.
Either use the Dialog Settings->Style Configurator and step through the languages
or open langs.xml and see which language uses the extension.

Cheers
Claudia

It works.
Thank you

@cjmac27
There are a couple of check-boxes, which might need checking: Settings,Preferences,MISC., “Document Switcher”, check Enable and check Enable MRU behaviour.

@Claudia-Frank

Oh. After a few days the problem disappeared. Exactly.

It seems that the plugins haven’t been updated. Nothing plugins was switched off. Npp ver 7.3.3 remained as before.

Mystic.
Perhaps the problem disappeared after reseting “Preferences -> Delimiter” and restart Npp.

@Contafisc-Empresarial

Unless I am misunderstanding what you are wanting to do (very possible!), I’d say that changing [^0]. to [^\s0]{2} does what you need. It means: for the next two positions, match as long as both positions are not some combination of:

whitespace (the \s) zero (the 0)

Any news on this topic?

This seems to be an issue with the https / TLS connection - at least in my case it works fine without https in front - with https I receive this error.

Maybe this can be fixed easily in the next version.

Thanks, Mark