How to Stop Literal String Highlight in Notepad++

[freefog]

Hi there, would be wonderful that Notepad++ stopped highlighting the literal strings so it would be much nicer to code Handlers Snippets?.

I have been digging arround Notepad++ plug-ins forums and playing with the Notepad++ configurations files for hours with no good results; if anyone has achieved this or anything similar I would really greet the answer.

Thanks for your Time.
FF.

[OrionShock]

you could always remove the brackets when debugging. Granted you'll have to put them back in when you go to load it in game..

[freefog]

Xd
I know.
That is what I want but ...
If it is possible in a more automated way...

Thanks any way.

[Arrowmaster]

Notepad++ is based of of SciTE so I think this should work. The literal string matching in SciTE doesn't check for balanced sides it just checks for "[=*[" and "]=*]" so you can break it with nesting.

Try the following.

str = [=[
--[[
]]
code here
]=]

[Xinhuan]

Originally Posted by Arrowmaster

Notepad++ is based of of SciTE so I think this should work. The literal string matching in SciTE doesn't check for balanced sides it just checks for "[=*[" and "]=*]" so you can break it with nesting.

Try the following.

str = [=[
--[[
]]
code here
]=]

Notepad++ does check for balanced sides, but its not 100% foolproof and can be broken. Your example will highlight correctly. but

str = [[
--[[
code here
]]

would highlight incorrectly (it would in fact color the rest of the document as a comment). Of course my literal string example here wouldn't compile.

[Nevcairiel]

So its not exactly broken, as it apparently behaves like the Lua parser?

Also, just for correctness, Notepad++ is NOT based on SciTE. Both Notepad++ and SciTE are based on the Scintilla Editor Framework (SciTE initially was a reference implementation), but Notepad++ extended the Syntax Highlighting itself alot, you can even define your own rules, if you wish.

[Arrowmaster]

I was just too lazy to lookup how to spell Scintilla.

Does this work?

str = [[
--]]
code here
]]

I completely broke SciTE's syntax highlighting with something like this before.

--[=[
code
--[==[
--]=]
code
--]==]

If you are wondering about my sanity, I would change to first line to have either 2 or 3 -'s and use it as a giant toggle.

[Nevcairiel]

Originally Posted by Arrowmaster

Does this work?

str = [[
--]]
code here
]]

It shouldn't parse in Lua.

[Xinhuan]

Originally Posted by Arrowmaster

I was just too lazy to lookup how to spell Scintilla.

Does this work?

str = [[
--]]
code here
]]

I completely broke SciTE's syntax highlighting with something like this before.

--[=[
code
--[==[
--]=]
code
--]==]

If you are wondering about my sanity, I would change to first line to have either 2 or 3 -'s and use it as a giant toggle.

both of your examples here highlight as expected by Lua parsing rules:

str = [[
--]]
code here
]]

--[=[
code
--[==[
--]=]
code
--]==]

The underlined parts above are what is in "green comment colouring" in Notepad++.

[Whitetooth]

You could always edit the source, its easy to do too.

1. Download src from: http://sourceforge.net/projects/notepad-plus/files/
2. Comment out the lines responsible for SCE_LUA_LITERALSTRING in \scintilla\src\LexLua.cxx:

   			} else if (sc.ch == '[') {
   				sepCount = LongDelimCheck(sc);
   				if (sepCount == 0) {
   					sc.SetState(SCE_LUA_OPERATOR);
   				} else {
   					//nestLevel = 1;
   					//sc.SetState(SCE_LUA_LITERALSTRING);
   					//sc.Forward(sepCount);
   				}

3. Compile SciLexer.dll
4. Backup/Replace original SciLexer.dll
5. Done.

I have one compiled for windows if you feel lazy: http://rapidshare.de/files/48657362/...r.dll.zip.html