From: Steinar Bang <sb@metis.no>
Subject: Problems with sending attachments
Date: 30 May 2001 09:20:49 +0200 [thread overview]
Message-ID: <whu223l3lh.fsf@viffer.computas.no> (raw)
Platform: XEmacs 21.1 (patch 8) "Bryce Canyon" [Lucid] (i386-suse-linux, Mule)
Oort Gnus v0.04 (recent CVS checkout), SuSE-linux
I get a beep and the following message in the minibuffer, when I
attempt to send a message with an attachment:
Wrong number of arguments: #<compiled-function (filename &optional visit beg end replace) "...(144)" [nil conversion-func used-codesys coding-system return-val err (byte-code "
[snip!]
The Gnus and XEmacs, and the rest of the linux installation, was
recently reinstalled after a disk crash, so I thought I may be getting
something from a wrong site-lisp directory (it happened to me
earlier).
I locate-library found that I had a filename.el in a site-lisp
directory. However, removing it, and restarting xemacs and gnus, and
checking that locate-library found something delivered with xemacs had
no effect.
`C-h f' can't find a function called filename.
Can anyone shed any light on this?
Thanx!
next reply other threads:[~2001-05-30 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 7:20 Steinar Bang [this message]
2001-05-30 9:28 ` Kai Großjohann
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=whu223l3lh.fsf@viffer.computas.no \
--to=sb@metis.no \
/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).