Timeline for Handling long-options with getopts
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 30, 2021 at 14:15 | history | undeleted | terdon♦ | ||
| Dec 28, 2021 at 19:34 | history | deleted | CommunityBot | via Vote | |
| Nov 20, 2021 at 10:49 | history | undeleted | terdon♦ | ||
| Nov 19, 2021 at 6:19 | history | deleted | CommunityBot | via Vote | |
| Nov 17, 2021 at 12:51 | history | undeleted | terdon♦ | ||
| Nov 15, 2021 at 22:43 | history | deleted | CommunityBot | via Vote | |
| Nov 13, 2021 at 5:04 | history | edited | user313992 | CC BY-SA 4.0 | no point in being overly honest with this bunch of xxx xxx |
| Oct 31, 2021 at 16:41 | comment | added | Vera | What is the purpose of a leading : with getopt(1)? Why does it shut up error messages? | |
| Oct 31, 2021 at 12:42 | history | edited | user313992 | CC BY-SA 4.0 | END instead of START with : the arg taking options |
| Oct 31, 2021 at 12:13 | history | edited | user313992 | CC BY-SA 4.0 | fix %% and quotes |
| Oct 31, 2021 at 12:02 | comment | added | ilkkachu | Might want to use ${OPTARG%%=*} in the first one too (with double %%). The second one has something wrong with recognizing invalid options, e.g. --xyz comes up as xyzsilent (and --sil comes up as silsilent too). But you did say it wasn't properly debugged anyway. Might be easier to just drop support for abbreviated long options. | |
| Oct 31, 2021 at 11:34 | comment | added | Vera | Does getopt also take a leading colon? Could I check for : and ? with getopt as well? | |
| Oct 31, 2021 at 11:29 | history | answered | user313992 | CC BY-SA 4.0 |