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
Hi! Thank you so much for this extremely useful extension. I'm loving it so far. 🙇
One wish I have for this extension is the ability to do filter the file list using a negative lookup. For example, let's say we have the following file tree:
a
- b
- c
- d
- e
In a very large tree, I want to exclude everything under a/b. I tried to filter them out by using a regular expression such as (?!b) and (?!a/b), but it doesn't seem to filter out anything.
Would it be possible to add support for negative lookahead/behind regular expressions?
The text was updated successfully, but these errors were encountered:
I can see that you want an advanced search mode. Actually, negative lookahead/behind regular expressions are already supported. However, for now, regular expressions are applied to file/folder names, instead of paths. That is why you got confused. I will update the description of search modes to prevent that.
And if the regular expressions are applied to paths, there will be no way to highlight results because matched characters of different paths can vary and get users more confused.
For now, I'd suggest manually collapse those folders you'd like to exclude after searching.
We can keep this issue open to see more users need advanced search mode.
EnixCoda
changed the title
Negative lookahead/lookbehind regular expressions
[Feature] Advanced search modes
Dec 25, 2021
Hi! Thank you so much for this extremely useful extension. I'm loving it so far. 🙇
One wish I have for this extension is the ability to do filter the file list using a negative lookup. For example, let's say we have the following file tree:
In a very large tree, I want to exclude everything under
a/b
. I tried to filter them out by using a regular expression such as(?!b)
and(?!a/b)
, but it doesn't seem to filter out anything.Would it be possible to add support for negative lookahead/behind regular expressions?
The text was updated successfully, but these errors were encountered: