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

File Patterns in CLI: They Work (?) #197

Open
bdkjones opened this issue Mar 22, 2018 · 1 comment
Open

File Patterns in CLI: They Work (?) #197

bdkjones opened this issue Mar 22, 2018 · 1 comment

Comments

@bdkjones
Copy link

The very bottom of the readme says: "file patterns do not currently work in the CLI".

That appears to be untrue, however. Enclosing the wildcard path in single quotes causes Bash to use the literal character value of *. In the command below, I'm running from the Terminal on macOS 10.13.3 in the media_queries folder that ships with purify-css as a test:

purify-css media_queries.css '*.html' -o out.css

From what I can tell, this runs correctly and out.css is indeed missing some CSS.

Question:

Is there another reason you don't officially support wildcards in the CLI besides the escaping required for asterisks in Bash? In short, if I rely on this approach, am I going to hit some weird bugs I'm not aware of?

@Illyism
Copy link
Contributor

Illyism commented Mar 26, 2018

No, this will not affect your results.

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

2 participants