From: Romain Francoise <romain@orebokech.com>
Subject: Re: reply format
Date: Tue, 16 Aug 2005 08:26:54 +0200 [thread overview]
Message-ID: <87y872wg5t.fsf@pacem.orebokech.com> (raw)
In-Reply-To: <8764u68wax.fsf@gmail.com> (Sean Sieger's message of "Mon, 15 Aug 2005 22:12:06 -0400")
Sean Sieger <sean.sieger@gmail.com> writes:
> I have been making time to look through the manual to find
> the hack to change the reply and follow-up formats from '>'
> to indented. What is the correct terminology to be looking
> for?
It's in the Message manual, see the message-yank-* variables.
What you're looking for is:
(setq message-yank-prefix nil)
--
Romain Francoise <romain@orebokech.com> | All you've been is a piece of
it's a miracle -- http://orebokech.com/ | blood wrapped in skin.
next prev parent reply other threads:[~2005-08-16 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 2:12 Sean Sieger
2005-08-16 6:26 ` Romain Francoise [this message]
2005-08-16 11:17 ` Sean Sieger
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=87y872wg5t.fsf@pacem.orebokech.com \
--to=romain@orebokech.com \
/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).