Gnus development mailing list
 help / color / mirror / Atom feed
From: Vincent Bernat <bernat@luffy.cx>
To: Matt Ford <matt@dancingfrog.co.uk>
Cc: ding@gnus.org
Subject: Re: Cycling gnus-posting-styles when composing
Date: Mon, 09 Jul 2012 19:48:07 +0200	[thread overview]
Message-ID: <m3ipdwkeqw.fsf@neo.luffy.cx> (raw)
In-Reply-To: <87obnolxew.fsf@rss01.mhs.man.ac.uk> (Matt Ford's message of "Mon, 09 Jul 2012 17:19:35 +0100")

 ❦  9 juillet 2012 18:19 CEST, Matt Ford <matt@dancingfrog.co.uk> :

> Sometimes I wish to cycle through the various accounts that I've got
> configured to read with Gnus when all ready composing a mail.
>
> Changing the sig, Gcc, from is a bit of a pain.  Am I missing something
> obvious?  How may I cycle through gnus-posting-styles?

I am using gnus-identities for this purpose. You can get it from here:
 https://github.com/renard/gnus-identities
-- 
panic("floppy: Port bolixed.");
	2.2.16 /usr/src/linux/include/asm-sparc/floppy.h



  reply	other threads:[~2012-07-09 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 16:19 Matt Ford
2012-07-09 17:48 ` Vincent Bernat [this message]
2012-07-09 20:57 ` John Wiegley

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=m3ipdwkeqw.fsf@neo.luffy.cx \
    --to=bernat@luffy.cx \
    --cc=ding@gnus.org \
    --cc=matt@dancingfrog.co.uk \
    /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).