vac241j@monu6.cc.monash.edu.au (Anthony Baxter) (12/10/90)
Ok, here's my problem/question... I recieve a few mailing lists, and want to forward them to a few other people on this system. I'd like to be able to do something like pick -f mailing-list | pick (!forwarded) | mail -f userlist I can pick all forwarded stuff with 'pick -h status f', but I have been unable to work out how to select 'not something'... Any help appreciated.. Anthony -- Wizards dont like philosophy very much. | Robotics and Digital As far as they are concerned, one | Technology, Monash hand clapping makes a noise like 'cl'. | University. vac241j@monu6.cc.monash.edu.au uunet!munnari!monu6.cc.monash.edu.au!vac241j
argv@Eng.Sun.COM (Dan Heller) (12/10/90)
In article <1990Dec10.062259.16862@monu6.cc.monash.edu.au> vac241j@monu6.cc.monash.edu.au (Anthony Baxter) writes: > I can pick all forwarded stuff with 'pick -h status f', but I have been unable > to work out how to select 'not something'... The "-x" option inverts the search. However, I don't recommend using "pick -h status f" to determine the status of messages. This header doesn't have "updated" information -- that is, anything you do in your current mush session is not reflected in the Status header until you update. Besides, it's slower than doing it the right way, which is to the "flags" command. In this case, "flags f" ... to get all the messages that *aren't* forwarded, you could do * { `flags f` } * = all messages, the {}'s means "except" the messages inside. The messages "inside" are those returned by the flags command -- specifically, the messages that have been forwarded. The result is a list of all messages that have not been forwarded. --dan
vac241j@monu6.cc.monash.edu.au (Anthony Baxter) (12/10/90)
argv@Eng.Sun.COM (Dan Heller) writes: >In article <1990Dec10.062259.16862@monu6.cc.monash.edu.au> vac241j@monu6.cc.monash.edu.au (Anthony Baxter) writes: >>I can pick all forwarded stuff with 'pick -h status f', but I have been unable >>to work out how to select 'not something'... >The "-x" option inverts the search. However, I don't recommend using >"pick -h status f" to determine the status of messages. This header >doesn't have "updated" information -- that is, anything you do in your >current mush session is not reflected in the Status header until you >update. Besides, it's slower than doing it the right way, which is to >the "flags" command. In this case, "flags f" ... >to get all the messages that *aren't* forwarded, you could do > * { `flags f` } >* = all messages, the {}'s means "except" the messages inside. >The messages "inside" are those returned by the flags command -- >specifically, the messages that have been forwarded. The result >is a list of all messages that have not been forwarded. >--dan I tried this, however, it doesn't seem to work. If I type " * { ` flags f ` } | headers " it gives me _all_ messages in my mailbox, not just the forwarded ones. From RTFM'ing, it seems that flags is used to set flags, it mentions nothing about reading them. What am I doing wrong? (btw, Im running 7.2.0, in command-line mode) Thanks, Anthony -- Wizards dont like philosophy very much. | Robotics and Digital As far as they are concerned, one | Technology, Monash hand clapping makes a noise like 'cl'. | University. vac241j@monu6.cc.monash.edu.au uunet!munnari!monu6.cc.monash.edu.au!vac241j
argv@turnpike.Eng.Sun.COM (Dan Heller) (12/12/90)
In article <1990Dec10.153108.10024@monu6.cc.monash.edu.au> vac241j@monu6.cc.monash.edu.au (Anthony Baxter) writes: > argv@Eng.Sun.COM (Dan Heller) writes: > > >to get all the messages that *aren't* forwarded, you could do > > * { `flags f` } > > I tried this, however, it doesn't seem to work. > If I type " * { ` flags f ` } | > headers " it gives me _all_ messages in my mailbox, not just the forwarded > ones. From RTFM'ing, it seems that flags is used to set flags, it mentions > nothing about reading them. OOOPS! Sorry about that -- I was thinking about "setting" the messages, which, of course, is completely different from what you want. My mistake. I was thinking of using the special headers commands such as :n (for new messages), :d (for deleted messages), etc... however, none of these include forwarded message specifications, so this is a deficiency that should be fixed. I apologize. Hopefully, we'll get that in the next (upcoming) patch. -- dan ---------------------------------------------------- O'Reilly && Associates argv@sun.com / argv@ora.com Opinions expressed reflect those of the author only.