From: Sebastian Rose <sebastian_rose@gmx.de>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Updating Emacs to latest org-release on MS Windows?
Date: Tue, 07 Jul 2009 18:15:39 +0200 [thread overview]
Message-ID: <87k52ksc44.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <871vosjypw.wl%ucecesf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 07 Jul 2009 16:32:11 +0100")
Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> However, in the standard software on this computer, there is no
> (gnu)make equivalent installed. Therefore, I have the same need as
> Stefan. Is there maybe an elisp script/function that can take the
> place of the make command used to prepare all the .elc files for
> org-mode pulled from the git repository?
C-x d path/to/orgs/el/files/ RET
% m \.el RET
L
B
L: loads all marked files
B: compiles all marked files
As an alternative, a list of the *.el files in the correct order would
be a nice think to have. We have `byte-compile-file' to compile the
files:
byte-compile-file is an interactive compiled Lisp function in
`bytecomp.el'.
(byte-compile-file bytecomp-filename &optional load)
Compile a file of Lisp code named bytecomp-filename into a file of
byte code. The output file's name is generated by passing
bytecomp-filename to the function `byte-compile-dest-file' (which
see).
With prefix arg (noninteractively: 2nd arg), load the file after
compiling. The value is non-nil if there were no errors, nil if
errors.
Sebastian
next prev parent reply other threads:[~2009-07-07 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 15:05 Updating Emacs to latest org-release on MS Windows? Stefan Vollmar
2009-07-07 15:32 ` Eric S Fraga
2009-07-07 16:15 ` Sebastian Rose [this message]
2009-07-07 16:22 ` Sebastian Rose
2009-07-07 16:37 ` Sebastian Rose
2009-07-07 19:21 ` Eric S Fraga
2009-07-07 19:59 ` Sebastian Rose
2009-07-07 20:16 ` Matthew Lundin
2009-07-07 19:32 ` Eric S Fraga
2009-07-07 15:45 ` Scot Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k52ksc44.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).