[23429] in Perl-Users-Digest
Perl-Users Digest, Issue: 5646 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Oct 11 00:05:52 2003
Date: Fri, 10 Oct 2003 21: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 Fri, 10 Oct 2003 Volume: 10 Number: 5646
Today's topics:
Re: Conditional options to a regexp match? (Anno Siegel)
Re: Conditional options to a regexp match? <dwake.no.spam@alumni.stanford.org>
Re: Conditional options to a regexp match? <cenxnfu@rpr.nevmban.rqh>
Re: Conditional options to a regexp match? <krahnj@acm.org>
End Record Charcter <bruce.dobson@xtra.co.nz>
Re: every combination of letters chance@austin.rr.com
How to parse e-mail messages? <e02@removethis.toao.net>
Re: mod_perl / Apache problem (David)
Re: mod_perl / Apache problem <tore@aursand.no>
Old CGI scripts do not work under Mandrake 9.1 <cerih@exportlink.ch>
Re: Old CGI scripts do not work under Mandrake 9.1 <kalinaubears@iinet.net.au>
Re: regex for URL in a log file <abigail@abigail.nl>
Re: strip text up to a keyword? (Anno Siegel)
Re: Teach me how to fish, regexp <kuujinbo@hotmail.com>
Re: Teach me how to fish, regexp (Tad McClellan)
Re: Teach me how to fish, regexp (Tad McClellan)
Re: Teach me how to fish, regexp <henryn@zzzspacebbs.com>
Re: Teach me how to fish, regexp <henryn@zzzspacebbs.com>
Re: Teach me how to fish, regexp <kuujinbo@hotmail.com>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 10 Oct 2003 22:44:18 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Conditional options to a regexp match?
Message-Id: <bm7co2$l8a$2@mamenchi.zrz.TU-Berlin.DE>
Cognition Peon <cenxnfu@rpr.nevmban.rqh> wrote in comp.lang.perl.misc:
>
> 9:24pm, IP packets from John W. Krahn delivered:
>
> >
> > /(?@{[ $insensitive ? 'i' : '' ]}:($pattern))/;
> >
>
> Great solution. Thanks!! Never seen an example of
> (?imsx) regular expression extension before.
Look for the keyword "cloistered" in perlre for the whole story.
Anno
------------------------------
Date: 10 Oct 2003 15:43:07 -0700
From: David Wake <dwake.no.spam@alumni.stanford.org>
Subject: Re: Conditional options to a regexp match?
Message-Id: <9noewok938.fsf@Turing.Stanford.EDU>
"Michael P. Broida" <michael.p.broida@boeing_oops.com> writes:
>
> Something with "eval"?? Something like:
>
> $matchstatement = "\$x = m/(\$pattern)/"; # add escapes (\) as needed
> if ($insensitive) $matchstatement .= "i"; # append desired options
> if ($global) $matchstatement .= "g"; # ditto
> ...
> eval $matchstatement; # I don't know the "eval" syntax :)
>
> Don't know if that's "safe", but it seems like it
> oughta work. :)
>
> Mike
"eval" was what I needed. Thanks!
David
------------------------------
Date: Fri, 10 Oct 2003 16:28:50 -0700
From: Cognition Peon <cenxnfu@rpr.nevmban.rqh>
Subject: Re: Conditional options to a regexp match?
Message-Id: <Pine.GSO.4.50.0310101621540.28142-100000@shellfish.ece.arizona.edu>
10:44pm, IP packets from Anno Siegel delivered:
> Cognition Peon <cenxnfu@rpr.nevmban.rqh> wrote in comp.lang.perl.misc:
> >
> > 9:24pm, IP packets from John W. Krahn delivered:
> >
> > >
> > > /(?@{[ $insensitive ? 'i' : '' ]}:($pattern))/;
> > >
> >
> > Great solution. Thanks!! Never seen an example of
> > (?imsx) regular expression extension before.
>
> Look for the keyword "cloistered" in perlre for the whole story.
Now, I see the wonderful Monastery :-)
>
> Anno
>
--
echo cenxnfu@rpr.nevmban.rqh | perl -pe 'y/A-Za-z/N-ZA-Mn-za-m/'
The folowing statement is true. The previous statement is false.
------------------------------
Date: Sat, 11 Oct 2003 00:37:59 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: Conditional options to a regexp match?
Message-Id: <3F8750DC.D4789EB1@acm.org>
Cognition Peon wrote:
>
> 9:24pm, IP packets from John W. Krahn delivered:
> >
> > /(?@{[ $insensitive ? 'i' : '' ]}:($pattern))/;
>
> Great solution. Thanks!! Never seen an example of
> (?imsx) regular expression extension before.
Actually it is an example of the (?imsx:) extension. Using the (?imsx)
extension it would be:
/(?@{[ $insensitive ? 'i' : '' ]})($pattern)/;
:-)
John
--
use Perl;
program
fulfillment
------------------------------
Date: Sat, 11 Oct 2003 16:51:52 +1300
From: "Bruce.Dobson" <bruce.dobson@xtra.co.nz>
Subject: End Record Charcter
Message-Id: <c7Lhb.174627$JA5.4388673@news.xtra.co.nz>
I am trying to learn some Perl and doing a tutorial which has the following
code.
%grades = ();
print "Enter student names (press <cntrl>+D when done:";
@names = <STDIN>;
chomp @names;
print "\n\n";
print "Enter corresponding grades (press <cntrl>+D when done):";
@scores = <STDIN>;
@grades{@names} = @scores;
It refers to <cntrl>+D as the "end record character", but this does not seem
to work for me when I run the programme.
I installed ActivePerl-5.8.0.806-MSWin32-x86.msi on Windows XP.
Can anybody tell me why I cannot get <Cntrl>+D to work or what I use for the
end record character instead of <Cntrl>+D.
--
Bruce Dobson
8 Prescott Place,
Hamilton,
New Zealand.
Ph 064 7 856 8804 Fax 064 856 8845
Mobile 027 230 7509
------------------------------
Date: Fri, 10 Oct 2003 23:42:55 GMT
From: chance@austin.rr.com
Subject: Re: every combination of letters
Message-Id: <bm7hfr$dp2$1@localhost.localdomain>
roger <rogerroger457@hotmail.com> wrote:
> Hi Folks,
> I need to write two programs for a school assignment. One is an
> "efficient" anagram program that will find all anagrams for a given
> word by sorting all given letters of the supplied word and dictionary
> which will then find all of the matching words.
> The next version of the program (the "inefficient" example) is
> supposed to try every combination of letters and find anagrams by pure
> brute force by trying every combination of letters up to
> len($suppliedWord) in length.
> I'm not looking for someone to do this for me, I'm looking for advice
> on how do I go about trying every possible combination of letters. It
> sounds pretty easy on the surface but as I think about it more it
> seems to get messier and messier.
> Does soemone know of a "clean" method I can use to iterate through
> every possible combination of letters?
My shoot-from the hip advice:
1) write the inefficient code first. Then observe why its
inefficient and fix it.
2) for the permutation generation do it recursively. Thats just more fun:
a) if I'm being asked to give every permutation of a single
letter, just return that letter.
b) otw loop through the whole word a letter at a time,
concatenating the 'current letter' with all the permutations
of all the other letters.
--
I used to think government was a necessary evil.
I'm not so sure about the necessary part anymore.
------------------------------
Date: Sat, 11 Oct 2003 01:27:05 GMT
From: "Experienced but Undocumented" <e02@removethis.toao.net>
Subject: How to parse e-mail messages?
Message-Id: <J%Ihb.65435$pl3.62702@pd7tw3no>
Is there a PERL module that will parse raw e-mail messages? I'm using
Net::POP3 to download them off a server, but I would like to strip any HTML
or Rich Text and just leave plain text.
Thanks if anyone can offer suggestions.
------------------------------
Date: 10 Oct 2003 19:31:05 -0700
From: superman183@hotmail.com (David)
Subject: Re: mod_perl / Apache problem
Message-Id: <1d4e2ae4.0310101831.5dc5f691@posting.google.com>
Thanks to all ...
I ended up phyiscally moving the location of Registry.pm into one of
the paths that I knew it could see, but also needed to change
httpd.conf references to Apache::Registry to be ModPerl::Registry
Also, per the above comments, the startup file (on XP) under
/Apache/confs/ also needed to be amended too.
Anyway, tested it and it all works fine now... Thanks!
------------------------------
Date: Sat, 11 Oct 2003 05:18:17 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: mod_perl / Apache problem
Message-Id: <pan.2003.10.11.01.28.12.827436@aursand.no>
On Fri, 10 Oct 2003 14:56:23 -0700, David wrote:
>>> Hopefully this is being posted in the right place
>> I don't think so. This is related to the Apache web server, not Perl.
>> You should try one of the Apache newsgroups.
> Hmmm, one can't help thinking that mod_perl, and by association Apache,
> is in fact somehow related to Perl ... that is after all the whole point
> of mod_perl.
Irrelevant; The OP was specifically asking for help with configuring his
Apache web server (with mod_perl).
So. Let's see: Apache. Web server. mod_perl. Apache extension. Perl.
Programming language.
The only association I see is in the name 'mod_perl' and 'perl'.
--
Tore Aursand <tore@aursand.no>
------------------------------
Date: Sat, 11 Oct 2003 00:12:47 +0200
From: Ceri Hankey <cerih@exportlink.ch>
Subject: Old CGI scripts do not work under Mandrake 9.1
Message-Id: <3F872EDF.9020302@exportlink.ch>
Hi,
I have a few CGI scripts that worked fine under mandrake 8.1 and apache
1.3.?, but having UPGRADED (ie not a new installation) to Mandrake 9.1
and Apache 2.0, I keep on getting a 'file not found' error whwn I run
the scripts - in var/log/httpd/error22.log.
The CGI scripts appear to work fine when called via 'perl -d
scriptname', but fail when called via a Web page.
What has changed in Mandrake 9.1 vs 8.1? Is it Perl or Apache? and where?
regards,
Ceri Hankey
------------------------------
Date: Sat, 11 Oct 2003 12:53:39 +1000
From: Sisyphus <kalinaubears@iinet.net.au>
Subject: Re: Old CGI scripts do not work under Mandrake 9.1
Message-Id: <3f877166$0$23589$5a62ac22@freenews.iinet.net.au>
Ceri Hankey wrote:
> Hi,
>
> I have a few CGI scripts that worked fine under mandrake 8.1 and apache
> 1.3.?, but having UPGRADED (ie not a new installation) to Mandrake 9.1
> and Apache 2.0, I keep on getting a 'file not found' error whwn I run
> the scripts - in var/log/httpd/error22.log.
>
> The CGI scripts appear to work fine when called via 'perl -d
> scriptname', but fail when called via a Web page.
>
> What has changed in Mandrake 9.1 vs 8.1? Is it Perl or Apache? and where?
>
Don't kmow but it sounds to me like an Apache configuration issue.
You've got a new Apache in the upgrade - and I would think that the
configuration file (httpd.conf, iirc) has been overwritten, and needs
editing. I would start by checking that.
Which "file" is "not found" ? I assume it's the perl script.
Hth.
Cheers,
Rob
--
To reply by email u have to take out the u in kalinaubears.
------------------------------
Date: 11 Oct 2003 01:42:51 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: regex for URL in a log file
Message-Id: <slrnboeo0r.j9q.abigail@alexandra.abigail.nl>
Jaga (darthlover@yahoo.com) wrote on MMMDCLXXXIV September MCMXCIII in
<URL:news:blhu8p$891$1@newsmaster.cc.columbia.edu>:
() > hail all,
() > I am trying to write a regular expression to match a url in a text
() file.
What scheme, or schemes, do you want to match? There are URLs for dozens
of schemes. The Regexp::Common module has patterns for fax, file,
FTP, gopher, HTTP(S), news, NTTP, prospero, tel, telnet, tv and WAIS
URIs.
Abigail
--
perl -e '* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
/ / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / /
% % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % %;
BEGIN {% % = ($ _ = " " => print "Just Another Perl Hacker\n")}'
------------------------------
Date: 10 Oct 2003 22:39:03 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: strip text up to a keyword?
Message-Id: <bm7ce7$l8a$1@mamenchi.zrz.TU-Berlin.DE>
Tad McClellan <tadmc@augustmail.com> wrote in comp.lang.perl.misc:
> Anno Siegel <anno4000@lublin.zrz.tu-berlin.de> wrote:
> > Tad McClellan <tadmc@augustmail.com> wrote in comp.lang.perl.misc:
> >> kw <anon002001@yahoo.com> wrote:
> >>
> >> > Is there a relatively simple way to strip/delete all text from a file,
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> > up to a keyword?
> >>
> >>
> >> No.
> >
> > Well, there is, but the OP doesn't need it (because the text is in memory
> > anyway). This prints blocks from "BEGIN" to "END" from a file:
> >
> > while ( <DATA> ) {
> > print if s/.*(?=BEGIN)// .. s/(?<=END).*//;
> > }
>
>
> But that does not modify the file, as stated in the spec (which
> was my point: the spec was imprecise).
Aha. I didn't note your point, although your "No." was notably pointed.
> Add a line and change a line of your code, _then_ I'll be wrong. :-)
>
>
> $^I = ''; # no backup!
> while ( <> ) {
Okay, so the problem the "No." points out is the naive mind-set that takes
Perl's image of a file (an array of lines) for the reality of the file.
The usual editors reinforce the notion of a file as a sequence of lines
that can be changed at will, that's makes it so common.
In reality, changing things in the middle of a file is possible, but if
the length of the file changes, this requires a complete rewrite of at
least everything that follows the change. This, again, means that there
is a moment when part of the file is only in memory, not on disk. That
part could get lost in a crash, so the operation isn't safe.
It is easier and safer (those rarely go together) to write a modified
copy of the original file, and rename that to the original after the
deed. This is what editors do to give you the illusion, and it is what
Perl does with your code above.
Anno
PS: Of course, Tad knows everything I wrote about files. It's this Usenet
way of ostensibly talking to the one you're replying to, but really writing
for a wider audience, to whom it may concern.
------------------------------
Date: Sat, 11 Oct 2003 07:28:02 +0900
From: ko <kuujinbo@hotmail.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <bm7btg$ef$1@pin3.tky.plala.or.jp>
Henry wrote:
[snip]
> I would not want to argue personal preferences, not at all. My preference
> would be for html. As I'm working on MacOS X, apparently I'm out of luck.
Try here:
http://www.perldoc.com/
HTH - keith
------------------------------
Date: Fri, 10 Oct 2003 18:50:03 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Teach me how to fish, regexp
Message-Id: <slrnboehdb.6fl.tadmc@magna.augustmail.com>
Henry <henryn@zzzspacebbs.com> wrote:
> HelgiBriem_1@hotmail.com wrote on 10/9/03 3:53 AM:
[ talking about Perl's std docs ]
>>> but this isn't exactly the most friendly
>>> environment.
>>
>> What do you mean? Plain text, a pageful at a time, readily
>> searchable, isn't friendly enough for you?
> My preference
> would be for html. As I'm working on MacOS X, apparently I'm out of luck.
No you're not.
Type this:
perldoc pod2html
:-)
> Would you mind sharing a few bullet points about the keys to getting the
> most out of perldoc?
Never use it. (that isn't a joke)
I don't.
I use the std docs many times each day, but never through perldoc.
I only use perldoc as a shorthand for pointing others to the
relevant docs.
I prefer to use vi and grep to read the raw *.pod files.
Because it lets me do things that perldoc does not let me do.
Doing a word search of _all_ of the docs works sometimes, but most
often finds too many hits, so then I try searching other ways:
use an Initial Cap on the search term rather than all lower case,
headlines and the first word in a sentence might be most relevant.
Make an "index" file and grep in the index:
grep ^= perlfaq*.pod >faq.heads
grep ^= *.pod >all.heads
I also have defined an alias that launches my editor with
perlfunc already in it for looking up function arguments and such.
> From my few first tries, it seems very awkward.
> Maybe I'm doing something completely wrong, but I seem to need to do a
> vi-style ":q" just to get back to the shell at the end of a doc.
That is a feature of your pager program, not of perldoc.
perldoc perldoc
says how to set things up to use a different pager if you don't
like whatever the default is on your system.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 10 Oct 2003 18:55:58 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Teach me how to fish, regexp
Message-Id: <slrnboehoe.6fl.tadmc@magna.augustmail.com>
Henry <henryn@zzzspacebbs.com> wrote:
> (Jeez, yet another permutation on scoping rules to learn.)
And here is where you can do that:
"Coping with Scoping":
http://perl.plover.com/FAQs/Namespaces.html
>> The parentheses for function calls are generally optional,
>> unless it becomes ambiguous which function gets an argument.
>
> Wow, yet another variation on syntax requirements.
No, you have that backwards.
Yet another _lack_ of syntax requirements.
It lacks the requirement of always using parens.
It lacks the requirement of never using parens.
Perl is into freedom, you get to choose.
> I would just as soon
> have parens for function arguments required, but that probably shows I
> haven't used perl long enough.
I think you are right.
Perl isn't like "other programming languages".
Perl is not a Bondage And Discipline language like, say, Java or C++.
>>>> I recommend \d instead of [0-9]).
>>>
>>> OK, these are equivalent, though, right?
Right.
>>> Is this a matter of style,
>>> dialect, common usage, modernity, or what?
It is a matter of writing the easiest-to-read code.
(the corollary is you use whichever _you_ think is easiest to read,
more choice.
)
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 11 Oct 2003 01:16:59 GMT
From: Henry <henryn@zzzspacebbs.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <BBACA81C.15A76%henryn@zzzspacebbs.com>
Keith:
Thank you for your post on this thread:
in article bm7btg$ef$1@pin3.tky.plala.or.jp, ko at kuujinbo@hotmail.com
wrote on 10/10/03 3:28 PM:
> Henry wrote:
>
> [snip]
>> I would not want to argue personal preferences, not at all. My preference
>> would be for html. As I'm working on MacOS X, apparently I'm out of luck.
>
> Try here:
> http://www.perldoc.com/
Very cool-- one stop shopping. I can even select the version; MacOS is at
5.6 (might change in a couple of weeks with the release of 10.3).
Thanks,
Henry
henryn@zzzspacebbs.com remove 'zzz'
>
> HTH - keith
>
------------------------------
Date: Sat, 11 Oct 2003 01:44:53 GMT
From: Henry <henryn@zzzspacebbs.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <BBACAEA5.15A79%henryn@zzzspacebbs.com>
Tad:
Thanks for your posts on this thread:
#1
in article slrnboehdb.6fl.tadmc@magna.augustmail.com, Tad McClellan at
tadmc@augustmail.com wrote on 10/10/03 4:50 PM:
> Henry <henryn@zzzspacebbs.com> wrote:
>> HelgiBriem_1@hotmail.com wrote on 10/9/03 3:53 AM:
>
>
<snip>
>
> Type this:
>
> perldoc pod2html
>
> :-)
Jeez, is there no part of perl that doesn't have a secret door... behind
which is (of course) an additional secret door?
>
>
>> Would you mind sharing a few bullet points about the keys to getting the
>> most out of perldoc?
>
>
> Never use it. (that isn't a joke)
>
> I don't.
>
> I use the std docs many times each day, but never through perldoc.
>
> I only use perldoc as a shorthand for pointing others to the
> relevant docs.
>
> I prefer to use vi and grep to read the raw *.pod files.
I'm perfectly willing to use grep, but vi is pushing it. The last time I
used it for anything significant was over 20 years ago.
>
> Because it lets me do things that perldoc does not let me do.
I can see that.
>
> Doing a word search of _all_ of the docs works sometimes, but most
> often finds too many hits, so then I try searching other ways:
>
> use an Initial Cap on the search term rather than all lower case,
> headlines and the first word in a sentence might be most relevant.
Good suggestion!
>
> Make an "index" file and grep in the index:
>
> grep ^= perlfaq*.pod >faq.heads
>
> grep ^= *.pod >all.heads
>
> I also have defined an alias that launches my editor with
> perlfunc already in it for looking up function arguments and such.
I can see why you would do this. Ummm, would it be silly to ask why an
effective index isn't simply part of the doc package? Of course it would.
>
>
>> From my few first tries, it seems very awkward.
>> Maybe I'm doing something completely wrong, but I seem to need to do a
>> vi-style ":q" just to get back to the shell at the end of a doc.
>
>
> That is a feature of your pager program, not of perldoc.
>
> perldoc perldoc
>
> says how to set things up to use a different pager if you don't
> like whatever the default is on your system.
Hmmm, there's a mystery here that would lead me _way_ off topic. I'll work
it out.
>
#2
>> (Jeez, yet another permutation on scoping rules to learn.)
>
>
> And here is where you can do that:
>
> "Coping with Scoping":
>
> http://perl.plover.com/FAQs/Namespaces.html
>
Bookmarked! Excellent!
Hmmmm. I find the use of "my" as in
for (my $i=0; $i<100; $i++) {
... "to confine the scope of $i to the for loop." either brilliant or
appallingly chaotic, I'm not sure yet.
>
>>> The parentheses for function calls are generally optional,
>>> unless it becomes ambiguous which function gets an argument.
>>
>> Wow, yet another variation on syntax requirements.
>
> No, you have that backwards.
>
> Yet another _lack_ of syntax requirements.
>
> It lacks the requirement of always using parens.
>
> It lacks the requirement of never using parens.
>
> Perl is into freedom, you get to choose.
Philosophy, eh? (I'll note that "you get to choose" rhymes with "Nothing
left to lose". Ooop, never mind.)
OK, I'll choose to always use parens to enclose function call args.
>
>> I would just as soon have parens for function arguments required, but that
>> probably shows I haven't used perl long enough.
>
> I think you are right.
>
> Perl isn't like "other programming languages".
>
> Perl is not a Bondage And Discipline language like, say, Java or C++.
Jeez, I'm a pervert!
Robert Frost defined "freedom" as "moving easy in harness". I guess (oops)
that proves he was into B&D, too.
>
>
<snip>
>
>
> It is a matter of writing the easiest-to-read code.
>
> (the corollary is you use whichever _you_ think is easiest to read,
> more choice.
Well, yes, of course. I'll do that. But I would do it anyway, even with
some inherent restrictions on choice form the language itself.
Thanks,
Henry
henryn@zzzspacebbs.com remove 'zzz'
------------------------------
Date: Sat, 11 Oct 2003 10:18:28 +0900
From: ko <kuujinbo@hotmail.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <bm7lt3$c26$1@pin3.tky.plala.or.jp>
Tad McClellan wrote:
> Henry <henryn@zzzspacebbs.com> wrote:
[snip]
>>Would you mind sharing a few bullet points about the keys to getting the
>>most out of perldoc?
>
> Never use it. (that isn't a joke)
>
> I don't.
>
> I use the std docs many times each day, but never through perldoc.
>
> I only use perldoc as a shorthand for pointing others to the
> relevant docs.
>
> I prefer to use vi and grep to read the raw *.pod files.
>
> Because it lets me do things that perldoc does not let me do.
>
>
>
> Doing a word search of _all_ of the docs works sometimes, but most
> often finds too many hits, so then I try searching other ways:
>
> use an Initial Cap on the search term rather than all lower case,
> headlines and the first word in a sentence might be most relevant.
>
> Make an "index" file and grep in the index:
>
> grep ^= perlfaq*.pod >faq.heads
>
> grep ^= *.pod >all.heads
>
> I also have defined an alias that launches my editor with
> perlfunc already in it for looking up function arguments and such.
Nice example - thanks :)
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
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.
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 5646
***************************************
