4 ms·
Nope, can't say I've needed to do any 2D pattern matching on the UNIX command line, ever. Sure back in age of dinosaurs when command line was being used for 2D
by snorkel 14y ago
Nope, can't say I've needed to do any 2D pattern matching on the UNIX command line, ever. Sure back in age of dinosaurs when command line was being used for 2D graphics this may have been useful, but ... we have actual GUI interfaces to do that now.
- icebraining 14y agoGraphics? What about just grepping over more than one line of code?
- sehugg 14y agoThere are plenty of reasons to do graphics on the command line (e.g. batch operations) and anyway that is not at all the main point of the paper, it's just an example.
- dwc 14y agoLook beyond the immediate, contrived example. Text can have meaningful structure beyond lines, which line-oriented tools handle poorly. So much power is available with UNIX command line tools, but often you must abandon them for python, ruby, or whatever. The proposed modest extension would allow the command line to be comfortably used for a larger problem space.
- quanticle 14y agoWhat about source code? Like Pike, I think that it's a little bit nonsensical that foo(shortArg1, shortarg2, shortArg3); is easy to find, but foo(longArg1, methodCall().stuff(), evenMoreComplicatedStuff); is much more difficult to grep for.
- duaneb 14y agoWhat are you talking about? Graphics have nothing to do with it.