Timeline for Why does bash need file descriptor duplicating?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23 at 9:49 | vote | accept | sylye | ||
| Oct 8 at 17:10 | comment | added | likewise | Regarding file descriptors and redirection, I've found this useful: mywiki.wooledge.org/BashGuide/InputAndOutput | |
| Oct 6 at 16:21 | history | became hot network question | |||
| Oct 6 at 12:02 | comment | added | ilkkachu | fds are just the file handles of Unix-land, not that special in the simple cases. Open a file, get an fd, read from/write to the fd, profit. It's the cases about multiple redirections that can screw heads. See e.g. this Q about the order of redirections, but there are others. | |
| Oct 6 at 11:51 | comment | added | ilkkachu | Yeah, the answer you linked to glossed over the details of what <&3 does under the hood. The point is that in effect the redirection has read read what there is available to be read from fd 3, though under the hood it's a bit messier. read -u 3 would be better. I tried to clarify that answer a bit. | |
| Oct 6 at 9:56 | history | edited | ilkkachu | CC BY-SA 4.0 | deleted 1 character in body |
| Oct 6 at 8:55 | history | edited | terdon♦ | CC BY-SA 4.0 | minor fixes to language and spelling |
| Oct 6 at 8:23 | answer | added | grawity | timeline score: 17 | |
| Oct 6 at 8:09 | history | asked | sylye | CC BY-SA 4.0 |