use Perl

• Excuse the nitpicking, I can't help it (Score:1)

  by Aristotle (5147)

  The following bit still irks me :)

  s/.*<(.*@.*)>.*/$1/;

  It's one of the things that constantly annoys me, like a pebble in the shoe, when I write sed scripts. What I believe it really should phrased as is

  $_ = $1 if /<(.*@.*)>/;
  • Re:Excuse the nitpicking, I can't help it (Score:2)

    by brian_d_foy (44)

    "Should" is strong phrasing. If that's the way you like to do things in sed, that's fine, but around these parts there is more than one way to do it.
    
    But this is open source, so if you decide to use the script, you can change it to anything that you like. :)
    • Re:Excuse the nitpicking, I can't help it (Score:1)

      by Aristotle (5147)

      What I'm saying is that I can't do it this way in sed, so I'm forced to repeat myself: "find anything followed by the bit I want followed by anything and replace it by the bit I want". At times, I've pined for a crop() function (in sed more so than in Perl, of course, but the Perl verbiage can get old as well).
• Ready-cooked software (Score:2)

  by Simon (89)

  I use a program called the "little brother database" (lbdb in Debian) to handle this for me.
• 'Pine' Piping (Score:1)

  by Smylers (2592)

  To get round 'Pine' only remembering one pipe command, and forgetting that when you quit, you can use its print functionality instead.

  The definition of a printer in 'Pine' can just be a command to pipe stuff to; obviously you're supposed to put commands like lpr in there, but there's no reason why you can't set up anything else as a printer.

  When I was a 'Pine' user I had gvim as my default printer.

  Smylers
  • Re:'Pine' Piping (Score:2)

    by brian_d_foy (44)

    Ah, very cool indeed. Thanks :)
    
    I never thought of that because my PINE machine does not have a printer that I can use, so I never bothered to look into that.