On 2021/06/29 15:20, [email protected] wrote:
"/tmp cd ~ >& /dev/zero"
cd ~>& is parsed correctly in more "intelligent" parsers.
"Violates POSIX on the parse level?!" Eek! Next
It does: >& is parsed as > & by POSIX rules, TTBOMK.
---
"What? WHAT?" Your abbreviation is violating my eyes on a parse level.
How am i supposed to know how to parse "TTBOMK"? :^)...ok, I can google it,
but doesn't it violate POSIX rules on TLA's, since it is obviously over
2x the length of a standard TLA! :-) Next you'll be telling me it wasn't
designed to be a TLA...
Besides, what does POSIX do by parsing >& as '> &'. Doesn't doing so simply
generate an error message that says the '~ > &' combo is meaningless?
Not issuing useless error messages is a first step in a good UI.
Languages, parsers or programs that essentially say: "I know what you
wanted, or
I know what you meant, but I'm going to make you wrong and ignore you
because users
need to be adapted to the computers. Um...*sigh*
