Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Never write it in 'C' if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible.
--Taylor's Laws of Programming
Which I think should be updated to:
Quote:
Never write it in 'C' if 'Perl' is enough;
Never drag out 'Perl' if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible.
--Taylor's Laws of Programming, revised
Quote:
If Larry Wall knew how to use awk, he never would have written Perl.
-- WFS
Joke
Quote:
Originally Posted by Tinkster
<BEG>
shouldn't that be "<beg />" -- XHTML standards, you know.
Serious
Quote:
Originally Posted by yitzle
Neat! Thanks!
I didn't even know you could search man (or less, I guess) like that!
Shows why I regularly re-read the man pages for the basics: less, grep, cat, etc. , etc. , etc.
BTW, did you know that you can put "#<name_of_command>" as a URL directly into Konqueror's Address/Location dialog box & get the man page in HTML format?
Never write it in 'C' if 'Perl' is enough;
Never drag out 'Perl' if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible.
--Taylor's Laws of Programming, revised
Heh. Words of wisdom. ;}
Quote:
If you find yourself using cat with only one argument
you're abusing it.
Glad you like my revision. I have been looking for the right words to capture flavor of the original, this time I think I either got it or came very close. At least close enough to make it public.
Of course then there are Python & Ruby to work in or combine into a high-level scripting class w/ Perl. . . .
It's been 21 months, but I just realized the humor in this:
Quote:
Originally Posted by Tinkster
Quote:
If you find yourself using cat with only one argument
you're abusing it.
Cheers,
Tink
Let me explain:
Sometimes for clarity I like to break a long pipeline up & put each "joint" of "pipe" on a separate line. This allows the reader to follow the logic step by step. When I do this, I frequently cat the target file into the pipeline, rather than making it the object of the 1st "real" command.
Since this involves using cat w/ only one argument, does this make me a cat abuser?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.