-
Notifications
You must be signed in to change notification settings - Fork 6
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
Autoloading #8
Comments
Thanks for your suggestions. A patch is welcome and I will do it when available. |
A possible solution is to create an Elisp file to (require 'literate-elisp)
(literate-elisp-load (format "%sfoo.org" (file-name-directory load-file-name)))
(provide 'foo) Now one can use use-package as usual - |
Okay, so that works for Is there anything |
Maybe we can create an interactive command |
I have added a commit to support autoload to org file. Can you have a test of it, and if all is fine I'll close this issue. |
literate-elisp-load is great, but currently suffers from issues with lexical scope [1] and autoload generation [2]. :( [1] jingtaozf/literate-elisp#6 [2] jingtaozf/literate-elisp#8
How would one lazy load using literate-elisp? I tried
(autoload 'foo "/path/to/foo.org")
, but goteval-buffer: Invalid read syntax: #
On a related note, could you please implement a literate-elisp extension for use-package? Perhaps as a new keyword, or ideally transparently detecting an Org file and preferring to load that.
The text was updated successfully, but these errors were encountered: