From: Alp Aker <alptekin.aker@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12745@debbugs.gnu.org, ami@fischman.org
Subject: bug#12745: crash in bidi_pop_it during (idle) redisplay
Date: Mon, 29 Oct 2012 16:42:23 -0400 [thread overview]
Message-ID: <CACxch4rMzA43Bt24+BUsVdnLn4MRJ0WY=Fuwj=UWmgSbx0khkQ@mail.gmail.com> (raw)
In-Reply-To: <83390x81ql.fsf@gnu.org>
> Out of curiosity: what is the purpose of having in an overlay this
> weird character and then to display it as a space?
It's a hack to achieve compatibility with packages that change the
display table entry for the newline character. When fci-mode is
active it puts, at the end of each line, a stretch glyph and then an
image with the line segment indicating the fill column. When, e.g.,
whitespace-mode changes the display table entry for newlines to
display a '$' at the end of the line, this would show up *after* the
stretch glyph and image unless we do something to handle that case.
So what fci-mode tries to do is intercept changes to the display table
entry for newlines. If something like whitespace mode changes newline
display, fci-mode changes the display table back to showing newlines
as blanks, and then updates the display table entry for U+E000 to (in
this case) [?$], so that the end-of-line indication appears where the
user expects it to be.
So the weird character is just a hook on which we can hang display
vectors intended for newlines. But when the display settings for
newlines are normal it just gets displayed as a space. This is
admittedly a gross manoeuvre, but I couldn't think of any other way to
handle the issue.
next prev parent reply other threads:[~2012-10-29 20:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 3:31 bug#12745: crash in bidi_pop_it during (idle) redisplay Paul Eggert
2012-10-28 7:49 ` Paul Eggert
2012-10-28 7:50 ` Paul Eggert
2012-10-28 17:23 ` Eli Zaretskii
2012-10-28 19:00 ` Ami Fischman
2012-10-28 19:50 ` Eli Zaretskii
2012-10-29 4:26 ` Ami Fischman
2012-10-29 17:11 ` Eli Zaretskii
2012-10-29 17:56 ` Ami Fischman
2012-10-29 18:10 ` Eli Zaretskii
2012-10-29 18:29 ` Ami Fischman
2012-10-29 18:55 ` Eli Zaretskii
2012-10-29 18:56 ` Alp Aker
2012-10-29 19:09 ` Alp Aker
2012-10-29 19:23 ` Ami Fischman
2012-10-29 20:24 ` Eli Zaretskii
2012-10-29 20:57 ` Eli Zaretskii
2012-10-29 21:08 ` Ami Fischman
2012-10-30 17:52 ` Eli Zaretskii
2012-10-30 18:29 ` Ami Fischman
2012-10-30 21:00 ` Eli Zaretskii
2012-10-30 21:08 ` Ami Fischman
2012-10-31 15:46 ` Eli Zaretskii
2012-11-01 22:25 ` Ami Fischman
2012-11-02 7:17 ` Eli Zaretskii
2012-11-02 7:43 ` Ami Fischman
2012-11-03 9:31 ` Eli Zaretskii
2012-10-29 20:25 ` Eli Zaretskii
2012-10-29 20:42 ` Alp Aker [this message]
2012-10-29 20:59 ` Eli Zaretskii
2012-10-29 21:25 ` Alp Aker
2012-10-29 21:53 ` Alp Aker
2012-11-23 20:14 ` Ami Fischman
2012-11-23 21:56 ` Eli Zaretskii
2012-11-25 4:52 ` Ami Fischman
2012-11-25 16:51 ` Eli Zaretskii
2013-02-10 3:07 ` Glenn Morris
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='CACxch4rMzA43Bt24+BUsVdnLn4MRJ0WY=Fuwj=UWmgSbx0khkQ@mail.gmail.com' \
--to=alptekin.aker@gmail.com \
--cc=12745@debbugs.gnu.org \
--cc=ami@fischman.org \
--cc=eliz@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).