3 ms·
You shouldn't parse the output of ls(1) (wooledge.org) 149 points by tosh on Dec 31, 2021 | past | 148 comments https://news.ycombinator.com/item?id=29747034 h
by 1vuio0pswjnm7 2y ago
You shouldn't parse the output of ls(1) (wooledge.org) 149 points by tosh on Dec 31, 2021 | past | 148 comments
https://news.ycombinator.com/item?id=29747034 https://news.ycombinator.com/item?id=29747034
Parsing the output of ls is an antipattern (wooledge.org) 2 points by goranmoomin on Sept 6, 2021 | past
https://news.ycombinator.com/item?id=28435532 https://news.ycombinator.com/item?id=28435532
Why you shouldn't parse the output of ls(1) (wooledge.org) 2 points by O1111OOO on Dec 24, 2018 | past | 2 comments
https://news.ycombinator.com/item?id=18753980 https://news.ycombinator.com/item?id=18753980
Parsing ls (wooledge.org) 3 points by tambourine_man on Jan 31, 2016 | past
https://news.ycombinator.com/item?id=11007601 https://news.ycombinator.com/item?id=11007601
Why you shouldn't parse the output of ls(1) (wooledge.org) 2 points by rosser on Jan 20, 2015 | past
https://news.ycombinator.com/item?id=8914841 https://news.ycombinator.com/item?id=8914841
Why you shouldn't parse the output of ls (wooledge.org) 31 points by dgellow on July 6, 2014 | past | 18 comments
https://news.ycombinator.com/item?id=7994720 https://news.ycombinator.com/item?id=7994720