From: Matthew Lundin <mdl@imapmail.org>
To: Peter Frings <peter.frings@agfa.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Latest Org and Carbon Emacs
Date: Fri, 10 Jul 2009 08:03:50 -0500 [thread overview]
Message-ID: <m2tz1k1yh5.fsf@fastmail.fm> (raw)
In-Reply-To: <90CC215B-8E59-4070-92D3-0A4AD7A0510F@agfa.com> (Peter Frings's message of "Fri\, 10 Jul 2009 09\:25\:38 +0200")
Peter Frings <peter.frings@agfa.com> writes:
> On 09 Jul 2009, at 23:32, Matthew Lundin wrote:
>
>> I found it easiest to install the new org files directly to the
>> Emacs.app directory.
>
> I've seen this approach mentioned several times, but I think it makes
> things more complicated then they should be. By keeping the app and
> the libs in separate places, the two can be updated independently.
> Emacs provides ample ways of supporting this style -- actually, I
> guess it was meant to work that way, until the bundles came along...
Exactly. The beauty of Emacs is that there are multiple options for
everything. Overwriting org when I updated Carbon Emacs wasn't really an
issue for me because 1) Carbon Emacs is very rarely updated 2) I pull
the latest changes from the git repo and run make && make install every
day.
The reason I just threw org-mode in the Emacs.app directory is that I
also had EmacsCVS.app and wanted to keep separate byte-compiled for
Emacs 22 and Emacs 23.
If you're looking for the simplest way to install a byte-compiled
org-mode, I believe you could just clone the git repository to
~/org-mode, run make in the directory, and then add ~/org-mode/lisp to
your load path.
> Of course, it's very convenient when you download Carbon Emacs (or
> others) that everything is in place, but since when do Linuxers care
> about convenience? :-)
Well, I suppose in this case convenience is in the eye of the beholder.
E.g., pacman -S emacs-cvs. ;)
Best,
Matt
prev parent reply other threads:[~2009-07-10 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 20:27 Latest Org and Carbon Emacs Karl Maihofer
2009-07-09 20:46 ` Nick Dokos
2009-07-09 21:09 ` Karl Maihofer
2009-07-09 21:32 ` Matthew Lundin
2009-07-10 7:25 ` Peter Frings
2009-07-10 13:03 ` Matthew Lundin [this message]
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=m2tz1k1yh5.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=peter.frings@agfa.com \
/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).