Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found that it was impossible to create custom shorthands that can tab in any order, so I added a way to define the order to go through the
#tab
s.For example:
\left#cursor #tab \right#tab
would always tab to the middle instead of the second tab, which is annoying and does not make sense for this custom shorthand.To fix this, I added a way to optionally define the order of the tabs like this:
\left#cursor #tab2 \right#tab1
This will first tab to
#tab1
and then to#tab2
.Other example:
\binom{#tab45}{#cursor}#tab12#tab999
would go to#cursor
, then to#tab12
, then to#tab45
, and finally to#tab999
(the numbers are chosen in increasing order).The normal
#tab
s still work for backwards compatibility, the only difference being that they are now searched from the start of the current line instead of after the cursor's position (which shouldn't be a problem since all previous custom shorthands had to have the#tab
s after the#cursor
.The description for the custom shorthand parameters in the settings was also updated to explain this addition.