From: David Kuehling <dvdkhlng@gmx.de>
To: emacs-devel@gnu.org
Subject: Some OpenWrt port related problems
Date: Tue, 28 Dec 2010 11:15:35 +0100 [thread overview]
Message-ID: <87sjxi5hko.fsf@snail.Pool> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1916 bytes --]
Hi,
I'm currently working on an OpenWrt port [1] for Emacs23 to use on the
Ben NanoNote PDA [2].
OpenWrt packages use cross-compilation, so Emacs is used in a NO_DUMP
configuration, loading loadup.el every time it starts. This causes at
least one problem with environment variables, that I already fixed [3].
Now I'm hitting another problem when using org-mode:
File mode specification error:
(wrong-type-argument stringp (require . t-mouse))
After some debugging this looks like being caused by variable
load-history containing the element:
((require . t-mouse))
This looks a little broken, since all other elements have a
filename-string in front of that cons cell, e.g.:
("/usr/share/emacs/23.2/lisp/term/linux.el"
(defun . terminal-init-linux))
Now org-mode calls eval-after-load which calls
load-history-filename-element which causes the wrong-type-argument error
when using the 'car' of ((require . t-mouse)) with string-match.
I can sanitize load-history in site-start.el, removing the broken entry,
but that's not a very clean fix (also it takes time and memory, what a
waste).
Anybody knows who's fault that error is anyways? is ((require
. t-mouse)) a valid entry? Is eval-after-load broken? How does that
entry get inserted into load-history in the first place?
Full output of C-h v load-history attached.
thanks for any help,
cheers,
David
PS: if it helps I could hand out SSH accounts to the nanonote to
individual developers
[1]
http://projects.qi-hardware.com/index.php/p/openwrt-packages/source/tree/master/emacs
[2] http://en.qi-hardware.com/wiki/Ben_NanoNote
[3]
http://projects.qi-hardware.com/index.php/p/openwrt-packages/source/tree/master/emacs/patches/010-fix-init-env.patch
--
GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg
Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40
[-- Attachment #1.2: load-history.gz --]
[-- Type: application/octet-stream, Size: 24031 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2010-12-28 10:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 10:15 David Kuehling [this message]
2010-12-28 19:36 ` Some OpenWrt port related problems Stefan Monnier
2010-12-28 21:12 ` David Kuehling
2010-12-28 22:02 ` Stefan Monnier
2010-12-29 9:37 ` David Kuehling
2010-12-29 7:47 ` Richard Stallman
2010-12-29 9:28 ` David Kuehling
2010-12-30 4:08 ` Ken Raeburn
2011-01-01 14:20 ` David Kuehling
2011-01-01 15:06 ` Andreas Schwab
2011-01-01 15:34 ` Eli Zaretskii
2011-01-02 1:35 ` Ken Raeburn
2011-01-02 13:53 ` David Kuehling
2011-01-02 14:44 ` Stefan Monnier
2011-01-02 14:55 ` David Kuehling
2011-01-02 20:35 ` Ken Raeburn
2011-01-02 21:12 ` David Kuehling
2011-01-03 9:32 ` David Kuehling
2010-12-30 16:06 ` Richard Stallman
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=87sjxi5hko.fsf@snail.Pool \
--to=dvdkhlng@gmx.de \
--cc=emacs-devel@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.