From: Xavier Maillard <zedek@gnu-rox.org>
Subject: tc advantages over message citation functions ?
Date: Fri, 24 Sep 2004 19:00:36 +0200 [thread overview]
Message-ID: <plop87sm97sitn.fsf@gnu-rox.org> (raw)
Plop fellows,
I use tc to cite but as I am cleaning up somehow my .gnus, I am
asking whether it is worth keeping tc for this or use the
standard message package. In fact, AFAIK, tc is no longer
maintained/modified whereas message mode is still evolving and
ehanced.
WYO ?
P.S: love the latest message-cide-article-* feature
--
GNUSFR.ORG http://gnusfr.org/
EMACSFR.ORG http://emacsfr.org/
Xavier Maillard Tel: +33 6 68 04 64 37
reply other threads:[~2004-09-24 17:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=plop87sm97sitn.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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).