[25946] in Perl-Users-Digest
Perl-Users Digest, Issue: 8165 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Jun 11 18:05:42 2005
Date: Sat, 11 Jun 2005 15:05:06 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sat, 11 Jun 2005 Volume: 10 Number: 8165
Today's topics:
Re: chown recursively <nobull@mail.com>
Re: chown recursively <no@email.com>
Re: how to format a $htmlpage without form feed <Oliver-Bleckmann@freenet.de>
Re: how to format a $htmlpage without form feed <flavell@ph.gla.ac.uk>
Re: how to format a $htmlpage without form feed <tadmc@augustmail.com>
Re: increase performance <usenet@vyznev.invalid>
Mail::DomainKeys example needed <news@LearnQuick.com>
Mail::DomainKeys example needed <news@LearnQuick.com>
Re: Posting Guidelines for comp.lang.perl.misc ($Revisi <ebohlman@omsdev.com>
Re: Posting Guidelines for comp.lang.perl.misc ($Revisi <tadmc@augustmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 11 Jun 2005 10:34:15 +0100
From: Brian McCauley <nobull@mail.com>
Subject: Re: chown recursively
Message-Id: <d8eb6o$aac$1@redhat2.bham.ac.uk>
Abigail wrote:
> Of course, the strongest argument is: programmer time is more important
> than CPU time. The time to program out
>
> system "chown -R $uid:$gid $dir";
>
> utterly dwarves the overhead of starting another process. (And note that
> unless '$uid', '$gid' and '$dir' contain characters that are special to
> shell, no shell will be started by perl - perl will call chown directly).
But even the briefest consideration of the question of whether or not
$dir may contain shell meta character takes more programmer time than
typing the extra punctuation to avoid this being an issue.
system 'chown','-R',"$uid:$gid",$dir;
------------------------------
Date: Sat, 11 Jun 2005 11:59:02 +0100
From: Brian Wakem <no@email.com>
Subject: Re: chown recursively
Message-Id: <3gvuflFekopuU1@individual.net>
Tim O'Donovan wrote:
> I've yet to find a way to use the sleep() function to sleep for
> less than a second
>
> Tim
use Time::HiRes qw(sleep);
sleep(0.2);
--
Brian Wakem
------------------------------
Date: Sat, 11 Jun 2005 08:11:52 +0200
From: "Oliver Bleckmann" <Oliver-Bleckmann@freenet.de>
Subject: Re: how to format a $htmlpage without form feed
Message-Id: <d8dvic$pl8$1@newsserver.rz.tu-ilmenau.de>
damn, that's what i started with - was in the original code paster from tv
parser, another very old project - and now
it works! I must have been too tired yesterday, thanks.
"Gunnar Hjalmarsson" <noreply@gunnar.cc> schrieb im Newsbeitrag
news:3gus09Feas97U1@individual.net...
> Oliver Bleckmann wrote:
>> it would be nice - just for reading - to break a line after every
>> closed tag - that means after a ">".
>
> <snip>
>
>> use LWP::Simple;
>> $URL="http://de.finance.yahoo.com/q/cq?s=710000&m=a";
>> $inh = get($URL);
>
> $inh =~ s/>/>\n/g;
>
> --
> Gunnar Hjalmarsson
> Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Sat, 11 Jun 2005 12:06:58 +0100
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: how to format a $htmlpage without form feed
Message-Id: <Pine.LNX.4.62.0506111151260.6710@ppepc56.ph.gla.ac.uk>
On Sat, 11 Jun 2005, Oliver Bleckmann blurted out atop a quote:
> ok guys,
> i see that you don't understand what i mean.
I see that you haven't yet positioned yourself to make effective use
of Usenet.
> for i am german, my english isn't the best.
In meine Erfahrung, erwarten die .de-Gruppen *auch* (koennete sagen
"noch strenger"), dass man die usenet-Regeln ("Netiquette") einhaelt.
http://www.kirchwitz.de/~amk/dni/einleitung und de.newusers.infos
koennte helfen.
Anyway, the key to solving a complex problem (and, based on what
you're posting, this appears to represent a complex problem for you)
is to identify the parts of the problem, and solve each of them *in
their proper place*. If you're having problems with the HTML that
you're generating from a Perl script, then the right place to solve
that is a forum where HTML is on topic, not a Perl programming group.
The only real Perl problem relevance that I've noticed so far in your
posting to this thread is the meaning of \n, which you got wrong at
first and then seem to have reacted inappropriately when it was
pointed out to you. The killfile awaits.
------------------------------
Date: Sat, 11 Jun 2005 00:46:30 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: how to format a $htmlpage without form feed
Message-Id: <slrndakulm.b96.tadmc@magna.augustmail.com>
Oliver Bleckmann <Oliver-Bleckmann@freenet.de> wrote:
> if ( $inh3 = s/"\>"/"\>\n"/sgoi)
You are requiring a 3-character substring:
double quote
closing angle bracket
double quote
If your angle brackets don't have quote characters, then the
pattern will not match.
If the pattern does not match then s/// does not do anything.
You need to write a pattern that will match rather than fail,
take out the double quotes.
And the backslashes, angle brackets are not special in regexes
nor in strings.
And the s///s option, it does not do anything when there is no
dot (.) in your pattern.
And the s///o option, it does not do anything when there is no
variable part in your pattern.
And the s///i option, it does not do anything when there are no
letters in your pattern.
Do not throw options onto the end willy nilly.
Use the ones you need, don't use the ones you don't need.
To do that, you will need to understand what each does, see the docs.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 11 Jun 2005 13:58:52 +0300
From: Ilmari Karonen <usenet@vyznev.invalid>
Subject: Re: increase performance
Message-Id: <slrndalgvc.2mj.usenet@boojum.home.vyznev.net>
Rodrick Brown <rodrick.brown@gmail.com> kirjoitti 09.06.2005:
> Hello all I have a script that processes the following data I could possibly
> speed it up
>
> 0107
> 0205
> 0304
> 0405
> 0105
> 0805
>
> the script just converts the output to
>
> Jan07
> feb05
> mar03
> apr05
I'd do that with a one-liner:
perl -pe 's/\d\d/(qw(jan feb mar apr may jun jul aug sep oct nov dec))[$&-1]/e' date.txt
--
Ilmari Karonen
To reply by e-mail, please replace ".invalid" with ".net" in address.
------------------------------
Date: Sat, 11 Jun 2005 08:16:34 GMT
From: "Herb Martin" <news@LearnQuick.com>
Subject: Mail::DomainKeys example needed
Message-Id: <C5xqe.39510$j51.28943@tornado.texas.rr.com>
I am seeking a Mail::DomainKeys example for signing
a mail message.
I have the CPAN project loaded and have not been able
to find any documentation (no pod in files, not html but
I may have missed it on this unfamiliar system where I
am working) in the files nor by searching the Internet.
Something simple that will show me how to load my
cert/private key, specify my DNS location for the public
key, input and sign an RFC822 SMTP message file (or
thereabouts.)
I suspect this is trivial once you have the package and
maybe it's just late (at night) but right now trying to
reverse engineer the code isn't working for me.
Odd thing is the sample CERN implementation in C# also
comes with no "sample" (that I can find.
Thanks for helping if you can...
--
Herb Martin
Accelerated MCSE
http://www.LearnQuick.Com
------------------------------
Date: Sat, 11 Jun 2005 08:26:36 GMT
From: "Herb Martin" <news@LearnQuick.com>
Subject: Mail::DomainKeys example needed
Message-Id: <0fxqe.39511$j51.3527@tornado.texas.rr.com>
I am seeking a Mail::DomainKeys example for signing
a mail message.
http://killa.net/infosec/Mail-DomainKeys/
I have the CPAN project loaded and have not been able
to find any documentation (no pod in files, not html but
I may have missed it on this unfamiliar system where I
am working) in the files nor by searching the Internet.
Something simple that will show me how to load my
cert/private key, specify my DNS location for the public
key, input and sign an RFC822 SMTP message file (or
thereabouts.)
I suspect this is trivial once you have the package and
maybe it's just late (at night) but right now trying to
reverse engineer the code isn't working for me.
Odd thing is the sample CERN implementation in C# also
comes with no "sample" (that I can find.)
Thanks for helping if you can...
--
Herb Martin
Accelerated MCSE
http://www.LearnQuick.Com
------------------------------
Date: 11 Jun 2005 10:22:59 GMT
From: Eric Bohlman <ebohlman@omsdev.com>
Subject: Re: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <Xns9672384C31345ebohlmanomsdevcom@130.133.1.4>
tadmc@augustmail.com wrote in
news:42a8cf8e$0$14572$8b463f8a@news.nationwide.net:
> Use an effective followup style
> When composing a followup, quote only enough text to establish
> the context for the comments that you will add. Always
> indicate who wrote the quoted material. Never quote an entire
> article. Never quote a .signature (unless that is what you are
> commenting on).
>
> Intersperse your comments *following* each section of quoted
> text to which they relate. Unappreciated followup styles are
> referred to as "top-posting", "Jeopardy" (because the answer
> comes before the question), or "TOFU" (Text Over, Fullquote
> Under).
>
> Reversing the chronology of the dialog makes it much harder to
> understand (some folks won't even read it if written in that
> style). For more information on quoting style, see:
>
> http://web.presby.edu/~nnqadmin/nnq/nquote.html
I think it's time to gather up and refine/summarize the advice a number
of people have been giving to Google Groups posters and include it here.
------------------------------
Date: Sat, 11 Jun 2005 09:30:59 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <slrndaltd3.coj.tadmc@magna.augustmail.com>
Eric Bohlman <ebohlman@omsdev.com> wrote:
> tadmc@augustmail.com wrote in
> news:42a8cf8e$0$14572$8b463f8a@news.nationwide.net:
>
>> Use an effective followup style
>> When composing a followup, quote only enough text to establish
>> the context for the comments that you will add. Always
>> indicate who wrote the quoted material. Never quote an entire
>> article. Never quote a .signature (unless that is what you are
>> commenting on).
>>
>> Intersperse your comments *following* each section of quoted
>> text to which they relate. Unappreciated followup styles are
>> referred to as "top-posting", "Jeopardy" (because the answer
>> comes before the question), or "TOFU" (Text Over, Fullquote
>> Under).
>>
>> Reversing the chronology of the dialog makes it much harder to
>> understand (some folks won't even read it if written in that
>> style). For more information on quoting style, see:
>>
>> http://web.presby.edu/~nnqadmin/nnq/nquote.html
>
> I think it's time to gather up and refine/summarize the advice a number
> of people have been giving to Google Groups posters and include it here.
I agree, but I don't know when I can get to having time to
participate in a discussion.
I will be news-less while out of town next week[1], followed by a few
days of dealing with a week's backlog of stuff that happened while
I was gone...
I'll start a thread soliciting wording in a couple of weeks.
In the meantime, it would be really great if someone would like to
start making a "first cut" of what should be said and how it should
be said, so we'll be ready to hit the ground running. :-)
[1] Unless I deign to actually using Google Groups for posting
(not likely, I'd end up having killfiled myself).
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 8165
***************************************
