Re:Why you shouldn't parse the output of ls(1)
by TeMPOraL on Sunday June 16, 2024 @03:36AM
(#40695352)
`ls` is faster and more portable in Unix-land, fallback to emulation on non-Unix platforms is easier than asking users to install a port of half of Unix just to have `ls`, and user customization points are what Emacs is made of and for in the first place.
Re:Why you shouldn't parse the output of ls(1)
by oefrha on Sunday June 16, 2024 @04:13AM
(#40695507)
Shelling out to `ls` (exec + opendir + readdir + stat) is not faster than opendir + readdir + stat. `ls --dired` is definitely not portable. readdir and stat (the libc functions) are portable, works across POSIX and other Unix-likes.
Re:Why you shouldn't parse the output of ls(1)
by hprotagonist on Sunday June 16, 2024 @03:39AM
(#40695366)
dired predates emacs, and was originally itself a standalone tool.
Re:Why you shouldn't parse the output of ls(1)
by oefrha on Sunday June 16, 2024 @04:14AM
(#40695513)
Sure, but the dired mode of Emacs has been first party forever, and nobody thought to improve it?
Re:Why you shouldn't parse the output of ls(1)
by mickeyp on Sunday June 16, 2024 @04:57AM
(#40695673)
It's not unbelievable if you know and use Emacs and dired.
dired will use `ls' if it is available. You can also control the arguments passed to `ls' if you want to customize sort order and suchlike. You cannot trivially do this if it's hardcoded as syscalls.
Emacs's buffer concept specifically works around the idea of annotating the output of common coreutils commands and annotating them so they are interactive in Emacs. That means you can combine `find' + `ls' and show a collated list of files matching the things you want. That is very powerful.
Oh, and you can swap out `find' or `ls' with anything that emits a similar format (or customize Emacs to interpret it differently).
Now your readdir, stat, etc. equivalents require significant development effort.
- shelling out to an unreliable program and doing all the parsing work;
- adding a special mode for yourself to another piece of software, which may or may not be present;
- adding a user customization point;
- adding an emulation of said software when it's not present;
when you are in a real programming language, and all you need to get the clean data directly is readdir(3) and stat(3) (or their Windows equivalents)? This is unbelievable.