Gnus development mailing list
 help / color / mirror / Atom feed
From: Phil Humpherys <phumpherys@utah-inter.net>
Cc: ding@gnus.org
Subject: Re: tm
Date: 24 Aug 1998 13:01:01 -0600	[thread overview]
Message-ID: <x7pvdqb3wy.fsf@utah-inter.net> (raw)
In-Reply-To: Karl Kleinpaste's message of "24 Aug 1998 08:25:41 -0400"

Karl Kleinpaste <karl@jprc.com> writes:

> Phil Humpherys <phumpherys@utah-inter.net> writes:
> > How do you send an attachment,
> > and what are the important lines for .emacs?
> 
> I'm using TM (7.108) under XEmacs, and during message composition,
> there is a menu bar item available, MIME Edit.  That menu will show
> you what you can include; if you insert a file (kbd equivalent, `C-c
> C-x TAB'), it will ask you how to encode the file if it's binary
> (default, base64).
> 
> No extra .emacs stuff needed, other than the (load "mime-setup") you
> must already have in place.
> 

Okay, major progress.  I put (load "mime-setup") in my .emacs
file, and sent a small .gif to myself, successfully using C-c C-x
TAB to insert the file.  But when the email message was
delivered, and I tried to enter the summary buffer, I got the
follow error message in the mini-buffer below:

Invalid coding system: ctext      

I had to kill emacs, comment out the (load "mime-setup") in order
to read the file, which I was then able to do no problem.  So,
currently I have to manually modify .emacs to insert attachments,
and modify it again to read them.  I'm missing something...

-- 
Phil Humpherys <phumpherys@utah-inter.net>   DriverSoft
Unix Systems Administrator                   Mobile: +1.801.725.3257 
WWW/PGPkeys: http://www.spire.com/~humphery


  reply	other threads:[~1998-08-24 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-24  3:58 tm Phil Humpherys
1998-08-24 12:25 ` tm Karl Kleinpaste
1998-08-24 19:01   ` Phil Humpherys [this message]
     [not found]     ` <vxkr9y6qjr5.fsf@pocari-sweat.jprc.com>
1998-08-24 20:03       ` tm Phil Humpherys
1998-08-25  9:26     ` tm Steinar Bang
1998-08-26 18:19       ` tm Dave Love

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=x7pvdqb3wy.fsf@utah-inter.net \
    --to=phumpherys@utah-inter.net \
    --cc=ding@gnus.org \
    /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).