From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ami Fischman <ami@fischman.org>, emacs-devel@gnu.org
Subject: Re: crash in bidi_pop_it during (idle) redisplay
Date: Sun, 28 Oct 2012 00:53:19 -0700 [thread overview]
Message-ID: <508CE46F.5060708@cs.ucla.edu> (raw)
In-Reply-To: <83sj8z8cyt.fsf@gnu.org>
On 10/27/2012 08:58 PM, Eli Zaretskii wrote:
> please file a bug about this via "M-x report-emacs-bug RET".
I filed a bug report; it's Bug#12745, so it can be seen at
<http://bugs.gnu.org/12745> and further email about it can
be sent to <12745@debbugs.gnu.org>. I've copied the current
thread into it.
prev parent reply other threads:[~2012-10-28 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 2:25 crash in bidi_pop_it during (idle) redisplay Ami Fischman
2012-10-28 3:58 ` Eli Zaretskii
2012-10-28 4:09 ` Ami Fischman
2012-10-28 18:45 ` Glenn Morris
2012-10-28 7:53 ` Paul Eggert [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=508CE46F.5060708@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=12745@debbugs.gnu.org \
--cc=ami@fischman.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).