in reply to The problem with one-liners...

I throw away 98% of my oneliners, so I have never noticed this problem. Were this a concern, though, I'd have something like this in my .bashrc (may need minor fiddling before it actually works):
function ol { local NAME="$1" shift eval perl $(grep '^'"$1"'\>' ~/oneliners|cut '-d ' -f2-) "$@" }
accompanied by a file oneliners in my home looking like this (assuming some snippets from jmcnamara's collection):
col1 -naleshift@F;print"@F" rmcr -i -pes/\r// 2spc -pe$_.=$/
(Yes, the quotes are missing; this is due to the fact that the line is passed back out of the command substitution as a single string). And then I could just do something like
$ ol rmcr file1 file2 file

Makeshifts last the longest.

Replies are listed 'Best First'.
Re: Re: The problem with one-liners...
by t'mo (Pilgrim) on Feb 04, 2003 at 18:57 UTC

    Oh, I got that backwards. I thought you programmed your shell to save any commands beginning with 'perl' to a file named "oneliners".