Timeline for How to read the whole shell script before executing it?
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 3, 2024 at 18:31 | history | suggested | CommunityBot | CC BY-SA 4.0 | small style change |
| Dec 3, 2024 at 18:29 | review | Suggested edits | |||
| S Dec 3, 2024 at 18:31 | |||||
| Oct 10, 2023 at 5:40 | history | edited | VasyaNovikov | CC BY-SA 4.0 | simplify my answer |
| Jun 14, 2018 at 14:09 | history | edited | VasyaNovikov | CC BY-SA 4.0 | deleted 44 characters in body |
| May 1, 2018 at 9:03 | history | edited | VasyaNovikov | CC BY-SA 3.0 | deleted 257 characters in body |
| Feb 22, 2017 at 13:36 | history | edited | VasyaNovikov | CC BY-SA 3.0 | deleted 100 characters in body |
| Feb 22, 2017 at 13:11 | history | edited | VasyaNovikov | CC BY-SA 3.0 | deleted 6 characters in body |
| Dec 22, 2016 at 15:25 | history | edited | VasyaNovikov | CC BY-SA 3.0 | edited body |
| S Dec 22, 2016 at 11:19 | history | mod moved comments to chat | |||
| S Dec 22, 2016 at 11:19 | comment | added | terdon♦ | Comments are not for extended discussion; this conversation has been moved to chat. | |
| Dec 22, 2016 at 7:30 | history | edited | VasyaNovikov | CC BY-SA 3.0 | deleted 4 characters in body |
| Dec 21, 2016 at 21:15 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 | typos |
| Dec 21, 2016 at 18:25 | history | edited | VasyaNovikov | CC BY-SA 3.0 | added 25 characters in body |
| Dec 21, 2016 at 17:52 | history | edited | VasyaNovikov | CC BY-SA 3.0 | added 346 characters in body |
| Dec 21, 2016 at 15:47 | history | edited | VasyaNovikov | CC BY-SA 3.0 | added 36 characters in body |
| Dec 21, 2016 at 15:03 | history | edited | VasyaNovikov | CC BY-SA 3.0 | added 63 characters in body |
| Dec 21, 2016 at 14:52 | comment | added | Stéphane Chazelas | bug reported now, see also patch. | |
| Dec 21, 2016 at 14:39 | history | edited | VasyaNovikov | CC BY-SA 3.0 | added 145 characters in body |
| Dec 21, 2016 at 14:17 | comment | added | Stéphane Chazelas | What I found is that it doesn't see EOF and stop reading the file, but it gets tangled up in its "buffered stream" processing and ends up seeking past the end of the file, which is why it looks fine if the size of the file increases by not much, but looks bad when you make the file more than twice as big as before. I'll report a bug to the bash maintainers shortly. | |
| Dec 21, 2016 at 13:06 | history | edited | VasyaNovikov | CC BY-SA 3.0 | deleted 9 characters in body |
| Dec 21, 2016 at 11:49 | history | edited | VasyaNovikov | CC BY-SA 3.0 | added 1 character in body |
| Dec 21, 2016 at 11:32 | history | edited | VasyaNovikov | CC BY-SA 3.0 | added 2 characters in body |
| Dec 21, 2016 at 10:59 | history | edited | VasyaNovikov | CC BY-SA 3.0 | added 309 characters in body |
| Dec 21, 2016 at 10:39 | history | edited | VasyaNovikov | CC BY-SA 3.0 | edited body |
| Dec 21, 2016 at 10:33 | history | answered | VasyaNovikov | CC BY-SA 3.0 |