From: Carsten Dominik <dominik@science.uva.nl>
To: Patrick Drechsler <patrick@pdrechsler.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Org update script
Date: Thu, 26 Apr 2007 06:41:42 +0200 [thread overview]
Message-ID: <a7a8a1d3179d5f27297d460fb0cb3f2e@science.uva.nl> (raw)
In-Reply-To: <87abww144m.fsf@pdrechsler.de>
On Apr 26, 2007, at 0:27, Patrick Drechsler wrote:
> "Scott Jaderholm" <jaderholm@gmail.com> writes:
>> wget http://staff.science.uva.nl/~dominik/Tools/org/
>> awk to find out version number
>> wget http://staff.science.uva.nl/~dominik/Tools/org/org-x.zip
>> tar -xvzf org-x.tar.gz
>> rm -rf ~/org-tar.gz
>> rm ~/.elisp/org
>> mv org-x ~/.elisp/org
>> cd ~/.elisp/org
>> make
>
> Why make?
>
> Isn't org mode small enough to run with *.el files instead of *.elc
> files?
org.el is the single biggest Emacs Lisp file in the
Emacs distribution. Admittetly there are larger packages
like gnus that have een split over many files, but still
org-mode is PRETTY BIG. I am glad that it still feels
lightweight to you, this is one of the goals of its
development.
I would always recommend doing the compilation step. It speeds
up loading of the file, and the general performance is much
better. Still most operations are fast enough so that you
will not feel the difference. However, producing a large agenda,
or in particular recomputing a large spreadsheet will be a
lot faster with compiled org.elc.
The one case when you should not use a compiled file is when
sending be the traceback of an error - that is much more useful
when made with uncompiled code.
- Carsten
next prev parent reply other threads:[~2007-04-26 4:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 16:30 Org update script Scott Jaderholm
2007-04-25 18:58 ` Pete Phillips
2007-04-25 19:57 ` Scott Jaderholm
2007-04-25 21:57 ` Pete Phillips
2007-04-25 22:27 ` Patrick Drechsler
2007-04-26 4:41 ` Carsten Dominik [this message]
2007-04-26 5:56 ` Pete Phillips
2007-04-28 22:22 ` Patrick Drechsler
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=a7a8a1d3179d5f27297d460fb0cb3f2e@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=patrick@pdrechsler.de \
/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).