Indeed, the SlickEdit feature seems to be very handy!
---
So, just for the record how to redirect output to stdout and stderr into one
logfile on both,
Windows and Unix:
* cmd > log.txt 2>&1
where "cmd" is any command and its output to stdout (.output, file descriptor
"1") will be
redirected into the file "log.txt" and addition its output to stderr (.error,
file descriptor "2")
will be redirected into the same file as "stdout" (.output, file descriptor
"1").
Sometimes it is very handy to redirect both, stdout and stderr to the same
logfile for later
analyzing and processing by a program.
---rony
On 15.09.2017 16:44, Gil Barmwater wrote:
>
> Thanks Rick! The SlickEdit suggestion sounds like a winner!
>
> Gil
> On 9/15/2017 10:40 AM, Rick McGuire wrote:
>>
>>
>> On Fri, Sep 15, 2017 at 10:23 AM, Gil Barmwater <gbarmwa...@alum.rpi.edu
>> <mailto:gbarmwa...@alum.rpi.edu>> wrote:
>>
... cut ...
>> One other question: the build process produces some warning messages but
>> many of them scroll
>> off the screen. Is there a way to preserve them in a log file (besides
>> redirecting the NMAKE
>> output which leaves you sitting there wondering if the build is still
>> running!)?
>>
>>
>> I'm not aware of any logging capability. I generally run the build in a
>> command line window with
>> a 1000 line buffer so that I can scroll back to see any errors/warnings.
>> Another useful method if
>> you use SlickEdit is to run the build in the SlickEdit command window. This
>> allows you to use
>> SlickEdit to navigate to the location of each warning message.
>>
>> Rick
>>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
