[Glass] "Transcript enableLoggingToGemLogFileForSession" not working anymore?

[Dale Henrichs via Glass]

Mariano,

When you run topaz the log file is written to stdout. In order to get a 
"log file" for a topaz session, you either capture stdout/stderr via 
output redirection or you can use the topaz `output` to route 
stdout/stderr to another file ... note that you have to supply the full 
path when using the `output` command.

I would recommend using output redirection when you want to create a log 
for topaz, because output redirection picks up the startup banner which 
includes a lot of useful information about the session...

Dale


On 2/2/17 5:49 AM, Mariano Martinez Peck via Glass wrote:
> Hi Dale,
>
> Remember some time ago we added #enableLoggingToGemLogFileForSession 
> and related methods?
>
> I am trying this simple script on a 3.3.3 stone:
>
> #!/bin/bash
>
> $GS_HOME/bin/startTopaz $1 -l <<EOF
>
> login
> run
> Transcript enableLoggingToGemLogFileForSession.
> Transcript show: 'wtf'.
> %
>
> commit
> logout
> exit
>
> EOF
>
>
> And then on my stone logs directory:
>
> [xx at xx logs]$ grep "wtf" *.log
> [xx at xx logs]$
>
>
> The string does gets written in the ObjectLog. But I want to gem file!
>
> Thanks in advance,
>
>
>
> -- 
> Mariano
> http://marianopeck.wordpress.com
>
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170202/9f299df7/attachment.html>