Tél: +33(0)1 69 08 75 40
Fax: +33(0)1 69 08 87 86
Email:
Olivier.Klein<at>cea.fr
Here is the log:
Attachment:
backtrace2.log
Description: Binary data
PS: The problem is more serious than that. Once it occurs, it messes up all my email headers??? PPS: Indeed, it is not related to the content of the .emacs, it might have something to do with the order at which the functions are called. BTW: same symptoms w/ my .gnus: If I do a change to my dot-gnus.el, emacs recompiles the file and the error message disappears during the first use, but then it reappears at subsequent call??? PPPS: I use your message-multiple-frames.el function :-) !!! I have included the email below: I do not notice anything special???
Attachment:
temp
Description: Binary data
Katsumi Yamaoka <yamaoka@xxxxxxx> writes:
>>>>>> In [emacs-w3m : No.10440]
>>>>>> Olivier Klein <oklein@xxxxxx> wrote:
>
>> Here is the log file of the debugger:
>
>> Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
>> w3m-decode-entities(reserve-prop)
>> w3m-fontify()
>> w3m-region(1347 6452 nil "iso-8859-1")
>> mm-inline-text-html-render-with-w3m((#<buffer *mm*<3>>\
>> ("text/html" (charset . "iso-8859-1")) quoted-printable nil nil nil nil nil))
>
> It looks like there's something special in that html message.
> Though it might not relate to whether your dot-emacs.el file is
> compiled or not, I'd like to know why such an error happens.
> Could you load the w3m.el file (not the w3m.elc file) [1] in
> advance and try getting the *Backtrace* again?
>
> [1] M-x load-file RET /some/where/w3m.el RET
>
> Please note that you will have to perform the `C-]' command
> (i.e. `M-x abort-recursive-edit RET') whenever you've seen the
> *Backtrace* buffer in order to initialize the Emacs debugger.
>
>> This might be linked to some incompatibilities w/ my local lisp files ??
>
> I'll look into them later, if needed. Thanks.
>
> Regards,
>