-
Notifications
You must be signed in to change notification settings - Fork 14
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
init.elc #3
Comments
Hey, I'm not sure I understood you correctly. Why do you need to remove Regardless, I had other issues with emacs daemon (at least on macOS), so I adopted another approach: I don't start emacs daemon separately, but instead just launch Emacs when my computer starts. Emacs automatically starts a server (see https://github.com/freetonik/emacs-dotfiles#server). Then I can use Another workaround is to ditch byte-compiling altogether (remove line |
I believe when I update the init.org, init.el gets updated on save, but not init.elc. So the next time I start emacs, it starts with inconsistent init. |
This is what I get whenever I update the init.org file and the init.el. Warning (initialization): An error occurred while loading ‘.../.emacs.d/init.elc’: I hope it shows where the problem can be. "--debug" doesn't show much more meaningful information. |
Can you show your full config? |
This is an ongoing work. @freetonik I switched from spacemacs to this like two weeks ago mostly after listening to your podcast. thank you for it. |
I am not sure if this is reporting of a problem, but maybe a question mostly. I am using this configuration as a baseline for my own configuration. One thing I do is that I start emacs as daemon and also I start an standalone emacs client (graphical one). One thing happens when I change the org-mode config is that it creates or forgets to update the "init.elc" file. So the next time when I start emacs I have to always remove that "init.elc" file. I wonder if this happens to others too, or I am doing something wrong or others do not use emacs --daemon!
The text was updated successfully, but these errors were encountered: