Awesome meditation. I have so many good ones that I don't even know where to start. Perhaps with the most pathological thing in my .bashrc?
alias ww='watch '\''ptyexec w | perl -pe '\''\'\'''\''(print(" -1 "),n
+ext) if $x++<2; ($i) = ($_ =~ /^.{42}\s+(\S+)/); $i=~/days/&&(print("
+ 9999999999 "),next); $i=~/(?:(\d+):)?([\d.]+)([md]?)/; ($t=$1*60+$2)
+; $3&&($t*=60); print sprintf(" %9d ",$t)'\''\'\'''\'' | sort -n | pe
+rl -pe '\''\'\'''\''s/^\s+\S+\s+//'\''\'\'''\'''\'''
where ptyexec is
this. (You can just drop the ptyexec, though, if it gives trouble, it'll just truncate the output width to 80 chars, which is a little ugly).
There's the ever-popular:
perl -pi -e 's/\r\n?/\n/' *
For fixing line-ends.
And another simple one that I love because of how it demonstrates a neat concept is just:
something | perl -lne 'END{print$x}$x+=$_'
(better known as "sum").
Update: added trailing slash to the line-end fixing regex. Thanks, tlm
------------
:Wq
Not an editor command: Wq
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.