From: Paul Stevenson <p.stevenson@surrey.ac.uk>
Subject: Re: Minimum emacs version for Oort
Date: 21 Jan 2002 14:40:34 +0000 [thread overview]
Message-ID: <i5k7kqbydgd.discriminatory@wigner.ph.surrey.ac.uk> (raw)
In-Reply-To: <iluy9irvll1.fsf@extundo.com>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
S Josefsson writes:
> Paul Stevenson <p.stevenson@surrey.ac.uk> writes:
>
> > Hello,
> >
> > Is there an official minimum emacs version required for ognus? As of
> > cancel-locks being added, my 20.3.1 seems not good enough:
>
> The manual says Emacs 20.3 or XEmacs 20.4 or later, so if those
> doesn't work, it is a bug.
Oh. Oh yes. My bad.
> > While compiling the end of the data in file
> > [...]/emacs/ognus/lisp/canlock.el: ** the function
> > base64-encode-string is not known to be defined.
> >
> > So I can't send news... Short of persuading the sysadmin to upgrade
> > emacs, which I know he'd put at the bottom of a large pile of jobs,
> > am I restricted to older gnusæ?
>
> No. Does your emacs have `base64-encode-region'? As a workaround put
> gnus/contrib in your load path.
Again, my bad (as they say these days). I jumped to the wrong
conclusion about the above message. It finds the base64 stuff just
fine.
Here's the backtrace of what happens when it fails
[-- Attachment #2: backtrace --]
[-- Type: application/octet-stream, Size: 596 bytes --]
next prev parent reply other threads:[~2002-01-21 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 13:41 Paul Stevenson
2002-01-21 14:13 ` Simon Josefsson
2002-01-21 14:36 ` Kai Großjohann
2002-01-21 15:33 ` Simon Josefsson
2002-01-21 15:41 ` Kai Großjohann
2002-01-21 16:13 ` Simon Josefsson
2002-01-21 16:35 ` Paul Stevenson
2002-01-22 9:45 ` Kai Großjohann
2002-01-22 9:48 ` Kai Großjohann
2002-01-23 14:31 ` Paul Stevenson
2002-01-21 16:35 ` Kai Großjohann
2002-01-21 16:50 ` Paul Stevenson
2002-01-21 17:23 ` Simon Josefsson
2002-01-21 18:15 ` Lars Magne Ingebrigtsen
2002-01-21 14:40 ` Paul Stevenson [this message]
2002-01-21 19:59 ` Lars Magne Ingebrigtsen
2002-01-21 21:12 ` Simon Josefsson
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=i5k7kqbydgd.discriminatory@wigner.ph.surrey.ac.uk \
--to=p.stevenson@surrey.ac.uk \
/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).