Interesting exercise... Frankly I'm impressed (I was guessing closer to a hundred):
[me@host]$ grep -rish '\b\(shit\|\(mother\)*fuck\|damn\|crap|hell\b\|a
+sshole\)' *
# the damn sign wrong!!! So we have to flip them all.
# currently, it's just too damn messy to try to make ProcessKi
+ckaction
print "\n\n\n\nHOLY SHIT, THERE ARE COLS THAT NEED TO BE SCRAMBLED T
+HAT WEREN'T: \n\n $missed_cols\n\nBETTER CHECK THAT OUT LEST YOU WIND
+ UP IN JAIL\n";
[me@host]$ find -type f | wc -l
5033
[me@host]$ find -type f -exec cat {} \; | wc -l
1102070
[me@host]$
Of course, a more humorous (and more illustrative of our team culture) grep is this:
[me@host]$ grep -rish '\bhack' * | wc -l
241
[me@host]$
------------
:Wq
Not an editor command: Wq
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.