Hi Mike,
On Thu, 8 Aug 2019 15:40:42 +0100
Mike Martin via beginners wrote:
> Is it possible to have the output of a perl module piped to open (open3 in
> my case), so I can use a file handle contains the output passed to sysread
>
> Odd question I know
>
you can use https://e
Is it possible to have the output of a perl module piped to open (open3 in
my case), so I can use a file handle contains the output passed to sysread
Odd question I know
Thanks
Can you please answer this question?
http://stackoverflow.com/questions/28857025/perl-open-output-file-in-same-endianess-as-input-file-utf-16be-vs-utf-16le
When Perl opens an UTF-16 encoded file,
open my $in, "< :encoding(UTF-16)", "text-utf16le.txt" or die "Erro
the list form:
>>
>> my @cmd = qw(ls /);
>>
>> open my $ch, '-|', @cmd
>> or die "Can't open <<@cmd>>: $!";
>>
>> (Untested!).
>
> Ok, not so hard to do I guess. But why is this important?
#1 is explained by
Shlomi Fish writes:
Accidentally left out of my previous resonse.
> In addition to what Ken said:
>
>> cat tst:
>>
>> #!/usr/local/bin/perl
>>
>> use strict;
>> use warnings;
>>
>> my $cmd = 'ls /';
>>
>> open m
Ken Slater writes:
(Note: somehow a post about like below didn't make it to the list when
my other response did... this is paraphrasing)
>> cat tst:
>>
>> #!/usr/local/bin/perl
>>
>> use strict;
>> use warnings;
>>
>> my $cmd = 'ls /
On Mon, Nov 3, 2014 at 9:57 AM, Harry Putnam wrote:
> Ken Slater writes:
that attribution is wrong. Ken didn't say this, Shlomi did.
>> It is a good idea to avoid using $_ in production code:
This is an opinion. I think it's ... I hesitate to use the word
"controversial", but it's not uni
Ken Slater writes:
>
> It is a good idea to avoid using $_ in production code:
>
> http://perl-begin.org/tutorials/bad-elements/#overuse_dollar_underscore
>
> So write it as:
>
> while (my $l = <$ch>) {
> print $l;
> }
Again, easy enough to do. and no doubt it would be good.
But why is
usr/local/bin/perl
>
> use strict;
> use warnings;
>
> my $cmd = 'ls /';
>
> open my $ch, '-|', "$cmd" or die "Can't open $cmd: $!";
>
1. No need to wrap «$cmd» in double quotes here:
http://perl-begin.org/tutorials/bad
> cat tst:
>
> #!/usr/local/bin/perl
>
> use strict;
> use warnings;
>
> my $cmd = 'ls /';
>
> open my $ch, '-|', "$cmd" or die "Can't open $cmd: $!";
>
> while ($ch) {
> print;
> }
I believe y
ide... but changing it does the same thing.
What is wrong with this example:
cat tst:
#!/usr/local/bin/perl
use strict;
use warnings;
my $cmd = 'ls /';
open my $ch, '-|', "$cmd" or die "Can't open $cmd: $!";
while ($ch) {
print;
}
--
To
g forked. and you can't do both ways
as that would likely cause hanging with blocking i/o.
and if you want finer control, then use IPC::Open[23]
This is far from definitive, as there is no way of intuiting whether `-`
refers to the Perl program's STDIO or to the child process's.
ways
as that would likely cause hanging with blocking i/o.
and if you want finer control, then use IPC::Open[23]
uri
--
Uri Guttman - The Perl Hunter
The Best Perl Jobs, The Best Perl Hackers
http://PerlHunter.com
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional comma
ve written scripts involving sending mail with sendmail from perl.
Or capturing the output of rsync etc.
I used a piped open like this:
open my $ch, '|-', "$sendm" or die
"Can't open $sendm: $!";
while (<$sch>){
print $ch bleh;
efully and you would get a reasoned response.
I think I would go with `>|` and `|>` though, which allows for `>|>` if
there is ever a real read/write open mode.
Rob
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com
Kenneth Wolcott writes:
> On Fri, May 9, 2014 at 1:41 PM, Harry Putnam wrote:
>> I guess I need a mnemonic device to trick myself into remembering
>> which way the pipe with dash symbol goes.
>
> Think of it as "producer" and "consumer". You could use your file
> handle variable to remind yours
On Fri, May 9, 2014 at 1:41 PM, Harry Putnam wrote:
> I guess I need a mnemonic device to trick myself into remembering
> which way the pipe with dash symbol goes.
Think of it as "producer" and "consumer". You could use your file
handle variable to remind yourself instead of using just "$ch".
H
On Fri, 09 May 2014 16:41:02 -0400
Harry Putnam wrote:
> As soon as I think I've got it right by thinking:
>
> ok, left side is into the command
> right side is out.
>
> If I start pondering over that ... it begins to seem it is the other
> way.
>
> Gack I'm sick of it.
Agreed. I w
dmail from perl.
Or capturing the output of rsync etc.
I used a piped open like this:
open my $ch, '|-', "$sendm" or die
"Can't open $sendm: $!";
while (<$sch>){
print $ch bleh;
print $ch blah;
}
Or perhaps it w
On Nov 19, 2013, at 8:40 AM, Jim Gibson wrote:
> That’s all the analysis I have time for.
I really appreciate the analysis. It gives me a lot to go on.
Thanks,
Frank
On Nov 19, 2013, at 3:17 AM, John W. Krahn wrote:
> readdir() returns just the file names, without the path.
Thanks, John. I didn't realize that. This morning, I found
http://perldoc.perl.org/functions/readdir.html and read the following:
"If you're planning to filetest the return valu
On Nov 18, 2013, at 2:02 PM, SSC_perl wrote:
>> Surf.pm:65: $cookie =~ Encode($cookie);
>> Surf.pm:66: $value =~ Encode($value);
>> Did you really mean to use the return value from Encode() as a regular
>> expression?
>
>
> Unfortunately, I can't answer this, as
s no value.
I also ran perl -c, as well as PerlCritic, on all the files and
have uploaded a "cleaned up" version (1.5.1) to our site. Here's a
direct link:
http://www.surfshopcart.com/download-zip.php
I started looking through it and found this mistake. In the old versi
On Nov 18, 2013, at 2:02 PM, SSC_perl wrote:
> Hi John,
>
> Thanks for getting back to me with your findings. I really appreciate
> it. I've gone through everything, made the changes that I could, and I have
> some questions to some of your remarks.
You should be responding to the lis
Hi John,
Thanks for getting back to me with your findings. I really appreciate
it. I've gone through everything, made the changes that I could, and I have
some questions to some of your remarks.
> You are using the value from readdir() without prepending the path to the
> file name.
SSC_perl wrote:
Hello,
Hello,
This is a one-time post to announce that the SurfShopPRO Perl
shopping cart system is going open source. Our site hasn't been fully
updated yet, but you can download the cart and check it our for
yourself. We are looking for developers, desi
Hello,
This is a one-time post to announce that the SurfShopPRO Perl shopping
cart system is going open source. Our site hasn't been fully updated yet, but
you can download the cart and check it our for yourself. We are looking for
developers, designers, and testers.
> Dear All,
>
> I am having an XLSX file in server and my OS in Win7. The first open
> statement is working fine in which we have give the actual file name.
>
> 2nd open function is not working where we have given the file name as
> variable.
>
> Please help in resolv
On May 7, 2013, at 1:48 AM, Ganesh Babu N wrote:
> I tried your method but it showing the same error.
Which method? I made two suggestions. It is always helpful to post the exact
program that you tried and the exact error message you are getting. As I
explained, I do not have a Windows system
I tried your method but it showing the same error.
Ganesh
On Mon, May 6, 2013 at 8:58 PM, Jim Gibson wrote:
>
> On May 6, 2013, at 6:42 AM, Ganesh Babu N wrote:
>
> >
> > Dear All,
> >
> > I am having an XLSX file in server and my OS in Win7. The first op
having an XLSX file in server and my OS in Win7. The first open
> statement is working fine in which we have give the actual file name.
> >
> > 2nd open function is not working where we have given the file name as
> variable.
> >
> > Please help in resolving this error.
On May 6, 2013, at 6:42 AM, Ganesh Babu N wrote:
>
> Dear All,
>
> I am having an XLSX file in server and my OS in Win7. The first open
> statement is working fine in which we have give the actual file name.
>
> 2nd open function is not working where we have g
Dear All,
I am having an XLSX file in server and my OS in Win7. The first open
statement is working fine in which we have give the actual file name.
2nd open function is not working where we have given the file name as
variable.
Please help in resolving this error.
use Win32::OLE;
use Win32
Smith,
Can you please try by setting the path extension
C:\>set PATHEXT=%PATHEXT%;.pl
Thank you
Govardhanan D
Excuse for Typos- Sent from Mobile.
From: Michael Smith
Sent: 03-02-2013 AM 03:24
To: beginners@perl.org
Subject: Re: getting perl to open pl f
it
again, just now, Exactly as you wrote it, in case perhaps pushing one button
out of order could cause a failure. The same thing happens. The "Open with"
window disappears and the program that opens the pl file extension remains the
same.
The only thing left that I can figure to try
d now I can't get anything but notepad to
> open the pl files. I have to type perl.exe test.pl every time
> and I'm just way to lazy for that.
While the other answer given should work, at least for complete
paths to the program file, you may consider wrapping your Perl
programs in a .bat
contains GUItest and now I
> can't get anything but notepad to open the pl files. I have to type
> perl.exe test.pl every time and I'm just way to lazy for that.
>
> I tried all the regular ways to change file extensions in XP. Perl.exe
> isn't listed in the window,
I know get a new OS :)
First I installed strawberry perl but it has no GUItest and I couldn't get
guitest to install. Then I deleted strawberry and I installed
padre-on-strawberry because it says it already contains GUItest and now I can't
get anything but notepad to open the pl fil
lina wrote:
Thanks Jim and John.
btw, what does the fileno mean? mean file-not-open?
It means file number. For example, STDIN is file number 0, STDOUT is
file number 1, STDERR is file number 2 and the next file opened is file
number 3, etc.
John
--
Any intelligent fool can make things
Hi,
On Tue, Aug 28, 2012 at 12:15 PM, lina wrote:
> Thanks Jim and John.
>
> btw, what does the fileno mean? mean file-not-open?
>
perldoc -f fileno
>
> --
> To unsubscribe, e-mail: beginners-unsubscr...@perl.org
> For additional commands, e-mail: beginn
Thanks Jim and John.
btw, what does the fileno mean? mean file-not-open?
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
lina wrote:
Hi,
Hello,
I don't know which is the best way to "check whether this file is open
or not,"
Here it what I came out so far,
#!/usr/bin/env perl
use strict;
use warnings;
use autodie qw(open close);
use 5.012;
my $fn = "new_30.pdb";
open my $fh,
On Aug 27, 2012, at 9:30 PM, lina wrote:
> Hi,
>
> I don't know which is the best way to "check whether this file is open
> or not,"
In general, you don't have to worry about it, because:
1. If a file handle goes out of scope, the file will be closed.
2. If
Hi,
I don't know which is the best way to "check whether this file is open
or not,"
Here it what I came out so far,
#!/usr/bin/env perl
use strict;
use warnings;
use autodie qw(open close);
use 5.012;
my $fn = "new_30.pdb";
open my $fh, '<',
t;>
>> Today I started another perl script that works on top of search.pl. It
>> opens search.pl with a piped open, and them process the results.
>> But I accidentally found that open acted oddly when '(cn=string*)' was
>> passed to it.
>> The possible bug
'
> > ---
> >
> > Today I started another perl script that works on top of search.pl. It
> > opens search.pl with a piped open, and them process the results.
> > But I accidentally found that open acted oddly when '(cn=string*)' was
> > passed to it.
Tessio Fechine wrote:
Hello,
Hello,
I have a perl script that uses Net::LDAP to query an directory service. It
is invoked like this:
---
search.pl '(cn=peter*)'
---
Today I started another perl script that works on top of search.pl. It
opens search.pl with a piped open, and th
works on top of search.pl. It
> opens search.pl with a piped open, and them process the results.
> But I accidentally found that open acted oddly when '(cn=string*)' was
> passed to it.
> The possible bug is that when I pass a nonexistent file name fallowed by
> '(cn=string
Hello,
I have a perl script that uses Net::LDAP to query an directory service. It
is invoked like this:
---
search.pl '(cn=peter*)'
---
Today I started another perl script that works on top of search.pl. It
opens search.pl with a piped open, and them process the results.
But I accident
I've been using Gmail and thought you might like to try it out. Here's an
invitation to create an account.
You're Invited to Gmail!
ganesh vignesh has invited you to open a Gmail account.
Gmail is Google's free email service, built on the idea that email can be
intuitive
>>>>>>>> "Bryan" == Bryan R Harris writes:
>>>
>>> Bryan> How can I use the "safe" 3-argument open and still be able to read
>>> off
>>> a
>>> Bryan> pipe?
>>>
>>> You don'
On 23/08/2011 04:17, Bryan R Harris wrote:
"Bryan" == Bryan R Harris writes:
Bryan> How can I use the "safe" 3-argument open and still be able to read off
a
Bryan> pipe?
You don't. 2-arg open has to be good for something.
And 2-arg open is perfectly safe
>>>>>> "Bryan" == Bryan R Harris writes:
>
> Bryan> How can I use the "safe" 3-argument open and still be able to read off
> a
> Bryan> pipe?
>
> You don't. 2-arg open has to be good for something.
>
> And 2-arg
>>>>> "Bryan" == Bryan R Harris writes:
Bryan> How can I use the "safe" 3-argument open and still be able to read off a
Bryan> pipe?
You don't. 2-arg open has to be good for something.
And 2-arg open is perfectly safe if the second arg is a
How can I do a 3-argument open on STDIN? This doesn't work because the
3-argument open won't open STDIN when you tell it to open "-".
**
@files = ("-");
for (@files) {
print reverse readfile($_);
}
sub readfile {
On 11-08-17 06:53 PM, Bryan R Harris wrote:
How can I do a 3-argument open on STDIN? This doesn't work because the
3-argument open won't open STDIN when you tell it to open "-".
**
@files = ("-");
for (@files) {
prin
On 18/08/2011 01:35, John Delacour wrote:
At 17:53 -0500 17/08/2011, Bryan R Harris wrote:
How can I do a 3-argument open on STDIN? This doesn't work because the
3-argument open won't open STDIN when you tell it to open "-".
**
@files =
At 17:53 -0500 17/08/2011, Bryan R Harris wrote:
How can I do a 3-argument open on STDIN? This doesn't work because the
3-argument open won't open STDIN when you tell it to open "-".
**
@files = ("-");
for (@files
On Wed, Aug 17, 2011 at 6:53 PM, Bryan R Harris
wrote:
> How can I use the "safe" 3-argument open and still be able to read off a
> pipe?
What I have done in the past is manually compare the filename to '-'
and skip the opening and just assign STDIN to my file handle.
How can I do a 3-argument open on STDIN? This doesn't work because the
3-argument open won't open STDIN when you tell it to open "-".
**
@files = ("-");
for (@files) {
print reverse readfile($_);
}
sub readfile {
Hi John,
a few comments on your code (some of which was derived from the OP's).
On Mon, 01 Aug 2011 00:26:29 -0700
"John W. Krahn" wrote:
> homedw wrote:
> > hi all,
>
> Hello,
>
>
> > i want to open some files in a directory, you can see the
rote:
>
> > homedw wrote:
> >
> >> hi all,
> >>
> >
> > Hello,
> >
> >
> >
> > i want to open some tha files in a directory, you can see the details
> >> below,
> >>
> >> #!/usr/bin/perl -w
> >&g
a large file in another drive and
it worked perfectly, after the correction stated above was used!
Regards
On Mon, Aug 1, 2011 at 8:09 AM, homedw wrote:
> hi all,
>
> i want to open some files in a directory, you can see the details below,
>
> #!/usr/bin/perl -w
> use strict;
>
I guess that $sum should be "my $sum" before using it.
Emeka
On Mon, Aug 1, 2011 at 8:26 AM, John W. Krahn wrote:
> homedw wrote:
>
>> hi all,
>>
>
> Hello,
>
>
>
> i want to open some tha files in a directory, you can see the details
&g
homedw wrote:
hi all,
Hello,
i want to open some files in a directory, you can see the details below,
#!/usr/bin/perl -w
use strict;
opendir (FH,'C:\Player');
chdir 'C:\Player';
for my $file(readdir FH)
{
open DH,"$file&qu
hi all,
i want to open some files in a directory, you can see the details below,
#!/usr/bin/perl -w
use strict;
opendir (FH,'C:\Player');
chdir 'C:\Player';
for my $file(readdir FH)
{
open DH,"$file";
foreach my $line()
{
whi
o,word!\n”;
>
> and save it under e:\ as perl.p1
>
> but when I run it with the window commend line as
>
>
> E:\ perl hello.p1 it told me that Can't open perl script "
> hello.p1" No such file or directory!!
>
> how can I solve it thank you!!!
he window commend line as
>
>
> E:\ perl hello.p1 it told me that Can't open perl script "
> hello.p1" No such file or directory!!
>
> how can I solve it thank you!!!
>
"p1" is different than "pl". "pl" is the usual suf
ndow commend line as
>
>
>E:\ perl hello.p1 it told me that Can't open perl script "
>hello.p1" No such file or directory!!
>
>how can I solve it thank you!!!
Maybe hello.pl, not hello.p1?
'pl' (abbreviated from 'Perl') is the co
hi,
I instaled my perl under the e:\r_software\perl.
I wrote a hello world programme as below
#! /usr/bin/perl
print “Hello,word!\n”;
and save it under e:\ as perl.p1
but when I run it with the window commend line as
E:\ perl hello.p1 it told me that Can't open perl s
On May 10, 9:18 pm, u...@stemsystems.com ("Uri Guttman") wrote:
> > "CD" == C DeRykus writes:
>
> CD> On May 9, 1:29 pm, demianricca...@gmail.com (D) wrote:
> >> Hello everyone,
> >>
> >> I would like to learn an efficient way to change a single column in a
> >> file that is accessed
> "CD" == C DeRykus writes:
CD> On May 9, 1:29 pm, demianricca...@gmail.com (D) wrote:
>> Hello everyone,
>>
>> I would like to learn an efficient way to change a single column in a
>> file that is accessed by an external program after the column is
CD> the tie that you mentione
On May 9, 1:29 pm, demianricca...@gmail.com (D) wrote:
> Hello everyone,
>
> I would like to learn an efficient way to change a single column in a
> file that is accessed by an external program after the column is
> changed each time. open write close is what I have been using. I
On 09/05/2011 21:29, D wrote:
Hello everyone,
I would like to learn an efficient way to change a single column in a
file that is accessed by an external program after the column is
changed each time. open write close is what I have been using. I
thought that tieing could help speed it up
> "DR" == Demian Riccardi writes:
>> is the file well defined with white space separation? is the third field
>> always the last field of non-whitespace? is the value of the third
>> field always 0 to start? is it always replaced by its line number? if
>> those are all yes, then you
> is the file well defined with white space separation? is the third field
> always the last field of non-whitespace? is the value of the third
> field always 0 to start? is it always replaced by its line number? if
> those are all yes, then you can do this and it will blow away your
> example in
>>>>> "D" == D writes:
D> I would like to learn an efficient way to change a single column in
D> a file that is accessed by an external program after the column is
D> changed each time. open write close is what I have been using. I
D> thought that
Hello everyone,
I would like to learn an efficient way to change a single column in a
file that is accessed by an external program after the column is
changed each time. open write close is what I have been using. I
thought that tieing could help speed it up. While I didn't dig in too
d
On 05/05/2011 08:31, Geospectrum wrote:
>
> I am putting together a simple website and would like visitors to be
> able to type a number into a form (say 1234) and a perl script should
> run open an existing page called .../1234.html or generate an error
> page if the use enters
2011/5/5 Geospectrum :
> Hi,
>
> I am putting together a simple website and would like visitors to be
> able to type a number into a form (say 1234) and a perl script should
> run open an existing page called .../1234.html or generate an error
> page if the use enters a wrong nu
Hi,
I am putting together a simple website and would like visitors to be
able to type a number into a form (say 1234) and a perl script should
run open an existing page called .../1234.html or generate an error
page if the use enters a wrong number. I will have already uploaded
the page before
directly to Linux.
> >>There are other systems out there more Open Source than Linux like OpenBSD
> >>(for example).
Open Source is ambiguous here. In this context it merely means the
source code is available. In that instance, both the BSDs and the
Linux distros are equally &qu
On Tue, 28 Dec 2010, Shlomi Fish wrote:
Date: Tue, 28 Dec 2010 02:55:32
From: Shlomi Fish
To: beginners@perl.org
Cc: Alvaro Mantilla Gimenez
Subject: Re: New Document:
"How to Start Contributing to or Using Open Source Software"
On Monday 27 Dec 2010 21:44:05 Alvaro Mantil
lem worse [for them]. No??
>
> This whole discussion is stupid. :P The OP was a little off topic, but
> as others have said, Shlomi Fish is one of the more constructive
> posters on this list. And even ignoring that, the OP wasn't /that/ off
> topic. Maybe I only feel this way
From: "Brandon McCaig"
On Sun, Jan 2, 2011 at 9:39 AM, Raymond Wan wrote:
> An extension to your reasoning is that there aren't just two groups of
> users on this list -- advanced and newbies -- but multiple levels.
> Beginners who don't follow the advanced programmers' rules may have
> questions
From: "Raymond Wan" On Sun, Jan 2, 2011 at 00:06, Octavian
Rasnita wrote:
> Better say that bottom-post is an old habit (and advanced programmers usually
> have old habits and not the newbies) and that the rules are enforced by the
> advanced programmers because they can help the others, and th
a little off topic, but
as others have said, Shlomi Fish is one of the more constructive
posters on this list. And even ignoring that, the OP wasn't /that/ off
topic. Maybe I only feel this way because it actually interests me to
write open source software, but meh.
The mailing list rule
On Sun, Jan 2, 2011 at 00:06, Octavian Rasnita wrote:
> Better say that bottom-post is an old habit (and advanced programmers usually
> have old habits and not the newbies) and that the rules are enforced by the
> advanced programmers because they can help the others, and they want to
> everyon
From: "Octavian Rasnita"
> From: "Jenda Krynicky"
> >> There was a period when it was OK to follow that old netiquette
> >> that said that bottom-posting is the good way, but now it isn't.
> >
> > Because you said so?
>
> Yes. Me and many others.
>
> I bottom post (on Perl - related mailing li
From: "Jenda Krynicky"
>> And by the way, there was a period when it was OK to say words like "black"
>> but now it isn't.
...
>
> And it was a much better period. Fuck newspeak and fuck political
> correctness. Rose, the same as shit, under any other name would smell
Better for who? For yo
People. Go -f>@+?*<.-&'_:$#/%! yourselves. How about some more Perl, and a
lot less fucking drama?
At least be original (or copypaste from Stack Overflow[0]) and do this on
topic, folks.
By the way, happy new year!
[0]
http://stackoverflow.com/questions/234075/what-is-your-best-programmer-joke/2
From: "Octavian Rasnita"
> This answer is very good for "Top posts don't bother me as much as
> those who don't trim the quotes." also. :-) When top-posting, the
> advantage is that it is not important how many messages remain at the
> bottom, exactly because nobody reads what's
From: "Shawn H Corey"
> On 10-12-31 10:58 PM, jeff pang wrote:
>> Another problem:
>> Shawn your signature message is too long to read.:)
>>
>> Regards.
>
> Doesn't matter; nobody reads those things anyway. :)
This answer is very good for "Top posts don't bother me as much as those who
don't
move on to the next one. But for
some, the learning part is important and that might encourage them to
stick with Perl or the mailing list.
As for your comment about not being part of the Perl community, you
make it sound like being in the Perl community is an exclusive club.
It isn't.
On 10-12-31 10:58 PM, jeff pang wrote:
Another problem:
Shawn your signature message is too long to read.:)
Regards.
Doesn't matter; nobody reads those things anyway. :)
--
Just my 0.0002 million dollars worth,
Shawn
Confusion is the first step of understanding.
Programming is as m
Hi Parag,
CCing the list.
On Monday 27 Dec 2010 22:33:08 Parag Kalra wrote:
> Hi Shlomi,
>
> Really nice article. Very informative indeed. Keep the good work and I
> really appreciate your efforts and contribution towards OpenSource.
I'm glad you like it. ( And it's not
On Thu, 30 Dec 2010 12:35:37 +0200, Shlomi Fish
wrote:
On the other hand, most of my
posts (and those of most other active members of the lists) were
replies
for people asking for help, while trying to be helpful. And since I
subscribed I've posted much more posts than you.
Why do you f
2011/1/1 Shawn H Corey :
>
> Top posts don't bother me as much as those who don't trim the quotes. Other
> problems:
>
Another problem:
Shawn your signature message is too long to read. :)
Regards.
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: begi
On 10-12-31 02:25 PM, Chap Harrison wrote:
And - seriously - thanks to the volunteers for their patience and effort.
Given enough eyeballs, all questions are answerable (to paraphrase ESR:-)
Chap
On Dec 31, 2010, at 11:57 AM, Octavian Rasnita wrote:
> Happy new years to all of you too!
>
>
that the context is obvious. :-)
>
> Octavian
>
> - Original Message -
> From: "Chap Harrison"
> To: "Perl Beginners"
> Sent: Friday, December 31, 2010 6:17 PM
> Subject: Re: [OT] New Document: "How to Start Contributing to or Using Open
1 - 100 of 781 matches
Mail list logo
