From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Shmakov <ivan@siamics.net>
Cc: 17169@debbugs.gnu.org
Subject: bug#17169: fails to start with (setq force-load-messages t) in ~/.emacs
Date: Wed, 02 Apr 2014 23:20:48 +0300 [thread overview]
Message-ID: <83fvlvbhzz.fsf@gnu.org> (raw)
In-Reply-To: <87sipv7hky.fsf_-_@violet.siamics.net>
> From: Ivan Shmakov <ivan@siamics.net>
> Date: Wed, 02 Apr 2014 17:43:25 +0000
>
> In GNU Emacs 24.4.50.1 (x86_64-unknown-linux-gnu)
> of 2014-04-02 on violet.siamics.net
> Configured using:
> `configure --prefix=/home/private/users/ivan --disable-silent-rules
> --enable-dependency-tracking --enable-gcc-warnings --without-pop
> --without-sound --without-x-toolkit --without-gpm --without-dbus
> --without-gconf --without-gsettings --without-makeinfo --without-x
> --with-wide-int --with-gnutls --with-zlib'
>
> Configured features:
> NOTIFY GNUTLS LIBXML2 ZLIB
Strange. One of the 2 system I checked is very similar to this one.
> What bothers me the most here is how force-load-messages
> interferes with an otherwise working build?
That part is quite clear: it requires one more slot in the staticvec[]
array.
Can you run Emacs under GDB, put a breakpoint in staticpro, and when
it breaks, show the backtrace and the value of staticidx?
next prev parent reply other threads:[~2014-04-02 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 9:45 bug#17169: fails to start with (setq force-load-messages t) in ~/.emacs Ivan Shmakov
2014-04-02 16:29 ` Eli Zaretskii
2014-04-02 17:43 ` Ivan Shmakov
2014-04-02 20:20 ` Eli Zaretskii [this message]
2014-04-03 6:35 ` Ivan Shmakov
2014-04-03 15:58 ` Eli Zaretskii
2014-04-03 19:05 ` Ivan Shmakov
2014-04-03 20:00 ` Eli Zaretskii
2014-04-03 20:41 ` Ivan Shmakov
2014-04-04 7:55 ` Eli Zaretskii
2014-04-04 9:15 ` Ivan Shmakov
2014-04-04 9:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fvlvbhzz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17169@debbugs.gnu.org \
--cc=ivan@siamics.net \
/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.