Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Problems with `require' in recent changes
Date: Tue, 11 Dec 2007 07:04:15 -0500	[thread overview]
Message-ID: <84ejdtxwsg.fsf@incoming.verizon.net> (raw)

With the renaming from password.el to password-cache.el, smime.el, sieve-manage.el and mml-sec.el have a sexp like this:

(or (require 'password-cache nil t)
    (require 'password))

This breaks XEmacs 21.4.20 with an error that require does not like
having three arguments.

Since I don't understand what the above call to require is supposed to
do, I cannot produce a proper patch.  For the time being, I've brute
forced a fix by commenting out the above sexp and replacing it with
(require 'password-cache) which is fine for my single user
installation and allows me to do my work today, assuming the issue
remains in 21.4.21 which I have at work.  If I find that it works
there I'll upgrade at home and be done with it, but I wanted to get
the word out early in case it doesn't as I don't have access to my
personal email while at work.

Thanks,

-- 
Dave Goldberg
david.goldberg6@verizon.net




             reply	other threads:[~2007-12-11 12:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 12:04 Dave Goldberg [this message]
2007-12-12  3:12 ` Katsumi Yamaoka
2007-12-12  3:15   ` Glenn Morris
2007-12-12  5:39     ` Katsumi Yamaoka
2007-12-12 15:09       ` Stefan Monnier
2007-12-12 20:45         ` Reiner Steib
2007-12-14  0:07           ` Katsumi Yamaoka
2007-12-16 18:32             ` Reiner Steib
2007-12-16 20:22               ` Miles Bader
2007-12-16 20:51                 ` Reiner Steib
2007-12-17  2:25                   ` Glenn Morris
2007-12-17 18:44                     ` Glenn Morris
2007-12-18  0:29                       ` Katsumi Yamaoka
2007-12-28 19:34                         ` Reiner Steib
2007-12-17 21:45                   ` Dave Goldberg

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=84ejdtxwsg.fsf@incoming.verizon.net \
    --to=david.goldberg6@verizon.net \
    --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).