From: Stan Pinte <stan.pinte@wanadoo.be>
Subject: Re: [Bug #2110] bug in threading implementation using guile-1.6.1
Date: Fri, 10 Jan 2003 15:23:20 +0100 [thread overview]
Message-ID: <oprisfk60bi4s3pc@BEDEVPINTES> (raw)
In-Reply-To: xy7iswxnldc.fsf@nada.kth.se
On Fri, 10 Jan 2003 15:13:35 +0100, Mikael Djurfeldt <djurfeldt@nada.kth.se>
wrote:
> nobody@savannah.gnu.org writes:
>
>> =================== BUG #2110: LATEST MODIFICATIONS ==================
>> http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2110&group_id=39
>>
>> Changes by: Stan Pinte <stan.pinte@wanadoo.be>
>> Date: 2003-Jan-10 13:38 (GMT)
>>
>> ------------------ Additional Follow-up Comments ------------------------
>>
>>
>> ----
>> This only seems to happen when I make two calls two (gtk-main),
>> indirectly.
>>
>> -> one via the (gtk-ensure-handler) call
>> -> one afterwards, via the (gtk-main) call.
>
> Well, this is not a correct usage pattern. (gtk-ensure-handler)
> spawns a gtk handler which handles all events of the application.
> That is, it is an *alternative* to (gtk-main).
>
> If your intention with calling gtk-main is to wait for the application
> to quit, I suggest that you wait on a condition variable instead.
> Then make sure that it is signalled when the application quits.
> (But maybe someone else more versed in guile-gtk have a better
> suggestion.)
>
> If I do what you describe in an interactive guile session, I get a lot
> of glib warning messages which are properly informative:
>
> g_main_iterate(): main loop already active in another thread
>
> It would of course be nicer not to get stuck in a loop but just get
> *one* error message...
that is exactly the same as I get. thanks for helping.
>
> Best regards,
> Mikael Djurfeldt
>
>
--
Stan Pinte
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2003-01-10 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 13:38 [Bug #2110] bug in threading implementation using guile-1.6.1 nobody
2003-01-10 14:13 ` Mikael Djurfeldt
2003-01-10 14:23 ` Stan Pinte [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-09 7:04 [bug " anonymous
2008-08-25 8:32 ` Ludovic Courtès
2009-07-20 21:38 ` Ludovic Courtès
2009-08-17 12:38 ` Ludovic Courtès
2003-01-02 13:12 [Bug " nobody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=oprisfk60bi4s3pc@BEDEVPINTES \
--to=stan.pinte@wanadoo.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).