<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
set CM3_ConsoleBehavior=4.1<BR>
m3guiapp<BR>
console behavior still changed<BR>
<BR>
m3guiapp @M3ConsoleBehavior=4.1<BR>
console behavior back to "default"<BR>
<BR> - Jay<BR><BR><BR>> Date: Thu, 19 Jun 2008 08:55:10 +0200<BR>> From: wagner@elegosoft.com<BR>> To: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] proposal for dealing with lazy console--please review and comment!<BR>> <BR>> Quoting Jay <jayk123@hotmail.com>:<BR>> <BR>> > Randy, just because the initialization happens early does not mean <BR>> > you can't affect the behavior later. The type can be changed at <BR>> > initialization time, and then the instance configured later. Unless <BR>> > you are worried about other module initializers ignorantly calling <BR>> > stdout.Wr() and causing the console to appear? If so, yeah.<BR>> ><BR>> > How about @M3 command line parameters instead?<BR>> > At least they aren't "sticky" and can be more easily localized to a <BR>> > single process.<BR>> What does sticky mean here?<BR>> <BR>> > I ignore sh's feature here usually, and in this case that makes good sense<BR><BR></body>
</html>