From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22975@debbugs.gnu.org, Ken Raeburn <raeburn@raeburn.org>
Subject: bug#22975: 25.0.92; CANNOT_DUMP build can't start in tty mode
Date: Fri, 11 Mar 2016 21:51:04 +0100 [thread overview]
Message-ID: <8737rwyc07.fsf@linux-m68k.org> (raw)
In-Reply-To: <83bn6kiypm.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Mar 2016 21:47:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> OK, I see. So now it's crystal clear that bidi-display-reordering
> should be bound to nil until loadup finishes, otherwise we are
> playing with fire.
>
> Is there a way to know that the build CANNOT_DUMP from Lisp?
Would it be wrong to do this always? In temacs that is preparing to
dump the value of bidi-display-reordering should make no difference.
(A emacs that CANNOT_DUMP doesn't have dump-emacs.)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-03-11 20:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 5:41 bug#22975: 25.0.92; CANNOT_DUMP build can't start in tty mode Ken Raeburn
2016-03-10 7:10 ` Eli Zaretskii
2016-03-10 7:39 ` Eli Zaretskii
2016-03-11 11:17 ` Ken Raeburn
2016-03-11 14:31 ` Eli Zaretskii
2016-03-11 19:18 ` Ken Raeburn
2016-03-11 19:47 ` Eli Zaretskii
2016-03-11 20:50 ` Kenneth Raeburn
2016-03-11 20:51 ` Andreas Schwab [this message]
2016-03-11 21:06 ` Eli Zaretskii
2016-03-12 10:01 ` Eli Zaretskii
2016-03-13 1:21 ` Ken Raeburn
2016-03-13 12:08 ` martin rudalics
2016-03-13 16:46 ` Eli Zaretskii
2016-03-13 20:09 ` martin rudalics
2016-03-13 20:31 ` Eli Zaretskii
2016-03-14 7:42 ` martin rudalics
2016-03-13 16:45 ` Eli Zaretskii
2016-03-14 7:17 ` Ken Raeburn
2016-03-14 17:41 ` Eli Zaretskii
2016-03-15 3:33 ` Ken Raeburn
2016-03-15 17:48 ` Eli Zaretskii
2016-03-15 18:29 ` Stefan Monnier
2016-03-15 18:44 ` Eli Zaretskii
2016-03-15 19:31 ` Stefan Monnier
2016-03-15 19:48 ` 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=8737rwyc07.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=22975@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=raeburn@raeburn.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).