215 reputation
211
bio website
location
age
visits member for 2 years, 3 months
seen 2 days ago

Jun
24
awarded  Notable Question
Jun
16
awarded  Caucus
May
1
awarded  Yearling
Dec
3
awarded  Popular Question
Oct
20
awarded  Popular Question
Jun
21
awarded  Popular Question
Oct
4
awarded  Self-Learner
Sep
21
awarded  Custodian
Jul
15
revised What does “Invalid argument” mean in Solaris?
added 27 characters in body
May
16
revised What does “Invalid argument” mean in Solaris?
edited tags
May
11
accepted Passing a bash command-line argument containing a dot
May
11
revised Passing a bash command-line argument containing a dot
added use-case
May
11
comment Passing a bash command-line argument containing a dot
let us continue this discussion in chat
May
11
comment Passing a bash command-line argument containing a dot
Okay, the code is in the question now! New to stackexchange :)
May
11
revised Passing a bash command-line argument containing a dot
code in script
May
11
reviewed Approve suggested edit on Passing a bash command-line argument containing a dot
May
11
comment Passing a bash command-line argument containing a dot
Here's my simple script from my original script: #!/bin/bash declare -a artifacts for i do artifacts[i]=$i echo ${artifacts[i]} done Execution1 -bash-3.00$ ./simple.sh arg1 arg2 arg3 arg1 arg2 arg3 Execution2 -bash-3.00$ ./simple.sh arg1.txt arg2.txt arg3.txt ./simple.sh: line 7: arg1.txt: syntax error in expression (error token is ".txt")
May
11
comment Passing a bash command-line argument containing a dot
@cjc @geekosaur Thanks for your comments, I tried a simple hello-world sort of script and it does accept arguments with a dot (.). I'll try moving the commands from my deploy.sh script to my hello-world script to see what's going wrong and repost.
May
11
asked Passing a bash command-line argument containing a dot
May
2
comment Where should a local executable be placed?
@uther, thanks for updating the answer!