X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Virus-Scanned:	Debian amavisd-new at mail.linetec.nl
Message-ID:	<7e38fe61-7350-7cca-4a27-3369ea504272@linetec.nl>
Date:	Tue, 21 Jun 2022 20:35:21 +0200
MIME-Version:	1.0
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
	Thunderbird/91.9.1
Subject:	Re: [geda-user] Installing geda, pcb from scratch - last problem
	SOLVED
To:	geda-user AT delorie DOT com
References:	<xn35hhnpho DOT fsf AT envy DOT delorie DOT com>
	<400b3366-05cb-9377-8211-0a6cf0a9753d AT linetec DOT nl>
	<f9e44e10-34cf-657e-76b0-8314aab26441 AT grinsen-ohne-katze DOT de>
	<16de0564-4ae8-3d2f-d8d3-fce9cf17e4a8 AT linetec DOT nl>
	<92295ad-a425-4e2f-98cd-1c7a3e7dfa39 AT grinsen-ohne-katze DOT de>
	<8812571a-4edd-e6ed-7607-244efe207d5d AT linetec DOT nl>
	<e01d65b3-66b0-0e3e-e6ed-897368163f27 AT linetec DOT nl>
	<1d4b9138-f147-b299-69d5-74e3d5aadd3e AT grinsen-ohne-katze DOT de>
	<5eeadbd6-a72d-ecb0-5767-62657edc4a5e AT linetec DOT nl>
	<7e259699-61ea-8050-18d1-5109797c6cc8 AT linetec DOT nl>
	<20220621160643 DOT 49d35762 AT jrenewsid DOT jretrading DOT com>
	<152271d6-1656-1988-e6ca-85ec62fe78b1 AT grinsen-ohne-katze DOT de>
	<a2f7805a-056a-29e1-885e-b4c633220cbd AT linetec DOT nl>
	<bfd4c84-97e4-2d-d66f-de5d672ed89a AT grinsen-ohne-katze DOT de>
From:	"Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
In-Reply-To:	<bfd4c84-97e4-2d-d66f-de5d672ed89a@grinsen-ohne-katze.de>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Op 21-06-2022 om 19:41 schreef Roland Lutz:
> On Tue, 21 Jun 2022, Richard Rasker (rasker AT linetec DOT nl) [via 
> geda-user AT delorie DOT com] wrote:
>> The only difference is that lepton-schematic keeps silent while this 
>> happens instead of popping up error messages all the time like gschem 
>> does.
>
> gschem raises the status window whenever a message with "warning" 
> priority or higher is printed so the warning isn't lost in case the 
> status window isn't currently visible.  Since GTK warnings are 
> redirected to the log window, this applies to them, as well.
>
> If this behavior annoys you, you can either dock the status window to 
> the bottom of the window (via View > Bottom Dock > Status) or comment 
> out the following code in gschem/src/gschem_log_dockable.c:
>
>>   if ((strcmp (tag_name, "critical") == 0 ||
>>        strcmp (tag_name, "warning") == 0))
>>     gschem_dockable_present (GSCHEM_DOCKABLE (dockable));

Nah, gschem is not to blame here. I've used it for many, many years 
without messages like this popping up, and the real culprit is more or 
less identified and neutralized.

Besides, even if the Status window does not pop up, those error messages 
still pile up in the log files, making it grow with several kilobytes at 
each and every menu event.

But thanks anyway :-)

Regards,

Richard

- Raw text -