Re: FVWM: 2.0.46 -> 2.1.4 differences in IconMan, Buttons

From: Mark Crocker <mcrocker_at_micron.com>
Date: Tue, 15 Dec 1998 17:10:13 -0700 (MST)

On Tue, 15 Dec 1998 13:43:49 -0700 (MST), Mark Crocker <mcrocker_at_micron.com> wrote:

> On Mon, 14 Dec 1998 22:52:54 -0500 (EST), Jim Nicholson <jim_at_kosmic.org> wrote:

>> I bit and built the new version, and managed to install it. I'm
>> noticing some behaviors that puzzle me:

>> - FvwmIconMan starts out by issuing "*FvwmIconMan: cannot open
>> /dev/console" and then goes on to send all kinds of debug info to
>> stdout. Is there a way to turn this off?

Yes -- I think so. I'm not an expert C programmer, but I found that
debug.h in the modules/FvwmIconMan directory has the following lines
near the top.

        #if 1
        #define PRINT_DEBUG
        #endif

Since the lines that produce the console messages that I see all come
from the print_button_info(Button *b) function (in xmanager.c), which
is #ifdef'd with PRINT_DEBUG, then changing the 1 in debug.h to a 0
should turn off the debugging messages that we are seeing.

This looks to be "hardwired". If anyone out there knows a "soft" way
to do this, please let me know.

> I get this too. I don't know how to turn it off, but definining a
> console at least keeps it from printing to the display.

> I have contool in my .Xinitrc, so the errors go to there. When I
> boot from a system that doesn't have console, I use the -C option on
> an Xterm to grab the console output.

I meant to say if the system doesn't have contool, use xterm -C...
And now I DO know how to turn it off.

-----------------------------------------------------------------------------
--
Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Dec 15 1998 - 18:10:41 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:02 BST