-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
Having &
in Directory name causing problems.
#1551
Comments
I've encountered this same issue but with a different special character (parentheses!), and I think I've got a minimal reproduction: # Taskfile.yml
version: '3'
vars:
FILE_BASENAME: 'Filename with (parens) & other special chars'
tasks:
gen:
generates:
- '{{.FILE_BASENAME}}.txt'
cmds:
- echo foo > '{{.FILE_BASENAME}}.in'
default:
deps: [gen]
sources:
- '{{.FILE_BASENAME}}.in'
generates:
- '{{.FILE_BASENAME}}.txt'
cmds:
- cp '{{.FILE_BASENAME}}.in' '{{.FILE_BASENAME}}.txt' As-is, I get: $ task
task: [gen] echo foo > 'Filename with (parens) & other special chars.in'
1:51: ( is not a valid word However with the Taskfile.yml (updated)# Taskfile.yml
version: '3'
vars:
FILE_BASENAME: 'Filename with (parens) & other special chars'
tasks:
gen:
generates:
- '{{.FILE_BASENAME}}.txt'
cmds:
- echo foo > '{{.FILE_BASENAME}}.in'
default:
deps: [gen]
#sources:
#- '{{.FILE_BASENAME}}.in'
#generates:
#- '{{.FILE_BASENAME}}.txt'
cmds:
- cp '{{.FILE_BASENAME}}.in' '{{.FILE_BASENAME}}.txt' the task seems to work fine: $ task
task: [gen] echo foo > 'Filename with (parens) & other special chars.in'
task: [default] cp 'Filename with (parens) & other special chars.in' 'Filename with (parens) & other special chars.txt' Interestingly... this error only seems to happen when both |
&
in Directory name causign problems.&
in Directory name causing problems.
Awesome!!! Thanks @andreynering! When do you think #1584 will be able to be released? I have an active project that uses lots of special characters right now. 😅 |
Running task in watch mode with next configuration
Causes it to fail with proximatly next message
So having "&" in folder is a problem...
related - #1069
The text was updated successfully, but these errors were encountered: