Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!ncar!csn!magnus.acs.ohio-state.edu!dnmiller
From: dnmiller@magnus.acs.ohio-state.edu (David Neal Miller)
Newsgroups: comp.mail.elm
Subject: elm and .signature files
Message-ID: <1991May10.162551.2250@magnus.acs.ohio-state.edu>
Date: 10 May 91 16:25:51 GMT
Sender: news@magnus.acs.ohio-state.edu
Organization: The Ohio State University
Lines: 31
Nntp-Posting-Host: bottom.magnus.acs.ohio-state.edu

As a newcomer to elm, I find the way it handles .signature
files to be, well, regrettable.

Unlike mm and rn/trn, elm adds the contents of one's
.signature file to the editable message; that is, invoke
vi and there's the contents of the .signature file,
cluttering up the editing area.  The doesn't seem to be
any alternative to pushing the d*** text down as one
composes and edits, or dG-ing the signature away altogether
and reading it back in (sans leading hyphens) before saving
and quitting.

I thought that the whole point of a .signature file is to
keep it out of the way and have it appended (or not) at
the point of sending the message on its way.  That's why
mm and rn/trn prompts with an "append signature?" type
question.

Am I missing something?  I'm more or less of a novice, and
wouldn't be surprised if I am.  Or is elm just poorly
designed in this respect?  If the latter, what's the hope of
whipping it up to shape in a future revision?

Many thanks in advance for any replies.


-- 
David Neal Miller

Internet: miller.3@osu.edu
Bitnet:   miller.3@ohstmail