Timeline for Automating textual input from a bash script without using EOF
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2014 at 1:11 | comment | added | Gilles 'SO- stop being evil' | @unexpected62 I don't understand what you're asking. You should probably ask a new question on this site. Be sure to give enough context. | |
| Mar 8, 2014 at 1:03 | comment | added | boltup_im_coding | How can you sleep in between commands read from the script? | |
| Jul 8, 2012 at 18:53 | history | edited | Gilles 'SO- stop being evil' | CC BY-SA 3.0 | note that EOF is just the traditional marker, not a keyword |
| Jul 8, 2012 at 16:51 | comment | added | killermist | Using here-documents like this, I have often changed the ending marker to something much more meaningful (and less likely to be "randomly" matched), like END_OF_WHATEVER_FUNCTION. Sometimes, trying to "save" space/size is actually a waste of effort because it causes ambiguity as to what is actually happening. | |
| Jul 8, 2012 at 13:53 | comment | added | cas | that bolded EOF should be <underscore><underscore>EOF<underscore><underscore> | |
| Jul 8, 2012 at 13:24 | comment | added | cas | in other words, EOF in this context means an end-of-file marker, not the actual end of the script file. the text "EOF" is any arbitrary text - whatever you use immediately after the << characters will indicate the end of the here-now document. I typically use EOF because it stands out and is very unlikely to be inside the herenow document if, e.g., i'm programatically-generating the shell script (which i do quite often). | |
| Jul 7, 2012 at 23:09 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 3.0 |