From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Group Parameters: gcc-self . "string"
Date: Sun, 24 Nov 2013 20:21:10 -0500 [thread overview]
Message-ID: <877gbxe0op.fsf@newsguy.com> (raw)
Using the builtin group parameters item: (gcc-self . "string")
Should I be able to do this:
(gcc-self . "nnimap+hput3fm:INBOX.some group, nnimap+hput3fm:INBOX.other group")
That is, Gcc multiple groups by inserting them as "string" with `G p'?
When I try that I get a Gcc in the headers of new message with only
the part before the comma. So, in the headers I get
Gcc: "nnimap+hput3fm:INBOX.some group"
I've also tried escaping the comma like so:
(gcc-self . "nnimap+hput3fm:INBOX.some group\\, nnimap+hput3fm:INBOX.other group")
And even went really crazy and tried this.
... "\\"nnimap+hput3fm:INBOX.some group\\"\\, \\"nnimap+hput3fm:INBOX.other group\\"")
The last thing above fails with an error:
byte-code: Invalid read syntax: ". in wrong context"
Is there a syntax that will allow me to enter multiple groups to be Gcc'ed?
next reply other threads:[~2013-11-25 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 1:21 Harry Putnam [this message]
2013-11-25 7:57 ` Katsumi Yamaoka
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=877gbxe0op.fsf@newsguy.com \
--to=reader@newsguy.com \
--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).