StdOut on Windows

Mike Bonner bonnmike at gmail.com
Sun Jan 22 13:59:49 EST 2012


Hmm ok, first run its low, after that it seems to be reliably fast (and
don't know why I didn't remember "more") so I wonder if its a matter of
diskaccess and cache.  Recent run = superfast rerun.

On Sun, Jan 22, 2012 at 11:58 AM, Mike Bonner <bonnmike at gmail.com> wrote:

> Yeah I've seen random delays too. Sometimes its lightning fast, other
> times as you say up to about a second delay. Kinda strange.
>
>
> On Sun, Jan 22, 2012 at 11:49 AM, Ken Ray <kray at sonsothunder.com> wrote:
>
>>
>> On Jan 22, 2012, at 12:28 PM, Mike Bonner wrote:
>>
>> > If you run it with the -ui parameters, as you've seen nothing appears on
>> > screen. But if you pipe to cat, viola' It works.
>>
>> If you don't have cat, you can pipe it to 'more' as well, and that works
>> (although after a delay). My code:
>>
>> on startup
>>    write "Hello" & cr to stdOut
>>    quit
>> end startup
>>
>> I called the standalone "cmdlinetest" so when I ran this in the command
>> window:
>>
>>  cmdlinetest | more
>>
>> if put "Hello" into the current command window (after a second delay
>> though).
>>
>> Just FYI,
>>
>> Ken Ray
>> Sons of Thunder Software, Inc.
>> Email: kray at sonsothunder.com
>> Web Site: http://www.sonsothunder.com/
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>



More information about the use-livecode mailing list