StdOut on Windows

[Mike Bonner]

Hmm also works with standard put, but still have to pipe it to cat or
whatever. Without -u the writing to stdout works when piped to cat, and the
put doesn't. including the -u makes the put command work also

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

> Hey, not sure this is an acceptable method but.. If you have control of
> the target system and can install unxutils, then you can build a standalone
> that does a "write whatever to stdout"
>
> 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.
>
> timeout -ui |cat
>
> I had noticed in the console logs that SOMETHING was occuring (an error
> crops up when a livecode app that does stdout is run) and on a whim did a
> redirect to a file and the file actually did end up with the stuff from
> stdout.
> (timeout > tempfile) so figured being able to pipe it to a well mannered
> utility like cat might work.
>
> The cool thing is that once unxutils are installed you then have access to
> grep, agrep and lots of other nifty things.
> If you want to check out these utils they can be found at *
> http://unxutils.sourceforge.net/*
>
> On Sun, Jan 22, 2012 at 10:47 AM, Mark Schonewille <
> m.schonewille at economy-x-talk.com> wrote:
>
>> Nothing new there. I know for a fact that it doesn't work on Windows and
>> am looking for a good trick.
>>
>> --
>> Best regards,
>>
>> Mark Schonewille
>>
>> Economy-x-Talk Consulting and Software Engineering
>> Homepage: http://economy-x-talk.com
>> Twitter: http://twitter.com/xtalkprogrammer
>> KvK: 50277553
>>
>> Download the Installer Maker Plugin 1.7 for LiveCode here
>> http://qery.us/za
>>
>> On 22 jan 2012, at 18:33, Thunder wrote:
>>
>> > *User Guide.pdf  - Search for stdout*
>> >
>> > Output to Standard Out (stdOut or the Console on Mac OS X)
>> > The stdOut is a useful place to log messages. Unlike the Message Box,
>> it is
>> > easy to log a
>> > sequence of events which you can then scroll back to review later on. It
>> > also has the
>> > advantage of being external to LiveCode so using it does not interfere
>> with
>> > your
>> > application window layering or focus in any way.
>> >
>> > *The stdOut is only available on Linux, Unix or Mac OS X systems.*
>> > */<------ No windows /*
>> >
>> > On Mac OS X, it can be accessed by opening the Console
>> > application, located in the Utilities folder within Applications.
>> > The syntax to write something to stdOut or the Console is:
>> > write tMessage & return to stdout.
>> >
>> >
>> ---------------------------------------------------------------------------------------------------------
>> >
>> > Search for *stdout in the dictionary* indicates that windows *is
>> *supported
>> > under : *Supported Operating Systems*
>> >
>> >
>> ---------------------------------------------------------------------------------------------------------
>> >
>> > ..so...should it work on windows ... or not ?
>> >
>> > (LiveCode 5.0.1)
>> >
>> >
>> >
>> >
>> > Mark Schonewille-3 wrote
>> >>
>> >> workaround .......
>> >>
>> >
>> > ...sorry , no.
>>
>>
>> _______________________________________________
>> 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
>>
>
>