On Fri, 23 Jun 2000, SoloCDM wrote:
> Charles Galpin wrote:
> >
> > why don't you remind us what you are trying to accomplish, and send us a
> > snippet of a file (this must be attached or we will lose the funny eol
> > chars) that you mention below. That or send us a few lines of
> > the output from
> >
> > od -c your_funny_file
> >
> > charles
> >
> > On Fri, 23 Jun 2000, SoloCDM wrote:
> >
> > > I successfully used "cat <file> | tr -d '\n'" on a file that "sed
> > > 's/\n//g' <file>" failed to properly recognize. I need sed to
> > > effectively recognize newlines or ask that someone provide a perl
> > > script that will.
>
> In a message processed with a .procmailrc recipe, I search for two
> lines by devising separate character strings (e.g. xxxxxxx, xxxxxx)
> with wild cards (e.g. ., *) amongst the character strings and a return
> in the middle that connects the two character strings, then remove the
> intended lines with the return found in the message.
again, without a snippet i cannot do better than tell you this is easily
done. I'm not in the mood for pulling teeth this morning, so please send a
snippet. Offline if you are worried about the contnets or some nonsense.
> If any of you are willing, I need to have it written for processing a
> message in a recipe *and* processing a file and string. I wonder if a
> .pl file will cover all three?
of course! all the procmail script is doing is reading from stdin, which
any perl script can do as a filter. As for a string you can just cat and
pipe it to the perl script.
sorry to sound irritated, but I am :)
charles
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
