Re: Hooks for moving an article and for setting it expirable

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Christopher Culver <crculver@christopherculver.com> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> Christopher Culver <crculver@christopherculver.com> writes:
>>> Does Gnus have a way of accessing messages in other groups than what
>>> is visible in the summary buffer? Of course, the article number will
>>> change in the group to which the message is moved. Or is there a way
>>> to run the gnus-article-move-hook function *prior* to the moving of
>>> the message?
>>
>> There are several dynamic variables bound during
>> `gnus-summary-move-article' that you might be able to use. In the
>> message moving loop, the variables to-group and to-article *ought* to be
>> bound to the destination group, and the message's new article number in
>> that group. Maybe try using those variables in your hook function to
>> find the article at its new location?
>
> If the Gnus internals create a variable referring to the to-article, how
> do I access it? Attempting to do perform an action with a variable
> "to-article" produces the error:
>
> Symbol's value as variable is void: to-article

Sorry, I wasn't looking closely enough at the code -- to-article is
already out of scope by the time the hook is run.

> So, the only variables I seem to be able to access are the ones passed
> by gnus-summary-article-move-hook to the hooked function: (action
> data-header from &optional to method). And here the value of "to" is
> only the destination group, not the destination message.

Yup, unfortunately I don't see any way of getting at the new article
number, it's just not present. It would make a lot of sense to me to
have that available to the hook functions, but it's not possible right
now. There might be some objection to changing the calling signature of
the hook functions, as well...

Eric