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-) "$@"
}

[download]
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$_.=$/

[download]
(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.

In reply to Re: The problem with one-liners... by Aristotle
in thread The problem with one-liners... by John M. Dlugosz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.