<SNIP> > See the man pages for ``xargs'' for information on ways to deal > with huge numbers of arguments. As an example to find all the > files containing some pattern this will work on most *ix boxes: > find . -type f -print | xargs grep -l pattern
Sorry to say, Bill, but I'm a GUI snob. It may be faster to have a console open and type that in, but it would be just as fast to have a GUI search tool open. And that says nothing for the results your piped command returns. With a well constructed GUI tool results can be displayed in a wide array of types. Take Evolution as an example. KFM is another. Even 'mc', the consummate console-based file management tool, groks the need for good GUI layout despite the fact that its text based. The same goes for 'links'. A lot of times its about the usability and not the format. 'mc' and 'links' are two text-based tools that draw a lot from the GUI side of things. Even though they are still text-based they are still very useful because they display information in a clear and concise manner. That and the tools are always either immediately available or damn near (I don't like the fact that you can't make the menu bar "sticky" in 'links'). I generally think that there is a disconnect between the CLI and GUI factions that doesn't really understand what the other is and what it can do. Both have their places. Just look at MacOS X! What a gorgeous meld of CLI and GUI all in one package. Everything to everyone (at least when there's enough software out for it :). Conundrum; why do GUI proponents use :-) and CLI proponents use <G>. My rule is to use smileys when I don't have to be serious. CLI type expressions are more serious. Tyler PS: Let the fur fly <G> -- PDA HandyMan www.pdahandyman.com "Giving the Mobile User What They Really Want!" _______________________________________________ Linux-users mailing list - http://linux.nf/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
