3 ms·
Wouldn't that fall over for common usages of the shell (presuming it acts like sed)? Suppose you have an executable "queue". you'd generally run it as ./qu
by ISL 6y ago
Wouldn't that fall over for common usages of the shell (presuming it acts like sed)?
Suppose you have an executable "queue".
you'd generally run it as
./queue
With this rule, wouldn't that be parsed as
./q'e'e
?
- kbenson 6y agoIt's the idea, rather than the implementation, which I'm advocating for. For a shell, it would likely be best to trigger with a reserved character (or two) that's much less likely to be encountered in normal usage.
- ISL 6y agoUnderstood. Finding a reserved character (or even sequence) that doesn't have collisions or unintended behavior beyond what the semi-reserved ' and " can do will be hard (but not necessarily impossible :)! ).
- a1369209993 6y agoIn addition to what kbenson said, word characters [a-zA-Z0-9] usually aren't eligible as quotes anyway, otherwise how would qq'this has a q in it' parse (versus q/'this has a /).