From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22975@debbugs.gnu.org, raeburn@raeburn.org, schwab@linux-m68k.org
Subject: bug#22975: 25.0.92; CANNOT_DUMP build can't start in tty mode
Date: Sun, 13 Mar 2016 21:09:26 +0100 [thread overview]
Message-ID: <56E5C8F6.2000909@gmx.at> (raw)
In-Reply-To: <8360wqfhqu.fsf@gnu.org>
>> > In tty mode, the CANNOT_DUMP version get stuck in a loop at startup
>> > complaining that internal-echo-keystrokes-prefix isn’t defined. If I
>> > set a breakpoint on Fsignal, it’s first complaining about
>> > window--resize-root-window-vertically when trying to display the long
>> > load path, presumably terminating the processing of loadup.el;
>>
>> Can you please try adding a placeholder function like Paul did with
>> Fframe_windows_min_size and Fwindow__sanitize_window_sizes.
>
> How can we know what these placeholders should do, without seeing
> which code calls them?
The idea was that if Ken's assumption is right that complaining about
window--resize-root-window-vertically terminates the processing of
loadup.el, then such a placeholder function (that would do nothing)
would have allowed it to proceed ...
martin
next prev parent reply other threads:[~2016-03-13 20:09 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
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 [this message]
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=56E5C8F6.2000909@gmx.at \
--to=rudalics@gmx.at \
--cc=22975@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=raeburn@raeburn.org \
--cc=schwab@linux-m68k.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).