Timeline for Tokenize string from $REPLY in bash script
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 31, 2014 at 0:59 | vote | accept | arch-abit | ||
| Aug 31, 2014 at 0:58 | history | edited | arch-abit | CC BY-SA 3.0 |
Final results to this post
|
| Aug 23, 2014 at 9:28 | history | edited | arch-abit | CC BY-SA 3.0 |
added 22 characters in body
|
| Aug 23, 2014 at 8:30 | history | edited | arch-abit | CC BY-SA 3.0 |
added 2798 characters in body
|
| Aug 22, 2014 at 18:55 | answer | added | mikeserv | timeline score: 5 | |
| Aug 22, 2014 at 18:51 | comment | added | arch-abit | @mikeserv - Yes, thanks, any suggestions, the more ways the better :) I still have more to add to this project, so flexibility is good. | |
| Aug 22, 2014 at 18:49 | comment | added | mikeserv | Oh cool. Then it's easy. Yeah - you can just IFS. It can be switched around or whatever - I'm doing an answer if that's ok. | |
| Aug 22, 2014 at 18:48 | comment | added | arch-abit | I realize this is more of a design issue for now, but I add: as far as delimiters go the data being created is probably going to be audited for the selected delimiter of the chosen character set, and it is going to have a representable substitute when it is used inside the data. | |
| Aug 22, 2014 at 18:27 | comment | added | arch-abit | @mikeserv - The majority of the data does not yet exists, so I can use anything. Even when exporting from another DBS the structure too, may be changed. edit I guess what I mean is the delimiters do not yet exists, so there is no chance of not being safe. | |
| Aug 22, 2014 at 18:06 | comment | added | mikeserv | are the comma delimiters safe? like - is there a chance of them occurring within the quoted strings? | |
| Aug 22, 2014 at 17:50 | review | First posts | |||
| Aug 22, 2014 at 17:51 | |||||
| Aug 22, 2014 at 17:46 | history | asked | arch-abit | CC BY-SA 3.0 |