-
Notifications
You must be signed in to change notification settings - Fork 366
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes #1524 This commit... 1. replaces `biblatex_snippet_completions` module by default ST3+ snippets as there's no obvious reason for providing default snippets by a plugin. 2. organizes all existing *.sublime-snippets in snippets/ sub directory 3. converts various *.sublime-completions files to *.sublime-snippet format to recover ST3 behavior in ST4. That's required because ST4 drops completions of which trigger perfectly matches user input in order to ensure real snippets always take precedence. Snippets to cycle through various tags via tab key have been removed as they may cause confusion when triggered directly (fixes #1555). Snippets are generally named by their trigger. Those, which differ only by case are suffixed with `_upr` to support case-insensitive filesystems. Notes: 1. line breaks in scope tag require ST3176+. 2. if no prefix is typed, completion panel shows entries only as of ST4.
- Loading branch information
Showing
174 changed files
with
783 additions
and
387 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.