From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: (provide 'nnmaildir)
Date: 04 Oct 2000 21:52:34 +0200 [thread overview]
Message-ID: <iluk8boidtp.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <m3vgv85rjb.fsf@multivac.student.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> > Wasn't `nnfoo-request-set-mark' enough? nnimap store marks on the
> > imap server.
>
> I never got an answer to my question:
> -request-set-mark isn't documented, AFAICT, at least not in the 5.7
> info. How does it work?
>From current documentation:
`(nnchoke-request-set-mark GROUP ACTION &optional SERVER)'
Set/remove/add marks on articles. Normally Gnus handles the
article marks (such as read, ticked, expired etc) internally, and
store them in `~/.newsrc.eld'. Some backends (such as IMAP)
however carry all information about the articles on the server, so
Gnus need to propagate the mark information to the server.
ACTION is a list of mark setting requests, having this format:
(RANGE ACTION MARK)
Range is a range of articles you wish to update marks on. Action
is `set', `add' or `del', respectively used for removing all
existing marks and setting them as specified, adding (preserving
the marks not mentioned) mark and removing (preserving the marks
not mentioned) marks. Mark is a list of marks; where each mark is
a symbol. Currently used marks are `read', `tick', `reply',
`expire', `killed', `dormant', `save', `download' and `unsend',
but your backend should, if possible, not limit itself to these.
Given contradictory actions, the last action in the list should be
the effective one. That is, if your action contains a request to
add the `tick' mark on article 1 and, later in the list, a request
to remove the mark on the same article, the mark should in fact be
removed.
An example action list:
(((5 12 30) 'del '(tick))
((10 . 90) 'add '(read expire))
((92 94) 'del '(read)))
The function should return a range of articles it wasn't able to
set the mark on (currently not used for anything).
There should be no result data from this function.
next prev parent reply other threads:[~2000-10-04 19:52 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 23:10 Paul Jarc
2000-07-14 23:47 ` Steve Harris
2000-07-15 0:56 ` Paul Jarc
2000-07-16 1:14 ` Steve Harris
2000-07-16 12:44 ` Simon Josefsson
2000-07-17 2:43 ` Steve Harris
2000-07-17 18:28 ` Paul Jarc
2000-07-18 9:04 ` Kai Großjohann
2000-07-18 10:16 ` Simon Josefsson
2000-07-18 15:34 ` Steve Harris
2000-07-18 16:34 ` Simon Josefsson
2000-07-18 16:48 ` Kai Großjohann
2000-07-19 15:36 ` Steve Harris
2000-07-20 14:19 ` Paul Jarc
2000-07-24 20:10 ` Paul Jarc
[not found] ` <vafittodfig.fsf@lucy.cs.uni-dortmund.de>
2000-07-31 16:42 ` Paul Jarc
2000-08-01 16:03 ` Paul Jarc
2000-08-02 14:51 ` Paul Jarc
2000-08-03 14:58 ` Paul Jarc
2000-08-04 15:44 ` Paul Jarc
2000-08-07 22:35 ` Paul Jarc
2000-08-11 15:01 ` Paul Jarc
2000-08-11 21:07 ` Kai Großjohann
2000-08-11 21:34 ` Paul Jarc
2000-08-13 16:08 ` Kai Großjohann
2000-09-04 3:51 ` Paul Jarc
2000-09-04 4:20 ` Paul Jarc
2000-09-04 8:26 ` Simon Josefsson
2000-09-05 18:49 ` Paul Jarc
2000-09-21 17:30 ` Paul Jarc
2000-09-21 21:30 ` Kai Großjohann
2000-09-21 22:43 ` Paul Jarc
2000-07-15 0:15 ` Simon Josefsson
2000-07-15 0:51 ` Paul Jarc
2000-07-15 1:21 ` Simon Josefsson
2000-07-15 1:24 ` Russ Allbery
2000-07-15 11:45 ` Kai Großjohann
2000-07-15 13:12 ` Simon Josefsson
2000-07-15 11:43 ` Kai Großjohann
2000-07-16 21:34 ` Paul Jarc
2000-07-16 21:47 ` Kai Großjohann
2000-07-17 18:17 ` Paul Jarc
2000-09-28 16:05 ` Paul Jarc
2000-09-28 18:46 ` Paul Jarc
2000-10-04 18:06 ` Paul Jarc
2000-10-04 18:21 ` Paul Jarc
2000-10-04 19:31 ` Simon Josefsson
2000-10-04 19:34 ` Paul Jarc
2000-10-04 19:52 ` Simon Josefsson [this message]
2000-10-04 20:32 ` Paul Jarc
2000-10-05 8:57 ` Simon Josefsson
2001-04-11 16:10 ` Paul Jarc
2001-04-15 3:57 ` Paul Jarc
2001-04-17 0:55 ` Paul Jarc
2001-04-24 15:11 ` Paul Jarc
2001-04-25 13:42 ` Paul Jarc
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=iluk8boidtp.fsf@barbar.josefsson.org \
--to=simon@josefsson.org \
--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).