Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 05 Aug 2009 16:50:52 -0400
From:      Tom Uffner <tom@uffner.com>
To:        "Carlos A. M. dos Santos" <unixmania@gmail.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: x11-toolkits/xview (actually contool)
Message-ID:  <4A79F0AC.4000103@uffner.com>
In-Reply-To: <e71790db0908042008j53d97e79gd38c088b5fdc858f@mail.gmail.com>
References:  <4A74D10A.9000507@uffner.com>	 <200908031312.14400.mel.flynn%2Bfbsd.ports@mailing.thruhere.net>	 <4A77A67D.1050101@uffner.com>	 <200908032207.37816.mel.flynn%2Bfbsd.ports@mailing.thruhere.net>	 <4A77D926.2070304@uffner.com> <e71790db0908042008j53d97e79gd38c088b5fdc858f@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Carlos A. M. dos Santos wrote:

> Can't xconsole do the job for you instead of contool?

more or less. i am using xconsole by default. however i prefer contool
because it has the following features which are missing from every other
X console program that I am aware of:

1. it can remain iconified (or entirely unmapped) and out of my way most
of the time.
2. it can timestamp the messages it prints
3. it can alert me to the presence of new console messages by flashing
its icon, beeping, and/or opening its window
4. it allows me to specify, using regular expression filters, the types
of messages it should or should not alert on.

> BTW, what problems do you have with contool? Are they the same ones
> discussed before in these threads?
> 
>      http://lists.freebsd.org/pipermail/freebsd-hackers/2008-October/026516.html
>      http://lists.freebsd.org/pipermail/freebsd-hackers/2008-November/026722.html

my xconsole still exhibits those problems. don't know about contool yet.
as i said, i haven't had the time to diagnose it yet. what console i use
on my X workstations is not really that high a priority in the grand scheme
of things. contool is exiting with this message:

Assertion failed: (ret != inval_id), function _XAllocID, file xcb_io.c, line 378.
Abort

which may be another symptom of the tty layer changes, but i haven't really
had time to look at it yet.

tom




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A79F0AC.4000103>