bug: -p behaves weird

[wildeyes]

I'm on Windows 10.

tcm -p "**/*.css" -w doesn't see any path, doesn't watch, doesn't do anything.

tcm -p "client/**/*.css" -w works.

[wildeyes]

Perhaps switching from gaze to chokidar could fix this.

[ahstro]

+1 on weird behaviour. I couldn't get tcm -p website/**/*.m.css to work, but tcm --pattern "website/**/*.m.css" did. Not sure if it was -p vs --pattern or quotes vs no quotes, although I would assume the latter.

[wildeyes]

Windows?

On Thu, 18 May 2017, 11:09 Anton Strömkvist, [email protected] wrote:

+1 on weird behaviour. I couldn't get tcm -p website//*.m.css to work, but tcm --pattern "website//*.m.css" did. Not sure if it was -p vs --pattern or quotes vs no quotes, although I would assume the latter.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Quramy/typed-css-modules/issues/25#issuecomment-302332753, or mute the thread https://github.com/notifications/unsubscribe-auth/ABk1jCFZcHYbgo3gRkZh_fllM9is9VXhks5r6_zHgaJpZM4L71BL .

--

Sincerely, Daniel.

[ahstro]

Nope, zsh on macOS.

[wildeyes]

Does it work on bash? perhaps zsh was interpreting the ** before they hit tcm. a console.log in the right place could confirm this suspicion.

On Thu, May 18, 2017 at 11:23 AM, Anton Strömkvist <[email protected]

wrote:

Nope, zsh on macOS.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Quramy/typed-css-modules/issues/25#issuecomment-302335902, or mute the thread https://github.com/notifications/unsubscribe-auth/ABk1jAabULLXC1rTRF8pwZVQZH75AqeYks5r7AAfgaJpZM4L71BL .

[ahstro]

Still need the quotes around the glob for it to work.

[dahei]

I am on Windows 10 and it's not working with single quotes. When I use double quotes or no quotes it runs fine.