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
This is a request for a feature and a proposal to write it myself.
Every time a code is run or submitted to LetCode, I felt it would be helpful to call a hook.
Except for the fact that I cannot locate the line where, for instance, leetcode-solution-mode-hook is called, I am unable to locate any evidence in the code that led me to believe that those hooks already exist.
I would need that to integrate the wakatime-mode melpa package, to keep track on the time spent with every problem.
This feature request is unrelated to the second integration with wakatime, and I would actually work on it later
The text was updated successfully, but these errors were encountered:
I implemented a leetcode-before-submit-hook along with some other hooks for user customizations on my branch (overview of changes here nverno@6a878fd).
However, I made so many changes I haven't decided which to submit as pull requests quite yet.
This is a request for a feature and a proposal to write it myself.
Every time a code is run or submitted to LetCode, I felt it would be helpful to call a hook.
Except for the fact that I cannot locate the line where, for instance,
leetcode-solution-mode-hook
is called, I am unable to locate any evidence in the code that led me to believe that those hooks already exist.I would need that to integrate the wakatime-mode melpa package, to keep track on the time spent with every problem.
This feature request is unrelated to the second integration with wakatime, and I would actually work on it later
The text was updated successfully, but these errors were encountered: