Gnus development mailing list
 help / color / mirror / Atom feed
From: Didier Verna <didier@xemacs.org>
To: david.goldberg6@verizon.net (Dave Goldberg)
Cc: ding@gnus.org
Subject: Re: Replying from an nnir group
Date: Tue, 26 Mar 2013 15:19:47 +0100	[thread overview]
Message-ID: <mux620edz0c.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <muxppyme0y5.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "Tue, 26 Mar 2013 14:37:54 +0100")

I wrote:

> ((cond ((message-news-p)
>         nnimap+gmail:sent-news)
>        ((stringp gnus-newsgroup-name)
>         (cond ((zerop (length gnus-newsgroup-name))
>                nnimap+gmail:sent-mails)
>               ((string-match ^nnir: gnus-newsgroup-name)
>                (aref (aref nnir-artlist 0) 0))
>               (t gnus-newsgroup-name)))
>        (t nnimap+gmail:sent-mails)))
>
>
> Of course, the nnir part is dirty and probably fragile. It will work
> only when doing searches on a single group, but that's a start. In
> fact, I still don't know how to figure out the exact article (which
> one in nnir-artlist) I'm replying to. Maybe an nnir expert knows
> better.

  And in light of the recent replies, I guess I can do

(nnir-article-group (gnus-summary-article-number))

instead, and get a cleaner solution.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com



  reply	other threads:[~2013-03-26 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 10:01 Didier Verna
2013-03-26 12:01 ` Dave Goldberg
2013-03-26 13:37   ` Didier Verna
2013-03-26 14:19     ` Didier Verna [this message]
2013-03-26 13:17 ` Andrew Cohen
2013-03-26 14:12   ` Didier Verna
2013-03-26 13:21 ` Steinar Bang
2013-03-27 13:46 ` Andrew Cohen
2013-04-23 15:44   ` Didier Verna

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=mux620edz0c.fsf@uzeb.lrde.epita.fr \
    --to=didier@xemacs.org \
    --cc=david.goldberg6@verizon.net \
    --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).