You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the user doesn't have to call the hooks themselves, I could just "attach" them straight away, i.e. run them when the user calls library(knitrhooks) (see this example).
The text was updated successfully, but these errors were encountered:
That’s really neat! But I guess it depends on where this package ends up going. It could end up catering to different formats (pdf, html, etc.) in which not all hooks will be relevant.
I guess my thoughts behind .onAttach was to load each of the hook functions so the user doesn’t have to, but then that could potentially bloat their environment unnecessarily. So both methods have negatives.
So the user doesn't have to call the hooks themselves, I could just "attach" them straight away, i.e. run them when the user calls
library(knitrhooks)
(see this example).The text was updated successfully, but these errors were encountered: