Another satisfied customer after fighting the long fight

merlyn on 2005-12-13T17:16:23

I search for "perl" in blogs constantly using RSS feeds from and , and in the midst of the noise, I found someone very frustrated with Perl.

His complaint arose because of a Unix-centric item in the FAQ, but he also noticed that http://faq.perl.org also had some weirdness. I got onto IRC, found Robrt to look at the faq.perl.org problem, got some email, and some resolution, and emailed the original guy to let him know what was what.

The result? He's now a happy camper, and we have one less person running around yelling "Perl sucks!". All in a day's work.


I may be wrong...

sigzero on 2005-12-13T19:57:32

I read in some blog discussion or newsgroup that 'cls' is not really a callable command in Windows, it is a hack. Which is why it doesn't work.

I will try and remember the conversation...

Re:I may be wrong...

sigzero on 2005-12-13T20:04:12

Or maybe I don't understand his problem...

If I run:

$clear = "cls";
system($clear);

That clears my screen. So maybe I don't know his problem.

Re:I may be wrong...

sigzero on 2005-12-13T20:19:21

I think this is it. 'cls' is not a program like cls.exe or cls.com but it is a command available to the CMD environment shell. Therefore, you cannot run it with `cls` because Windows doesn't know what to do with that.

You have to do something like: `cmd /c cls`

Win32::Console or Term::InKey

runrig on 2005-12-13T22:08:00

The $x = `cls` trick doesn't work on Windows, but there's Win32::Console, which is non-portable and a little awkward, but someone wrapped the clear screen function into a Unix/Windows portable module, Term::InKey.

RE: faq.perl.org being borked

stu42j on 2005-12-14T20:10:50

http://perldoc.perl.org/perlfaq.html

Bravo!

n1vux on 2005-12-14T22:36:30

Yeah Merlyn!