From: Juanma Barranquero <lekktu@gmail.com>
To: Eduard Wiebe <ew@pusto.de>
Cc: 7616@debbugs.gnu.org
Subject: bug#7616: 24.0.50; bidi; emacs crashes with SIGABRT
Date: Mon, 28 Mar 2011 18:04:56 +0200 [thread overview]
Message-ID: <AANLkTimVaWQBkgr+moSivWLQet7QHe8NVOCO87JwuYdy@mail.gmail.com> (raw)
In-Reply-To: <87wrngfbcb.fsf@pusto.de>
Another recipe to trigger the same bug:
emacs -Q --eval "(setq-default bidi-display-reordering t)" etc\NEWS
-f vc-annotate
then type "v" (which runs vc-annotate-toggle-annotation-visibility)
and move around the "*Annotate NEWS (rev ...)*" buffer with up/down.
next prev parent reply other threads:[~2011-03-28 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 13:32 bug#7616: 24.0.50; bidi; emacs crashes with SIGABRT Eduard Wiebe
2010-12-11 17:15 ` Eli Zaretskii
2010-12-11 17:34 ` Eli Zaretskii
2010-12-11 17:50 ` Eduard Wiebe
2011-03-28 16:04 ` Juanma Barranquero [this message]
2011-07-14 17:50 ` Eli Zaretskii
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=AANLkTimVaWQBkgr+moSivWLQet7QHe8NVOCO87JwuYdy@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=7616@debbugs.gnu.org \
--cc=ew@pusto.de \
/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).