From: Nick Roberts <nickrob@snap.net.nz>
To: David Reitter <david.reitter@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: crashes during Feval from within WINDOW_WANTS_HEADER_LINE_P
Date: Sun, 2 Mar 2008 20:53:03 +1300 [thread overview]
Message-ID: <18378.23775.318854.68572@kahikatea.snap.net.nz> (raw)
In-Reply-To: <8CCF0B2D-4741-4C98-92D9-3C8C88514ABD@gmail.com>
> > and it looks to me like the elisp function whose name is stored in
> > `window-wants-header-line-function' is a lisp primitive which either has
> > too many argumnts ( > 8 ) or whose argument list has been incorrectly
> > defined.
>
> I found the same in the code, but this is not true. The function is
>
> (defun need-header-line-p (window) t)
You're right, abort is called from Feval, not Ffuncall.
> and it seems to get called in some situations without problems.
> Perhaps there is some re-entrance business when re-display is
> triggered from the Lisp side? Is that possible?
>
> I've not found much in the way of documentation (beyond a section in
> the the Emacs Lisp Reference), and it's pretty hard to find one's way
> into the C source.
The source _is_ the documentation, as they say. I've found lisp.h a good
starting point. Any real documentation can easily become outdated but the
XEmacs Internals Manual by Ben Wing is good for some things, like specbinding.
Generally though, if it seems difficult to understand the source code that's
probably because it is difficult to understand the source code: there's no
silver bullet.
> Either way, I've solved my problem now without calling a Lisp function.
>
> - D
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-03-02 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 12:03 crashes during Feval from within WINDOW_WANTS_HEADER_LINE_P David Reitter
2008-03-01 20:58 ` Nick Roberts
2008-03-01 21:35 ` David Reitter
2008-03-02 7:53 ` Nick Roberts [this message]
2008-03-02 5:46 ` Stefan Monnier
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=18378.23775.318854.68572@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=david.reitter@gmail.com \
--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.