That is absolutely true... Robert
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 04, 2005 10:23 AM > To: Hicks, Bob; 'R. S. van Keuren' > Cc: [email protected] > Subject: RE: Top posting > > For what it's worth, e-mail programs like MS Outlook make it difficult to > *not* top-post. > > For example, if one changes MS Outlook 2003's default setting to have the > > character in front of each line of the original e-mail message, MS Outlook > immediately displays a message warning that the setting will cause problems > with spell-checking. > > Using MS Outlook to post a message in the more acceptable manner can take a > significant amount of time, searching for and then changing MS Outlook's > default settings or manually reformatting the message. > > Richard > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Hicks, Bob > Sent: Tuesday, October 04, 2005 8:33 AM > To: R. S. van Keuren > Cc: [email protected] > Subject: RE: Top posting > > That is just a preference and most of usenet does not follow it. > > A: Yes, it is. > Q: Is top posting bad? > > YMMV > > Robert > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:activeperl- > > [EMAIL PROTECTED] On Behalf Of R. S. van Keuren > > Sent: Tuesday, October 04, 2005 9:03 AM > > Cc: [email protected] > > Subject: Top posting > > > > When a post starts to contain more than one previous message or pane, > top > > posting is much easier to follow than bottom posting. With bottom > posting, > > it's hard to find the most recent message. > > > > --Bob van Keuren > > San Diego > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of $Bill > > Luebkert > > Sent: Tuesday, October 04, 2005 1:42 AM > > To: Chris Cappelletti > > Cc: [email protected] > > Subject: [lists] Re: (no subject) > > > > > > Foo Ji-Haw wrote: > > > I think the tricky part is that spaces may appear within the "..." > field. > > In > > > which case the pattern may well be: > > > > > > /^"([^"]+)"\s+"([^"]+)"\s+"([^"]+)"\s+"([^"]+)"\s+"([^"]+)"\s+"([^"]+)"\ > s+"( > > > > [^"]+)"\s+"([^"]+)"\s+"([^"]+)"\s+"([^"]+)"\s+"([^"]+)"\s+"([^"]+)"\s+$/ > ) > > > > > > But I'm a rookie on regex, so this may not be optimal. > > > > You're a rookie on posting. Please don't top-post and trim the prior > posts. > > > > You can just adjust the split: > > > > foreach (@lines) { > > my @flds = split /"\s+"|^"|"$/; # remove "s - column0 will now > be > > empty > > if ($flds[6] eq 'pink' and $flds[8] eq 'blue') { > > print "found one: $_\n"; > > } > > } > > > > -- > > ,-/- __ _ _ $Bill Luebkert > Mailto:[EMAIL PROTECTED] > > (_/ / ) // // DBE Collectibles Mailto:[EMAIL PROTECTED] > > / ) /--< o // // Castle of Medieval Myth & Magic > > http://www.todbe.com/ > > -/-' /___/_<_</_</_ http://dbecoll.tripod.com/ (My Perl/Lakers > stuff) > > _______________________________________________ > > ActivePerl mailing list > > [email protected] > > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs > > > > > > > > > > _______________________________________________ > > ActivePerl mailing list > > [email protected] > > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs > > _______________________________________________ > ActivePerl mailing list > [email protected] > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
