On Wed, Aug 19, 2009 at 9:06 PM, Michael Petch<mpe...@capp-sysware.com> wrote:
> unknown keywords to stdout.
>
> @@ -1264,10 +1252,7 @@
> break;
>
> if( !pc->sz ) {
> - outputf( _("Unknown keyword `%s'."), pch );
> - output("\n");
> -
> - outputx();
> + outputerrf( _("Unknown keyword `%s'.\n"), pch );
> return;
> }
>
> Its curious that stderr output didn't previously go to the console.
>
gnubg is very verbose, even when commands are working as expected and
therefore normal output is discarded during start up. Errors, on the
other hand, are printed.
>
> I notice that the key section that drives this is in function main()
> (gnubg.c). Among other things is:
>
> #ifdef WIN32
> fNoTTY = TRUE;
> #endif
>
Windows executables have a special flag set requiring the command line
background (or not). I believe that is the motivation for doing things
differently. Windows users are apparently not comfortable with having
the command line window hanging around.
Christian
_______________________________________________
Bug-gnubg mailing list
Bug-gnubg@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnubg
