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 17:13:52 +0100 [thread overview]
Message-ID: <iluzo37u1fj.fsf@extundo.com> (raw)
In-Reply-To: <vafadv7k8ya.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 21 Jan 2002 16:41:33 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>>
>>> The base64.el there does not have base64-encode-string, so
>>> that won't help. >> >> Oops. Paul, does the following patch
>>> work?
>
> I'm not sure if Emacs 20.3 already has base64 support in C code.
Perhaps only elisp. MIME etc needs some kind of base64 support.
Paul, which functions does C-h f base64 TAB TAB expand to?
> If not, then I guess that it would be better to define
> base64-{de,en}code-string in base64.el, don't you think?
Well, contrib/base64.el isn't part of the "real" Gnus
distribution, or is it? (Due to copyright reasons.) If it isn't,
it probably makes sense to include the wrapper in a file that is
part of the real distribution. Or?
But now that I actually look in contrib/base64.el my copy do have
b-{d,e}-string. So it would work as a workaround. Does your copy
differ?
next prev parent reply other threads:[~2002-01-21 16:13 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 [this message]
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
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=iluzo37u1fj.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).