Strings work fine, the problem is the (single) quotes:
~ $ foo="echo 'hello world'"
~ $ for x in $foo; do echo $x; done
echo
'hello
world'
~ $ $foo
'hello world'
~ $ eval "$foo"
hello world
The splitting is by whitespace, so the single quotes remain in the arguments. Using eval (and double quotes to preven splitting), it gets processed correctly. That said, don’t use eval; use functions or aliases instead.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@beehaw.org
All things programming and coding related. Subcommunity of Technology.
It might be because it’s a single string, and might work if you store it or expand it as an array. I think it would in Zsh, anyway.
But the response to use a function instead is probably wiser.
Strings work fine, the problem is the (single) quotes:
The splitting is by whitespace, so the single quotes remain in the arguments. Using eval (and double quotes to preven splitting), it gets processed correctly. That said, don’t use eval; use functions or aliases instead.
Yep, the function did the trick. My guess is it was being misread at execution as a variable and thats why it was breaking