-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid loading Org on init #120
Comments
Maybe. Lots of things in Emacs use Org, and loading it once means not having to call |
Few people may bring up the issue here because they don't know it's magit-todos, like how I at first had difficulty figuring out why Emacs starts slow in the first place, and it took some time to figure out that something is loading Org, and then some time to figure out whodunit. Anyway, does |
So you mean that |
With Org: 1.8s by stopwatch (Doom dashboard reports 1.5s, Without Org: 1.2s by stopwatch (Doom dashboard reports 0.9s, I guess it doesn't fit all definitions of "slow", but it's noticeable to me. Sorry, I can't offer advice on whether or not you should move the |
Second that the requirement to load org early is stopping me from using this (otherwise) excellent package. The reason why has to do with the emacs-jupyter package, not startup time |
Ok, if it's presenting a problem, I don't mind making that change. Most cases won't involve an Org file anyway, and in the few that do, the change shouldn't be a performance problem, I think. |
That should do it. Please let me know if the problem is solved for you. |
I don't know if you consider this relevant or if I should make an issue with Doom Emacs instead. Perhaps our
use-package
declarations should defer magit-todos until first time they call up a magit buffer anyway.But if it's possible within this codebase to not load Org immediately, maybe it's a good feature? Takes work off the shoulders of Doom and other community configs.
The text was updated successfully, but these errors were encountered: