Timeline for UNIX command to add comma and space
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 17, 2023 at 8:43 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 |
added 2 characters in body
|
| Dec 17, 2023 at 8:42 | comment | added | Stéphane Chazelas | @CharlesDuffy, see the first item: Create a subshell to prevent the x variable from leaking out | |
| Dec 16, 2023 at 22:07 | comment | added | Charles Duffy |
I'm curious: Why the parens to create a subshell? Is the purpose just to scope the variable x so it doesn't remain in memory after the command is complete?
|
|
| Dec 16, 2023 at 16:14 | comment | added | Stéphane Chazelas |
In those shells, you can also do x=$(<IP).
|
|
| Dec 16, 2023 at 16:13 | comment | added | Stéphane Chazelas |
The builtin echo or bash and ksh can also expand backslash-escapes (as POSIX requires!) depending on how those shells were built or invoked or the environment. You may also have problems if the first line starts with a -. See Why is printf better than echo? for details.
|
|
| S Dec 16, 2023 at 7:58 | review | First answers | |||
| Dec 16, 2023 at 21:18 | |||||
| S Dec 16, 2023 at 7:58 | history | edited | dave_thompson_085 | CC BY-SA 4.0 |
make description more exact
|
| S Dec 15, 2023 at 23:05 | review | First answers | |||
| Dec 16, 2023 at 1:11 | |||||
| S Dec 15, 2023 at 23:05 | history | answered | sfink | CC BY-SA 4.0 |