all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: 19660@debbugs.gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: bug#19660: Acknowledgement (24.4.51; Crash in draw_row_fringe_bitmaps)
Date: Sun, 25 Jan 2015 17:46:19 +0200	[thread overview]
Message-ID: <83386ysw1g.fsf@gnu.org> (raw)
In-Reply-To: <768087C3-7B81-44FD-BCCC-629535681556@swipnet.se>

> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Sun, 25 Jan 2015 10:17:20 +0100
> 
> Fixed, but it would be nice to know why this function needs input blocked.

This was there since day one, according to the history.  Unless Kim,
who wrote it (CC'ed), can recollect why he put the assertion there,
I'm afraid the reason is lost in time.  My wild guess would be that
the reason is this function calls X APIs to actually draw stuff, and
many of those block input.  Perhaps Kim wasn't sure whether input
should be blocked here.

If no other information emerges, my suggestion would be to remove the
assertion on master, and see if we get any bug reports.

Thanks.





  reply	other threads:[~2015-01-25 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  6:30 bug#19660: 24.4.51; Crash in draw_row_fringe_bitmaps Jan D.
2015-01-23  7:05 ` Jan D.
     [not found] ` <handler.19660.B.1421994662864.ack@debbugs.gnu.org>
2015-01-25  9:17   ` bug#19660: Acknowledgement (24.4.51; Crash in draw_row_fringe_bitmaps) Jan D.
2015-01-25 15:46     ` Eli Zaretskii [this message]
2015-01-26  9:12       ` Jan D.
2015-01-26  9:31         ` Eli Zaretskii
2015-01-27  9:16           ` Jan D.
2015-01-27 17:41             ` Eli Zaretskii
2015-01-27 18:22               ` Jan D.
2015-01-27 19:13                 ` Eli Zaretskii
2015-01-26 11:10       ` Kim Storm

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83386ysw1g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19660@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=storm@cua.dk \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.