You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
I'm using node-oniguruma to port the Sublime Text syntax highlighting engine to JavaScript. Sometimes, the engine has to restrict scanning to a prefix of the current line (because an escape pattern has been matched). In that situation, I am explicitly slicing the string. It would be better to instead pass an endPosition argument to findNextMatchSync. Oniguruma supports this, but node-oniguruma does not expose the feature, but always passes the end of the string as the end position.
The text was updated successfully, but these errors were encountered:
I'm using node-oniguruma to port the Sublime Text syntax highlighting engine to JavaScript. Sometimes, the engine has to restrict scanning to a prefix of the current line (because an
escape
pattern has been matched). In that situation, I am explicitly slicing the string. It would be better to instead pass anendPosition
argument tofindNextMatchSync
. Oniguruma supports this, but node-oniguruma does not expose the feature, but always passes the end of the string as the end position.The text was updated successfully, but these errors were encountered: