Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: Paul Stevenson <p.stevenson@surrey.ac.uk>, ding@gnus.org
Subject: Re: Minimum emacs version for Oort
Date: Mon, 21 Jan 2002 18:23:10 +0100	[thread overview]
Message-ID: <ilulmerty81.fsf@extundo.com> (raw)
In-Reply-To: <vafy9ir1x1v.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 21 Jan 2002 17:35:56 +0100")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Paul, what happens when you do the following?
>
> emacs -q -no-site-file -batch --eval "(print (featurep 'base64))"
>
> If it prints t, then Emacs has base64 support in the C code. 
> Then a workaround for base64-encode-string should be in canlock. 
> If it prints nil, then (require 'base64) in canlock.el should do 
> the trick.

Emacs 20.3 doesn't seem to have base64 at all, neither in C nor in 
elisp.  The MIME stuff in Gnus seems to require Base64 though. 
Should the requirement in the manual be bumped to Emacs 20.4? 
That version does have base64 support (in C).




  parent reply	other threads:[~2002-01-21 17:23 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 [this message]
2002-01-21 18:15               ` Lars Magne Ingebrigtsen
2002-01-21 14:40   ` Paul Stevenson
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=ilulmerty81.fsf@extundo.com \
    --to=jas@extundo.com \
    --cc=ding@gnus.org \
    --cc=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).