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
It's weird that the patterns are [SORT].[EVENT].[EXT].vimhook, [SORT].[EVENT].vimhook and [FILENAME].vimhook. A better pattern might be ^\.?(\d+\.)?(.+\.)?(\w+)\.vimhook which is best visualized on Regexper. Basically it allows an optional sort key, an optional "suffix" (which could be just "js" or the whole filename itself), and the event name. They each have a "." dot between them and it allows for an optional dot at the beginning, which lets the user decide whether or not to make the file hidden.
The text was updated successfully, but these errors were encountered:
ahw
changed the title
Allow sort keys for file-specific hook scripts
Generalize hook naming convention
Jan 4, 2015
It's weird that the patterns are [SORT].[EVENT].[EXT].vimhook, [SORT].[EVENT].vimhook and [FILENAME].vimhook. A better pattern might be
^\.?(\d+\.)?(.+\.)?(\w+)\.vimhook
which is best visualized on Regexper. Basically it allows an optional sort key, an optional "suffix" (which could be just "js" or the whole filename itself), and the event name. They each have a "." dot between them and it allows for an optional dot at the beginning, which lets the user decide whether or not to make the file hidden.The text was updated successfully, but these errors were encountered: