Re: Marking as already read when using gcc-self?

[Lloyd Zusman <ljz@asfast.com>]

Hrvoje Niksic <hniksic@srce.hr> writes:

> Justin Sheehy <justin@linus.mitre.org> writes:
> 
> > Lloyd Zusman <ljz@asfast.com> writes:
> > 
> > > Then, when entering summary mode, some routine (which one? ... well,
> > > I'll dig around and find it if no one can make a suggestion) could
> > > then recognize this `X-Gnus-Gcc-Action' header and perform the
> > > specified action.
> > 
> > Hm.
> > 
> > So, one could send me mail with a X-Gnus-Gcc-Action: <something>
> > header and make Gnus do something for me when it processes that
> > mail?
> > 
> > I don't think I'd like that very much.
> 
> Why not?  I think it's be totally hip -- see the headers.  :-)

Sure ... why not!  Might as well allow any and all sexp's that appear
data portion of that header to be evaluated, instead of just
interpreting a few specific actions. :)

But yes, I agree with all of you who pointed out that even with a few
specific action keywords, the header is indeed a bad idea, given the
fact that anyone could send a message with that header already
defined.

Hmmm ... OK.  What about this idea:

Create a new group parameter, perhaps called `gcc-action'.  It can
take only a few specified values such as 'tick, 'mark-read, etc.

See to it that `gnus-inews-do-gcc' in `gnus-msg.el' has access to the
value of `gcc-action' for the given group (I have to look more closely
at the code to determine the details as to how to get that value into
`gnus-inews-do-gcc', but I'm certain that this can be done).  If this
`gcc-action' value is present, pass it as a new parameter to the
invocation of `gnus-request-accept-article' near the end of this
routine.

Then, add another optional argument called `action' to the function
`gnus-request-accept-article' in `gnus-int.el'.  If this optional
argument is `nil', then this function will behave as it currently
does.  However, if `action' is set to one of the possible values
of `gcc-action', then tick or mark the article accordingly after
the `funcall' at the end of `gnus-request-accept-article' returns
(the article number of the new article should be contained within
the return value of this funcall, and this plus the group name
should allow us to set the appropriate ticking or marking flags).

Any comments?


-- 
 Lloyd Zusman
 ljz@asfast.com