Skip to content
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

Closed
epsilonhalbe opened this issue Mar 19, 2019 · 6 comments
Closed

documentup pattern documentation is incorrect #247

epsilonhalbe opened this issue Mar 19, 2019 · 6 comments

Comments

@epsilonhalbe
Copy link

epsilonhalbe commented Mar 19, 2019

according to do https://documentup.com/feuerbach/tasty#patterns

-p test/foo*

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 where

testgroup.subgroup.test A case 01
 ...
testgroup.subgroup.test A case  20
testgroup.subgroup.test B case  01
 ...
testgroup.subgroup.test B case 20

ideal would be something along the lines of /test A* 0[1-9]/
right now I have a workaround to $3 ~ /A/ && $3 ~ / 0/.

@UnkindPartition
Copy link
Owner

  1. Thanks, will fix.
  2. No, globs or regexes are not supported at the moment unfortunately.

@epsilonhalbe
Copy link
Author

epsilonhalbe commented Mar 20, 2019

If I can help tell me where the sources for documentup are, I can send a PR.

@UnkindPartition
Copy link
Owner

Thanks — the doc is generated from README.md in the root directory.

@sjakobi
Copy link
Contributor

sjakobi commented Sep 18, 2019

I have a similar issue where I would like to use the pattern including a slash: type-inference/failure.

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!

@UnkindPartition
Copy link
Owner

@sjakobi this should work, I think:

-p '/type-inference\/failure/'

The logic is that you have to enclose the pattern in /.../ since it contains special characters, and then you need to escape the / in the standard way to avoid it being treated as the pattern delimiter.

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.

@sjakobi
Copy link
Contributor

sjakobi commented Sep 19, 2019

@feuerbach Thank you! This works if I use the test executable directly. It was cabal that mangled my --test-options: haskell/cabal#6248.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants