Timeline for Processing optional arguments with getopts in bash
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 11, 2020 at 1:27 | answer | added | Jayr Magave | timeline score: 0 | |
| Oct 29, 2020 at 15:14 | vote | accept | 220284 | ||
| Oct 29, 2020 at 15:07 | comment | added | 220284 |
@Stéphane-Chazelas Hm, I don't care really (it's for my personal use only). It should just complain (and more importantly, do nothing) if I write something like sh script.sh -a arg1 or sh script.sh -a arg1 -b arg2.
|
|
| Oct 29, 2020 at 15:05 | answer | added | Stéphane Chazelas | timeline score: 1 | |
| Oct 29, 2020 at 15:02 | comment | added | Stéphane Chazelas |
And what should happen if the script is called as script.sh -i file1 -i file2 file3 file4?
|
|
| Oct 29, 2020 at 14:52 | history | asked | 220284 | CC BY-SA 4.0 |