Timeline for How to split a single line of fields delimited by commas into multiple lines with a specific number of fields in each line?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2022 at 23:29 | comment | added | Kusalananda♦ | @DanieleGrassini Your original enquiry was about how someone could have downvoted this answer, not whether the code could run on some number of various systems. I know how to modify it to work (and be safe), so there's no need to convince me of anything. Note too that using --posix does not remove all non-POSIX features from GNU sed (EDIT: It does not remove behaviour that is explicitly left unspecified in the POSIX spec.) | |
| Jul 10, 2022 at 23:25 | comment | added | DanieleGrassini | @Kusalananda I think is well supported anyway. Work with GNU sed with --posix flags and with busybox sed. And if some implementations of sed does not support it, is just matters to add it in line a part i think. | |
| Jul 10, 2022 at 23:17 | comment | added | DanieleGrassini | @Kusalananda how we can speak about security implications with out knowing the full environnement? any of the other code coud be considered potentially dangerous in some circumstances. To mee, in regards to this question which dosnt state anything else that "How to split.." seem to be a good solutions. | |
| Jul 10, 2022 at 23:15 | comment | added | Kusalananda♦ | @DanieleGrassini Inserting a newline using \n in the replacement string of the s command. | |
| Jul 10, 2022 at 23:10 | comment | added | DanieleGrassini | @Kusalananda What isn't standard in this sed? | |
| Jul 5, 2022 at 11:48 | comment | added | Kusalananda♦ | @DanieleGrassini Assumes a particular non-standard implementation of sed, and contains a code injection vulnerability unless one assumes full control over the value in $m. | |
| Jul 3, 2022 at 16:11 | comment | added | DanieleGrassini | I can't explain to myself how someone could have downvotes this answer. It's really elegant. | |
| Jul 2, 2022 at 4:27 | review | Low quality posts | |||
| Jul 2, 2022 at 8:21 | |||||
| Jul 2, 2022 at 4:04 | history | answered | guest_7 | CC BY-SA 4.0 |