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

Constraints on @Unparsed #1

Open
kribblo opened this issue Nov 14, 2011 · 3 comments
Open

Constraints on @Unparsed #1

kribblo opened this issue Nov 14, 2011 · 3 comments
Assignees
Milestone

Comments

@kribblo
Copy link

kribblo commented Nov 14, 2011

Would be nice if it was possible to set some constraints on the result from @unparsed, such as "count=1" or "count > 0", maybe some more advanced things like patterns.

Thanks!

@davelnewton
Copy link

Agreed; being able to enforce the presence of things like a list of files would be nice.

@ghost ghost assigned lexicalscope Nov 21, 2011
@lexicalscope
Copy link
Owner

In the latest version you should be able to specify patterns on @unparsed

@lexicalscope
Copy link
Owner

need to also add support for this to the help messages

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