From: Michael Grubb <mg@duke.edu>
Subject: Re: Red .53 and TM 7.93 (any problems?)
Date: 01 Nov 1996 13:40:42 -0500 [thread overview]
Message-ID: <vw1vibp64lx.fsf@cambot.oit.duke.edu> (raw)
In-Reply-To: Brian Oneill's message of 01 Nov 1996 10:01:53 -0600
Brian Oneill <btoneill@member.com> writes:
> Well, i'm using .53 and tm 7.92 and i don't have any problems
> as of yet. Except that i can't get it to add my .sig automatically.
This works for me in v0.52 (am about to try .53) and tm7.90:
(setq message-signature '(concat "first line
second line
\"quoted material\"\n"))
-- Mike
--
Michael Grubb <mg@duke.edu>
Duke University Office of Information Technology
phone +1 919 660 6903 / 409 North Building, Durham NC 27708-0132 USA
"Science does not remove the terror of the gods."
next prev parent reply other threads:[~1996-11-01 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-01 14:36 Robert Nicholson
1996-11-01 16:01 ` Brian Oneill
1996-11-01 18:40 ` Michael Grubb [this message]
1996-11-01 18:51 ` David Blacka
1996-11-07 17:19 ` Help! tm problem with .55 Brian Oneill
1996-11-07 22:17 ` Steven L Baur
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=vw1vibp64lx.fsf@cambot.oit.duke.edu \
--to=mg@duke.edu \
/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).