Add support for backrefs in file names #198
Open
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.
At my work I'm working with a lot of custom EDA tools that have redundant filename patterns. So, backrefs in the file names would useful, at least for me! Please let me know what you think. I did a few manual tests to check for navigating and completion working on both Windows and Linux.
For paths with redundancy, capture the repeating part of the path. Any * or ** in the pattern creates a capture group, which can be repeated with {1}, {2}, {3}, etc. Also, adds support for multiple single * groups, and for * before **. Can support up to one **, and it groups all extra matches into it like "x/y/z".
Example .projections.json:
Examples:
:Econfig tmp-> src/config/tmp/tmp.cfg:Eabc a/c-> a/a/c/c.abc:Eabc a/x/y/z/c-> a/a/x/y/z/c/c.abc