3 ms·
The old behaviour is the sane default, at least for editing text files. POSIX defines a text file as a file consisting of a number of lines, each terminated by
by nemetroid 8y ago
The old behaviour is the sane default, at least for editing text files. POSIX defines a text file as a file consisting of a number of lines, each terminated by an LF character.
- coldtea 8y agosane is what the user expects, not what POSIX demands.
- lexicality 8y agoOne could reasonably expect that a user expects a POSIX system to behave according to the POSIX standards?
- williamdclt 8y agoNot really, most users (even tech people) don't know that it is a POSIX standard, or what's a POSIX standard, or what's POSIX really
- lexicality 8y agoAre you thinking about most people who use a computer or most people who use a CLI based editor that's presumably on a remote machine they just sshed into?
- coldtea 8y agoI'd say both sets. Hardly any of my colleagues knows what POSIX is (and surely not in any depth, even those that do), but they still SSH and use editors that include Vim all the time... I'd say in a company of 50+ SSHing people, around 5-6 know POSIX and its history, and usually the older ones (35+).
- unveres 8y agoI think it's better to expect more from a specialist than less. ;)
- coldtea 8y agoA sysadmin maybe. A user hardly. Especially a 2019 user, 20+ years removed from the systems, decisions, and rationales, behind POSIX. Just try to get someone (even a seasoned Linux user) to use a POSIX-only userland (as opposed to GNU), as see how fast they'll be pulling their hair out...
- unveres 8y agoI would say it's not just a POSIX demand. Most unix tools are POSIX-complaint, and the user should expect just it and nothing more. Non-proper text files without LF at the end may not be processed properly, so to be assured that everything works fine that LF is mandatory.