From: Eli Zaretskii <eliz@gnu.org>
To: dann@gnu.org
Cc: 9963@debbugs.gnu.org
Subject: bug#9963: ./temacs -Q -nw abort in bidi_initialize
Date: Sun, 06 Nov 2011 20:28:53 +0200 [thread overview]
Message-ID: <831utljeai.fsf@gnu.org> (raw)
In-Reply-To: <E1RMx5v-00072T-6r@fencepost.gnu.org>
> Date: Sun, 06 Nov 2011 02:24:43 -0500
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 9963@debbugs.gnu.org
>
> > > This abort means you somehow have a problem loading uni-bidi.el, or
> > > didn't load it at all, or perhaps load a wrong uni-bidi.el (e.g., from
> > > Emacs 23). It is strange that it works without -nw, though.
> >
> > It looks this happens when printing the first "Loading" message at
> > startup to load loadup.el.
>
> That figures: Emacs needs uni-bidi for display, and `message' enters
> redisplay.
>
> > Is uni-bidi.el loaded before that?
>
> Evidently, it isn't. I think it is pulled in when charprop is loaded,
> but that's half-way down loadup.el.
>
> We need to find a way of loading uni-bidi and uni-mirrored before
> loading loadup.el. I will get to that later today, if no one beats me
> to it.
I think I fixed this (revision 106305 on the trunk), please check.
For the record: I decided that loading uni-bidi in advance is not a
good idea, as proper functioning of character property tables needed
by bidi.c depends on many other *.el files that are normally loaded
before uni-bidi. There be dragons there. So instead, I disabled bidi
reordering for as long as purify-flag is non-nil; I hope this is TRT
for all supported configurations, including CANNOT_DUMP.
next prev parent reply other threads:[~2011-11-06 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 3:40 bug#9963: ./temacs -Q -nw abort in bidi_initialize Dan Nicolaescu
2011-11-06 4:01 ` Eli Zaretskii
2011-11-06 4:48 ` Dan Nicolaescu
2011-11-06 7:24 ` Eli Zaretskii
2011-11-06 9:47 ` Andreas Schwab
2011-11-06 10:08 ` Eli Zaretskii
2011-11-06 18:28 ` Eli Zaretskii [this message]
2011-11-06 23:10 ` Dan Nicolaescu
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=831utljeai.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9963@debbugs.gnu.org \
--cc=dann@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 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.