Skip to content
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

Open
senny opened this issue Oct 1, 2011 · 7 comments
Open

support byte-compilation of e-max #72

senny opened this issue Oct 1, 2011 · 7 comments

Comments

@senny
Copy link
Owner

senny commented Oct 1, 2011

I think the install.sh and update.shshould byte-compile the e-max installation. This would offer a huge speed benefit when booting up emacs.

@jone
Copy link
Collaborator

jone commented Oct 1, 2011

How should we byte-compile?
The easiest way I know is:

(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 emacs is the emacs the user wants to use...

@jone
Copy link
Collaborator

jone commented Oct 1, 2011

Byte-compiling creates .elc files. Not every vendor-submodule does ignore *.elc.
So if you do not ignore .elc globally in git, the submodules are dirty by default...

@senny
Copy link
Owner Author

senny commented Oct 1, 2011

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.

@jone
Copy link
Collaborator

jone commented Oct 1, 2011

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...

@senny
Copy link
Owner Author

senny commented Oct 1, 2011

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.

@tonini
Copy link
Collaborator

tonini commented Aug 26, 2013

@senny @jone what is the state about this issue?

@senny
Copy link
Owner Author

senny commented Aug 26, 2013

I did not work on that. @jone ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants