The only problem I was trying to determine was could i know if I was running from BBEdit dynamically or not? That was the question. No problem, just could I know what environment I was running in. The output was a the Unix output log which up to the last update automatically came to the front of the BBEdit windows. No longer does. Whether it is Perl or another scripting language, I was trying to make it easier as one tested.
So that is what I was after... ;) WagsWorld World of Perl Hebrews 4:15 Ph D:(408)914-1341 Ph M:(408)761-7391 On Nov 21, 2020, 21:10 -0800, Uri Guttman <u...@stemsystems.com>, wrote: > On 11/21/20 10:32 PM, wagsworl...@yahoo.com wrote: > > Well, up until this last update is BBEdit, when a script was run while > > in BBEdit, the Unix log file would automatically come to the fore > > front. Now it stays hidden. > > > > that doesn't sound like a perl problem. what log file? there are many on > a unix system. and why/how would a log file come to the front? it would > have to be open in some program. > > > A gentleman on the BBEdit mail list gave an osasctipt that one can > > execute from within the script bring executed. But sometimes I run > > from terminal session, so don’t want to tell BBEdit to do something is > > not required. Hence where am I and from that know what to do... > again, i don't see the actual problem you are having. is it really a > perl issue? would the problem exist if you did your program in another > language? that is a good question to determine if it is a language vs > system issue. i don't see a perl problem in your comments. > > thanx, > > uri >
