-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search: Optionally require symbols to be adjacent (low priority) #57
Comments
This functionality is available on dev. To mark symbols as adjacent add a modifier before the pattern As you pointed out, the feature of re-adding flexibility requires much more efforts to implement. So, I am currently not planning to implement it. |
Awesome! Let me know when that's in a released version, and I'll update the doc to match. My primary desire now is #77 (full unification) but obviously that's a subtle algorithm that is much harder :-). |
Sure. I am going to release what currently is in the dev version after some testing. I also created a CHANGELOG.md, so it should be easier to track changes now.
Yeah, I remember that issue :) |
Hi David, this feature is released in version 25. |
|
Thank you! |
Search is easy to use, but it's hard to be specific because it allows 0+ symbols between each symbol.
It'd be nice to have an option (irrelevant in regex) to require that "symbols must be adjacent". If enabled, the pattern specifies a sequence of symbols that must be adjacent (though they could be inside a matching statement). Obviously this is only useful once the search pattern can search on variables (since otherwise there are few useful working patterns).
As a bonus you might add symbols that re-add flexibility. E.g.,
$$
for one symbol,$+
for 1 or more unspecified symbols, and$*
for 0 or more symbols. But that could be done later or never. I'm not sure what the right specifiers should be in this case, and that extra flexibility would require backtracking (or using a DFA which would be complete overkill in this case).The text was updated successfully, but these errors were encountered: