-
Notifications
You must be signed in to change notification settings - Fork 21
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
support byte-compilation of e-max #72
Comments
How should we byte-compile? (byte-recompile-directory e-max-repository 0) Is that enough? Which emacs should we take? The easiest way from the shell would be something like: emacs --execute "(byte-recompile-directory e-max-repository 0)" But this opens a emacs frame and we cannot be sure that |
Byte-compiling creates .elc files. Not every vendor-submodule does ignore *.elc. |
is there a git way to ignore files in submodules? Otherwise I think we should submit pull-requests to ignore *.elc files in the dependent repositories. |
Indeed. The other problem is that when e-max is compiled, modifications on the .el-files are not loaded (the .elc is loaded). Development would not be handy then... |
We need some kind of development mode, which deals with the fact, that there might be compiled *.elc files. I'm not quite sure how a good setup would look like. |
I did not work on that. @jone ? |
I think the
install.sh
andupdate.sh
should byte-compile the e-max installation. This would offer a huge speed benefit when booting up emacs.The text was updated successfully, but these errors were encountered: