Gnus development mailing list
 help / color / mirror / Atom feed
From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: Forwarding Mail Messages
Date: 01 Dec 1999 19:42:07 -0500	[thread overview]
Message-ID: <7s4se2uqao.fsf@brutus.mts.jhu.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Wed, 01 Dec 1999 20:47:55 +0100"

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

 [...]

 LMI> An even more general way to do this would be a way to create an
 LMI> nnvirtual group based on an arbitrary subset of messages from
 LMI> various groups.  I don't actually think it would be difficult to
 LMI> implement, but, er, I don't really see much utility here.  One
 LMI> can, instead, just save the messages and then forward the
 LMI> result.

This would be super useful. Something similar VM's virtual
folders. The functionality I am looking for is like that  of Gnus'
gnus-summary-limit-to-* but acting on *all* articles in the group(s)
rather than just the ones visible in the summary. Earlier when I used
VM I had the following as part of my virtual folder specifications:

,----
| (setq vm-virtual-folder-alist
|       (list
|        '("unreplied"
|          (("Inbox")
|           (and (unreplied) (not(label "info")))))
|        ))
`----


i.e, create a virtual folder called "unreplied" by taking messages
from "Inbox" which are unreplied and are not labeled "info". VM can
slurp a subset of messages from a particular file or directory. I miss 
this feature.

-Nevin


  reply	other threads:[~1999-12-02  0:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-24  0:06 Brian May
1999-12-01 19:47 ` Lars Magne Ingebrigtsen
1999-12-02  0:42   ` Nevin Kapur [this message]
1999-12-02  1:19     ` What now? (was: Forwarding Mail Messages) Lars Magne Ingebrigtsen
1999-12-02  2:59       ` What now? Brian May
1999-12-02 16:23         ` Colin Marquardt
1999-12-02 16:56         ` Jody M. Klymak
1999-12-06  4:26           ` Lars Magne Ingebrigtsen
1999-12-06  5:31             ` Brian May
1999-12-07  5:36               ` William M. Perry
1999-12-07  5:59                 ` Brian May
1999-12-07 16:09                   ` William M. Perry
1999-12-08  8:02                     ` nnimap URLs? (Was: What now?) Steinar Bang
1999-12-08 16:08                       ` William M. Perry
1999-12-08 18:02                         ` Simon Josefsson
1999-12-08 18:23                           ` William M. Perry
1999-12-08 17:26                       ` Simon Josefsson
1999-12-10 16:07                         ` William M. Perry
1999-12-08 22:51                     ` What now? Brian May
1999-12-06 17:36             ` Jody M. Klymak
1999-12-06 20:34               ` Bruce Stephens
1999-12-06 22:38               ` Kai Großjohann
1999-12-03 19:12       ` What now? (was: Forwarding Mail Messages) Jody M. Klymak
1999-12-04 17:05         ` Hrvoje Niksic
1999-12-04 22:53           ` Jody M. Klymak
2000-04-21 21:13         ` Lars Magne Ingebrigtsen
2000-04-21 21:05           ` William M. Perry
2000-04-21 21:16             ` Arcady Genkin
2000-04-21 23:32               ` William M. Perry
2000-04-22  9:36             ` Hans de Graaff
1999-12-05 21:46       ` Kai Großjohann
1999-12-05 21:51       ` Kai Großjohann
1999-12-06  1:27       ` Richard Hoskins
1999-12-02  1:48   ` Forwarding Mail Messages Brian May
1999-12-06  4:12     ` Lars Magne Ingebrigtsen

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=7s4se2uqao.fsf@brutus.mts.jhu.edu \
    --to=nevin@jhu.edu \
    /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).