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

Postcss transformation fails with space in filepath in Windows #7571

Closed
jdclarke5 opened this issue Aug 19, 2020 · 3 comments
Closed

Postcss transformation fails with space in filepath in Windows #7571

jdclarke5 opened this issue Aug 19, 2020 · 3 comments

Comments

@jdclarke5
Copy link

jdclarke5 commented Aug 19, 2020

What version of Hugo are you using (hugo version)?

Hugo Static Site Generator v0.74.3/extended windows/amd64 BuildDate: unknown

Does this issue reproduce with the latest release?

Yes

Summary

When running hugo command in Windows within a working directory with a space (e.g. C:\Users\Jackson Clarke\...), the postcss transformation fails with the following error.

Error: Error building site: POSTCSS: failed to transform "scss/main.css" (text/css): 'C:\Users\Jackson' is not recognized as an internal or external command, operable program or batch file.

Obviously the space means that the path is being interpreted as separate command line arguments. The error would occur at the following line:

cmd := exec.Command(binary, cmdArgs...)

A potential fix would be to ensure such file paths are surround by double quotation marks.

Note: Running the hugo_extended_0.74.3_Windows-64bit.zip build.

@jmooring
Copy link
Member

Duplicate of #7333.

@stale
Copy link

stale bot commented Dec 19, 2020

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

@stale stale bot added the Stale label Dec 19, 2020
@stale stale bot removed the Stale label Mar 26, 2021
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants