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 16, 2021. It is now read-only.
Currently the editor offers autocomplete only for mentions. It'd be optimal if that autocomplete would be completely dynamic, allowing the programmer to register arbitrary autocomplete patterns.
Where the first parameter is a regular expression containing a single captured group or no captured group, resulting in the complete content being passed. The input then gets passed to the handler function, which returns the autocomplete options for that given input.
The editor would then update the view after calling the handler.
On selection another handler should be called, something like:
Currently the editor offers autocomplete only for mentions. It'd be optimal if that autocomplete would be completely dynamic, allowing the programmer to register arbitrary autocomplete patterns.
For example:
Where the first parameter is a regular expression containing a single captured group or no captured group, resulting in the complete content being passed. The
input
then gets passed to the handler function, which returns the autocomplete options for that given input.The editor would then update the view after calling the handler.
On selection another handler should be called, something like:
The autocomplete input should always be the first match and cut off at the current cursor position.
So
:Emo(Cursor)ji:
would be passed asEmo
and the replacement should be Replacementji.The text was updated successfully, but these errors were encountered: