From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Alexis <flexibeast@gmail.com>
Cc: 17059@debbugs.gnu.org
Subject: bug#17059: bug 17059 still present
Date: Thu, 23 Oct 2014 09:18:46 -0400 [thread overview]
Message-ID: <jwvsiifdixh.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87oat3z1i7.fsf@gmail.com> (Alexis's message of "Thu, 23 Oct 2014 18:27:29 +1100")
> So: calling `sit-for` in `doc-view-start-process` solves the problem for
> me:
[...]
> Is this a reasonable solution?
No, that just changes the odds of the race-condition, but is only an
ugly workaround. IIUC Tassilo installed an actual fix into trunk a few
days ago.
Stefan
next prev parent reply other threads:[~2014-10-23 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5315.1413844526@ccs.covici.com>
2014-10-22 7:28 ` bug#17059: bug 17059 still present Alexis
2014-10-22 13:13 ` Stefan Monnier
2014-10-23 7:27 ` Alexis
2014-10-23 13:18 ` Stefan Monnier [this message]
2014-10-23 22:12 ` Alexis
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=jwvsiifdixh.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17059@debbugs.gnu.org \
--cc=flexibeast@gmail.com \
/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).