From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Add message-id in message-citation-line-format
Date: Wed, 04 Jul 2007 20:32:39 +0900 [thread overview]
Message-ID: <b4mtzskxv3c.fsf@jpl.org> (raw)
In-Reply-To: <m2tzskzc7g.fsf@cam.ac.uk>
>>>>> In <m2tzskzc7g.fsf@cam.ac.uk> Leo wrote:
> There is one common citation line format that is not supported by
> message-citation-line-format, for example:
> ,----
>| In <mux3b1zx092.fsf@uzeb.lrde.epita.fr> Didier Verna wrote:
> `----
> Can we add a letter for message-id?
I use the MU-CITE package[1], that is fully customizable. Though
there is no manual, the comment at the beginning of the mu-cite.el
file describes briefly how to use it. You can customize some
options including `mu-cite-top-format'. The "In ID NAME wtote:"
form is the default but you are required to be skillful in ELisp
if you want to make it complicated (please don't ask me how to do
it ;-).
[1] http://www.jpl.org/elips/mu/
next prev parent reply other threads:[~2007-07-04 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 10:37 Leo
2007-07-04 11:32 ` Katsumi Yamaoka [this message]
2007-07-04 12:05 ` Leo
2007-07-04 12:03 ` Leo
2007-07-04 18:34 ` Reiner Steib
2007-07-04 22:28 ` Leo
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=b4mtzskxv3c.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).