I wrote a shell script which automatically set up environment
#!/bin/sh
set path=(/dv/project/ $path)
I change the execution bit by
chmod +x init.sh
When I run it as
./init.sh
It prompted me with error
./init.sh: line 3: syntax error near unexpected token `('
./init.sh: line 3: `set path=(/dv/project/ $path)'
What could be the problem here? Thanks!
If using of set isn't required, just try this:
#!/bin/bash
path=(/dv/project/ $path)
As I have noticed, you're trying to extend your $PATH environment variable, right? There is a better way. Try this approach:
# Extend $PATH without duplicates
function _extend_path() {
if ! $( echo "$PATH" | tr ":" "\n" | grep -qx "$1" ) ; then
PATH="$1:$PATH"
fi
}
# Add custom bin to $PATH
[ -d ~/.bin ] && _extend_path "$HOME/.bin"
_extend_path() { [[ $PATH =~ (^|:)"$1"(:|$) ]] || PATH+=":$1"; } -- one compound command, no subshells.path=( /dv/project/ $path ) is array syntax, which isn't valid with /bin/sh at all. Presumably you want #!/bin/bash?function keyword isn't part of the POSIX sh standard, so that's a portability bug too; in POSIX sh, it's just extend_path() { with no function preceding to define a function. While I'm usually fond of bash extensions (when used with a #!/bin/bash shebang), this one adds no value over the portable alternative.
set path=? What kind of syntax is that? What is it supposed to do? Where did you see documentation that made you think it's valid?setis a valid command, as I know. It's used for setting up an environment options.set -- path=foowould be valid (setting$1to"path=foo"), but that's not what was given.#!/bin/shmeans your shell is POSIX sh, which has no array support.