--As off Friday, November 28, 2003 1:08 PM -0800, R. Joseph Newton is
alleged to have said:
s[\][]gsi
Cool! Thanks, Daniel, that is very nice work. I could feel myself
going back over those first steps in using regexes as I followed
your post.
--As for the rest, it is mine.
Heh, thanks. I'm
On Nov 28, 2003, at 8:54 PM, Jason Dusek wrote:
Hi Everyone,
On Friday, November 28, 2003, at 08:51 PM, drieux wrote:
a. how did you initialize it to begin with
and why not simple re-use that solution
The hash consists of filenames, line numbers and strings.
$HASH{$file}{$line} = line
Hi Everyone,
I guess drieux was write about perldoc -f 'delete' - it completely
solved my problem. So as an act of penance to the Perl community, I
will flagellate myself right here on this list!
for (1..108) {
print 'wap';
print 'ouch';
}
That'll teach me to write to the list
Hi Everyone,
On Friday, November 28, 2003, at 08:51 PM, drieux wrote:
a. how did you initialize it to begin with
and why not simple re-use that solution
The hash consists of filenames, line numbers and strings.
$HASH{$file}{$line} = line of code from some file.
So the script goes along
On Nov 28, 2003, at 4:09 PM, John W. Krahn wrote:
[..]
"Advanced Programming in the UNIX Environment" by W. Richard Stevens
[..]
I should note that, as myFascistHousemate just whined at moi,
that we need to make sure that we are clear about the
distinctions between
unix philosophy
On Nov 28, 2003, at 6:26 PM, Jason Dusek wrote:
Let's say I have a hash of hashes. And I want to use it over
and over again, so I need to reinitialize it often.
There are two issues here,
a. how did you initialize it to begin with
and why not simple re-use that solution
b. have you looke
Jason Dusek wrote:
>
> Hi Perl Beginners,
Hello,
> Let's say I have a hash of hashes. And I want to use it over and over
> again, so I need to reinitialize it often. I suppose I could go
> through each key in the hash of hashes, and go through each key in the
> little hashes and use delete on
Hi Perl Beginners,
Let's say I have a hash of hashes. And I want to use it over and over
again, so I need to reinitialize it often. I suppose I could go
through each key in the hash of hashes, and go through each key in the
little hashes and use delete on each of them. But isn't there some
Mark Weisman wrote:
I've got several BSD boxes running in my organization, and I'd like to
make a singular interface into them for viewing the logs. That's all I
want to do, I don't want to give permissions to the users of this
interface to do anything else, just review the logs. I've got my script
On Saturday, Nov 29, 2003, at 15:10 US/Pacific, Saskia van der Elst
wrote:
Rob said:
I would love to know of a description of the Unix
/philosophy/. Once sucked in to the surrounding ideas
everything seems obvious, but I know of no book that
explains stuff like processes, forking, signals and
so
Rob Dixon wrote:
>
> Paul Kraus wrote:
> >
> > I need to beef up on my UNIX skills.
>
> I would love to know of a description of the Unix
> /philosophy/.
"The UNIX Philosophy" by Mike Gancarz
"Linux and the Unix Philosophy" by Mike Gancarz
"The UNIX Programming Environment" by Brian W. Kernigh
I've got several BSD boxes running in my organization, and I'd like to
make a singular interface into them for viewing the logs. That's all I
want to do, I don't want to give permissions to the users of this
interface to do anything else, just review the logs. I've got my scripts
working fine on my
check out the O'Reilly Unix Bookshelf, you get a "in a nutshell" hard copy
and 6 books in HTML on a cd. Makes a really great quick reference. I have
the Perl and Linux/Webserver bookshelves as well. You can carry ~18 books
around with you in your laptop case!
-Tom Kinzer
714.404.9362
-Orig
Rob said:
> I would love to know of a description of the Unix
> /philosophy/. Once sucked in to the surrounding ideas
> everything seems obvious, but I know of no book that
> explains stuff like processes, forking, signals and
> so on that underly the basic ideas of Unix.
>
> In essence it is a mu
Paul Kraus wrote:
>
> I need to beef up on my UNIX skills.
I would love to know of a description of the Unix
/philosophy/. Once sucked in to the surrounding ideas
everything seems obvious, but I know of no book that
explains stuff like processes, forking, signals and
so on that underly the basic i
Rob Dixon wrote:
> Joseph wrote:
> >
> > Just remember that the enclosing double-quotes are always a part
> > of Windows long filenames. When the the sytem processes the
> > string expression offered as an argument, it takes only the
> > textual content, and strips the quuotes. Enclose the whole
Paul Kraus wrote:
I need to beef up on my UNIX skills. Are major server is running Sco
Open server.
Will this book benefit me or is there another I should look at.
Not on topic and I apologize but beyond perl the list seems to have many
UNIX enthusiasts.
I would echo the comments about the "Essent
Daniel Staal wrote:
...
> You definitely need the s/// operator, (unless you can use one of the
> HTML parsing modules). But let's fix that regrexp first, shall we?
>
> First off, you may have noticed I removed the first '.*' from your
> regrexp: that's because nothing is allowed between the open
On Friday, Nov 28, 2003, at 11:01 US/Pacific, Paul Kraus wrote:
[..]
I need to beef up on my UNIX skills. Are major server is running Sco
Open server.
Will this book benefit me or is there another I should look at.
[..]
as a general over-view it is a reasonable work.
The question of course is 'whi
On Thursday, Nov 27, 2003, at 17:49 US/Pacific, John W. Krahn wrote:
Philipp Traeder wrote:
[..]
If I am not mistaken, this is more or less exactly what I am doing
right
now - the only problem I have got with this is that the user is
interrupted in his work when the 'long_action' finishes - like t
I'm sorry, small correction. The Unix CD Bookshelf does not contain
"Essential System Administration".
It has:
Unix Power Tools, 3rd Edition
Learning the Unix Operating System, 5th Edition
Learning the vi Editor, 6th Edition
Mac OS X for Unix Geeks
Learning the Korn Shell, 2nd Edition
sed &
Philipp Traeder wrote:
Hi Phillip,
Sorry. That last example cheated with a long, hard-coded wait. Below is
something that speaks a little more closely to the problem.
...
> b) How can I set up the ReadLine() part in a way that the user is able
> to type new actions, but can receive new message
Philipp Traeder wrote:
>
...
> b) How can I set up the ReadLine() part in a way that the user is able
> to type new actions, but can receive new messages (from finished long
> actions) as well? I have played around with Term::ReadKey, and ended up
> with something like this:
Are you looking for
Sorry to hear you're running SCO. My sincerest sympathies.
As for Unix books, the O'Reilly "Unix in a Nutshell" is a good book.
I don't consider it quite as indispensible as "Essential System
Administration",
but that book assumes you're a little more fluent in Unix.
So if you're a user on the
I need to beef up on my UNIX skills. Are major server is running Sco
Open server.
Will this book benefit me or is there another I should look at.
Not on topic and I apologize but beyond perl the list seems to have many
UNIX enthusiasts.
Paul
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
"R. Joseph Newton" <[EMAIL PROTECTED]> wrote:
> Try this:
>
>
>
>
> Joseph's first Perl-based form
>
>
>
>
> Name
> Rank
> Serial Number
>
>
>
>
> Then use CGI to get the parameters.
>
> perldoc CGI
I got a '405 error', resource not available. I guess I'll just have to
switc
Marcus Claesson wrote:
>
> I settled for the simplest of them all, by single quoting the shell
> variables:
>
> > perl -wne 'if (/'$FILENAME'/) { s/\d{4}-\d{2}-\d{2}/'$UPDATED'/;print;
> > }' updated_files.txt
Actually, you are single quoting the perl program. The shell variables
are outside th
John wrote:
>
> tr/// does not use regular expressions, only m// and s/// and split()
> use regular expressions.
Hi John.
Are you sure of that? I've just answered a private question
about use of $_ from a guy who was insecure about its use.
I said that the only places it was /altered/ was in 'for
Thanks for all your answers!
I settled for the simplest of them all, by single quoting the shell
variables:
> perl -wne 'if (/'$FILENAME'/) { s/\d{4}-\d{2}-\d{2}/'$UPDATED'/;print;
> }' updated_files.txt
The reason I use bash here and not only good old perl is that the bash
script is much bigger
Joseph wrote:
>
> Just remember that the enclosing double-quotes are always a part
> of Windows long filenames. When the the sytem processes the
> string expression offered as an argument, it takes only the
> textual content, and strips the quuotes. Enclose the whole
> string, including double-qu
[EMAIL PROTECTED] wrote:
> I have sendmail working ok with perl by calling sendmail (qmail-inject).
> However, now I need to send an attachment with it. Can someone tell me how
> this can be done?
>
> fw
Is that the Mail::Sendmail module, or shelling out to an external sendmail
utility? If its t
Jerry Rocteur wrote:
> In as much as perldoc is your friend (Just like Google ;-) I find when
> you first use perldoc you get awfully confused as to which one to look
> for.
>
> I like to use perldoc perltoc and of course
> http://www.perldoc.com/perl5.8.0/pod/perltoc.html is the bees knees..
>
>
"Wagner, David --- Senior Programmer Analyst --- WGO" wrote:
> Boris Shor wrote:
> > And when I rename the directory to "House 98" (space instead of
> > underscore), the following does not:
> >
> > @filelist = glob("w:/stleg/Colorado/House 98/*.htm");
> I tried a number of things and was n
Paul Kraus wrote:
> Someone want to show me how this module can help parse out html?
>
> I want to grap text between text being able to apple regexp to
> get what I want.
>
> The problem is my text is among 10,000 td tags. With the only difference
> being what the above tag has in it.
>
> So if t
34 matches
Mail list logo
