Hi Christian,
thanks for testing.
Christian Schwarzgruber writes:
> thanks for that change. But unfortunate this one doesn't work for the
> org-agenda-filter-by-* functions. However, it would work for all
> org-agenda-filter* functions, if the hook would be called at the end of
>
Hi Bestian,
Bastien writes:
> Yes, this one makes sense, I've added `org-agenda-filter-hook' for
> functions that you need to run right after `org-agenda-filter' has
> been called.
thanks for that change. But unfortunate this one doesn't work for the
org-agenda-filter-by-* functions. However,
Hi Christian,
Christian Schwarzgruber writes:
> or perhaps add a new hook `org-agenda-filter(-(apply|after))?-hook`?
Yes, this one makes sense, I've added `org-agenda-filter-hook' for
functions that you need to run right after `org-agenda-filter' has
been called.
Thanks for the suggestion!
Hi Bastien,
thank you! That would reduce it to one advice.
However, I would still need to advice the function org-agenda-filter-apply since
it doesn't call `org-agenda-finalize`. Would it make sense to call the hook
org-agenda-finalize-hook at the and of org-agenda-filter-apply or perhaps add a
Hi Christian,
you might want to have a look at org-agenda-finalize-hook, though I'm
not sure it can help, I'm not familiar with org-super-agenda enough.
HTH,
--
Bastien
Hi Bastien,
Bastien writes:
> Christian Schwarzgruber writes:
>
>> The question is now, is it possible to further reduce the advised
>> functions to just one advised function.
>
> I am sorry, I don't understand what change does it imply on Org's
> side. Can you explain us a bit more?
Nothing
Hi Christian,
Christian Schwarzgruber writes:
> The question is now, is it possible to further reduce the advised
> functions to just one advised function.
I am sorry, I don't understand what change does it imply on Org's
side. Can you explain us a bit more?
Thanks!
--
Bastien
