Uwe Brauer <oub(a)mat.ucm.es> wrote:
On 29 Sep 2003, james(a)xemacs.org wrote:
>
> Can you please attach text as MIME type text/plain instead of
> application/octet-stream? That way I don't have to save it to a
> file just to look at it. Thanks!
>
Ok, sorry I never know what is best, sometimes netscape users seem to
have difficulties with text/plain
Oh really? I didn't know that. Well then, you can't win. If you
attach as text/plain the Netscape users will complain, and if you attach
as application/octet-stream the Gnus users will complain. Welcome to
hell.:-)
I just need this part of the backtrace:
Signaling: (void-function nil)
nil("XEmacs Beta <xemacs-beta(a)xemacs.org>" "[Bug: 21.4.12] file
" nil nil nil nil nil)
compose-mail("XEmacs Beta <xemacs-beta(a)xemacs.org>" "[Bug:
21.4.12] file " nil)
[snip]
> 1) What is the value of mail-user-agent in your XEmacs?
vm-user-agent
> 2) What is the value of (get mail-user-agent 'composefunc) in your
> XEmacs?
vm-compose-mail
If this is the problem kyle jones should know about it.
Weird. On my system, at least, compose-mail is defined in simple.el as
follows (minus the docstring):
(defun compose-mail (&optional to subject other-headers continue
switch-function yank-action send-actions)
(interactive
(list nil nil nil current-prefix-arg))
(let ((function (get mail-user-agent 'composefunc)))
(funcall function to subject other-headers continue
switch-function yank-action send-actions)))
From the backtrace above, this appears to mean that `function' is
nil,
which means that (get mail-user-agent 'composefunc) should have returned
nil for you. Since you got vm-compose-mail instead, I don't know what
to think. Does C-h f compose-mail indicate that it comes from
simple.el? Can you step through that function in the debugger and see
if anything obvious jumps out at you?
--
Jerry James
http://www.ittc.ku.edu/~james/