Gnus development mailing list
 help / color / mirror / Atom feed
From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: Add another "nndraft" type ?
Date: Thu, 03 Jun 2004 13:15:47 -0400	[thread overview]
Message-ID: <u8zhdts4l6k.fsf@mm117419-pc.MITRE.ORG> (raw)
In-Reply-To: <86n03kha99.fsf@rumba.de.uu.net> (Kai Grossjohann's message of "Thu, 03 Jun 2004 18:33:22 +0200")

>>>>> On Thu, 03 Jun 2004 18:33:22 +0200, Kai Grossjohann <kai@emptydomain.de> said:

> Xavier Maillard <zedek@gnu-rox.org> writes:
>> What I  currently miss  is a  way to keep  a copy  of such  message that
>> would be the base for other messages.  I call that template but I am not
>> sure of the terminology.

> Perhaps you can "just" use abbrevs?  I think that's a low-tech
> mechanism that's underused.

This can be painful if you have a lot of them, especially if some are
similar and you mix up which you want.

> Or keep each template in a file and use C-x i.

For a while I had a couple of nndraft articles that held initial
contents of things like scheduled outage messages and the like.  I
would B C them and then D E the copy.  That got old the first time I
accidentally ran D E on the main copy, though :-)

> Or use skeleton to generate them.

Not sure what you mean by skeleton, but eventually I discovered
tempo.el which is how I handle these things now.

-- 
Dave Goldberg
david.goldberg6@verizon.net





  reply	other threads:[~2004-06-03 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 21:02 Xavier Maillard
2004-06-03 16:33 ` Kai Grossjohann
2004-06-03 17:15   ` David S Goldberg [this message]
2004-06-03 19:16     ` Xavier Maillard
2004-06-03 20:16       ` David S Goldberg
2004-06-04  6:13     ` Kai Grossjohann
2004-06-03 17:40   ` Xavier Maillard

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=u8zhdts4l6k.fsf@mm117419-pc.MITRE.ORG \
    --to=david.goldberg6@verizon.net \
    /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).