Timeline for bash script: incorrect argument value being set
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2018 at 20:52 | vote | accept | dot | ||
| Feb 14, 2018 at 20:48 | comment | added | Jeff Schaller♦ | No problem; glad to hear you got to the bottom of it! | |
| Feb 14, 2018 at 20:46 | comment | added | dot | gotcha. trying to accept your answer but looks like i have to wait a few minutes. | |
| Feb 14, 2018 at 20:45 | comment | added | Jeff Schaller♦ | If you run env, you'll see a list of variables that have already been set and are exported/visible to child processes. Using any of those names is risky. | |
| Feb 14, 2018 at 20:43 | comment | added | dot | Being a noobie with bash - I didn't quite understand your explanation of the variable being exported from my environment. But I did substitute with a lowercase variable name and the problem went away. I will change all my vars to be lower case. THanks. | |
| Feb 14, 2018 at 20:39 | history | answered | Jeff Schaller♦ | CC BY-SA 3.0 |