From: NAGY Andras <nagya@inf.elte.hu>
Subject: Re: using base64
Date: 17 Jan 2001 11:56:15 +0100 [thread overview]
Message-ID: <87r922h2gg.fsf@lovi.inf.elte.hu> (raw)
In-Reply-To: <2nbst6zz2o.fsf@tiger.jia.vnet>
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> > (("text/x-patch" 8bit) ("text/.*" qp-or-base64)
> > ("message/rfc822" 8bit) ("application/emacs-lisp" 8bit)
> > ("application/x-patch" 8bit) (".*" base64))
> >
> >
> > But Gnus still sends out a 7bit application/rtf attachment in
> > plaintext. How do I achieve the desired effect?
>
> I suspect that there is an old base64.el in your load path. Check
> function base64-encode-region. If there are only two arguments, that's
> it.
`base64-encode-region' is an interactive Lisp function
-- loaded from "base64"
(base64-encode-region START END &optional NO-LINE-BREAK)
Note that base64 actually works if it really needs to (that is,
sending a binary file as an attachment); what I want is to use base64
even if it does not seem necessary.
Andras
prev parent reply other threads:[~2001-01-17 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 16:26 NAGY Andras
2001-01-17 2:34 ` ShengHuo ZHU
2001-01-17 10:56 ` NAGY Andras [this message]
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=87r922h2gg.fsf@lovi.inf.elte.hu \
--to=nagya@inf.elte.hu \
/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).