Scintilla Update frequency
dail last edited by
@MAPJe71 v3.7 should be out in a few days.
Can I request a pull request and include the scintilla upgraded components alone
Don Ho will not accept updates to Scintilla. He handles all this himself. (I hope v3.7 will be a good candidate for Don Ho to consider; lots of nice features :) )
or include the scintilla components as well in my Lexer Pull request?
Pretty much anything changing something inside the Scintilla directory won’t be accepted. This is mostly due to making sure to not maintain a custom version of Scintilla. It is easiest just to use it as-is and keep all the Scintilla stuff strictly to the Scintilla developers.
@dail /@MAPJe71 ,
Thx for your response.
I hope Scintilla version 3.7.0 gets updated.
@donho , Kindly consider upgrading Scintilla Version to 3.7.0 (will be released next days).
donho last edited by
Sure, I’ll make it happen in the future version.
Thx @donho . WIll await the future version. Just for info, scintilla version 3.7.0 is released.
I made a Python script to apply all the necessary Notepad++ changes (w/ or w/o Boost RegEx support) to a Scintilla official library release.
Let me know if you’re interested.
Claudia Frank last edited by
I’m interested - can I get it too ;-)
Sure, interested in the script.
Let me know.
See my fork’s Convert-to-SCI-for-NPP branch.
cmeriaux last edited by cmeriaux
Your script is amazing. It should have take a long time to do it.
There is also a scintilla mirror on github https://github.com/mirror/scintilla
What about adding it as a submodule. Wouldn’t it be more convenient ?
Wise? Probably not. When any change to a third-party library gets automatically integrated into the this project, the project also automatically inherits the libraries (new/unknown) issues e.g. none backwards compatible changes in its interface.
IMO a controlled/managed update of third-party libraries/tools with regression tests/checks is preferred.