Re: Unknown runtime screen output question

The script is my own. I am not new to Perl and am aware of redirection and do so when needed.
This output is not from my own code. I assume it is from some library module that I hoped someone could recognize. I am using a grep call to filter an array on a regex.
The interesting thing is that when running in command line I can see flashes of the word "searching" that dissappear. The scheduler seems to be able to capture those suppressed messages.

Comment on Re: Unknown runtime screen output question

Replies are listed 'Best First'.
Re^2: Unknown runtime screen output question by blazar (Canon) on May 26, 2006 at 14:34 UTC
The script is my own. I am not new to Perl and am aware of redirection and do so when needed. Then just do what is generally recommended: prepare a suitably trimmed down version of your script that still exhibits the problem. Chances are that while doing so you will find the answer to your question yourself. And otherwise you will have an actual starting point to offer other people to help you.	[reply]
Re^2: Unknown runtime screen output question by dsheroh (Monsignor) on May 26, 2006 at 16:17 UTC
I see... In that case, if you see the word flashing on the terminal when run interactively, it seems clear what's happening: The code is printing the message then either backspacing over it, sending a 'clear line' command or similar, causing it to be erased from the screen. The logging/capture from the scheduler, on the other hand, is not a fully-featured interactive terminal, so it doesn't know how to do things like backspacing, clearing lines, etc., it just records what's printed, but never erases it. No clue what module might be sending this, though. What modules do you `use`?	[reply] [d/l]