Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: EasyPG menu to mml.el update breaks XEmacs
Date: Mon, 24 Mar 2008 20:34:21 +0900	[thread overview]
Message-ID: <b4mzlsocq4i.fsf@jpl.org> (raw)
In-Reply-To: <v9iqzhw20n.fsf@marauder.physik.uni-ulm.de>

>>>>> Reiner Steib wrote:
> On Thu, Mar 20 2008, Dave Goldberg wrote:

>> Well so much for that - easymenu is not part of a separate package.

> Probably it is in the xemacs-base package.

No, it's in lisp/ .  But I tried the most recent No Gnus on
XEmacs 21.4.21 and have no such problem.

>>>>> Dave Goldberg wrote:
[...]
> Debugger entered--Lisp error: (error "unknown menu item keyword" :visible...
>   signal(error ("unknown menu item keyword" :visible ["Externalize Attach...
[...]
>   easy-menu-add(("Attachments" ["Attach File..." mml-attach-file t] ["Attac\
> h Buffer..." mml-attach-buffer t] ["Attach External..." mml-attach-external\
>  t] ["Externalize Attachments" (lambda nil ... ... ...) :visible (and ...
>   mml-mode()
>   message-mode()

I don't know why, but `:visible' should not appear there because
the source code has been designed so as not to use it as follows:

(easy-menu-define
  mml-menu mml-mode-map ""
[...]
     ,@(if (featurep 'xemacs) nil
	 '(:visible (and (boundp 'gnus-gcc-externalize-attachments)
			 (memq gnus-gcc-externalize-attachments
			       '(all t nil)))))

My guess is that your mml.elc was compiled by ?macs that returns
nil for (featurep 'xemacs).



  reply	other threads:[~2008-03-24 11:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 14:03 Dave Goldberg
2008-03-20 18:19 ` Reiner Steib
2008-03-20 20:26   ` Dave Goldberg
2008-03-20 20:36     ` Dave Goldberg
2008-03-20 20:53       ` Reiner Steib
2008-03-24 11:34         ` Katsumi Yamaoka [this message]
2008-03-24 12:38           ` Reiner Steib

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=b4mzlsocq4i.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).