-
Notifications
You must be signed in to change notification settings - Fork 110
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
documentup pattern documentation is incorrect #247
Comments
|
If I can help tell me where the sources for documentup are, I can send a PR. |
Thanks — the doc is generated from README.md in the root directory. |
I have a similar issue where I would like to use the pattern including a slash: I also can't figure out how to workaround the slash-parsing issue by using awk expressions – better parse errors would be very useful here! |
@sjakobi this should work, I think:
The logic is that you have to enclose the pattern in As for the original issue, it seems like documentup is no longer updated from the README source, so there's probably nothing we can do here. I don't think we link to documentup anywhere, so just ignore it. |
@feuerbach Thank you! This works if I use the test executable directly. It was |
according to do https://documentup.com/feuerbach/tasty#patterns
should match, but yield a "Could not parse pattern". I guess this is due to #38 .
The new pattern should be
-p '$0 == test && $1 ~ /^foo/
.Is there a simple way to match only 01-09 of
test A case
whereideal would be something along the lines of
/test A* 0[1-9]/
right now I have a workaround to
$3 ~ /A/ && $3 ~ / 0/
.The text was updated successfully, but these errors were encountered: