From: Markus Triska <markus.triska@gmx.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 1708@debbugs.gnu.org, Dan Nicolaescu <dann@ics.uci.edu>
Subject: bug#1708: 23.0.60; g_main_context_prepare() called recursively
Date: Thu, 06 Feb 2014 19:32:35 +0100 [thread overview]
Message-ID: <m238jwks70.fsf@gmx.at> (raw)
In-Reply-To: <8738jxxd4r.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Wed, 05 Feb 2014 17:07:16 -0800")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Are you still seeing this in Emacs 24.3?
No, since I am no longer using emacsclient due to its memory leaks (#1504).
prev parent reply other threads:[~2014-02-06 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 12:00 bug#1708: 23.0.60; g_main_context_prepare() called recursively Markus Triska
2008-12-27 17:18 ` Dan Nicolaescu
2008-12-31 16:26 ` Markus Triska
2008-12-31 16:38 ` Dan Nicolaescu
2014-02-06 1:07 ` Lars Ingebrigtsen
2014-02-06 18:32 ` Markus Triska [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m238jwks70.fsf@gmx.at \
--to=markus.triska@gmx.at \
--cc=1708@debbugs.gnu.org \
--cc=dann@ics.uci.edu \
--cc=larsi@gnus.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).