From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Two questions about using a =#+begin_src emacs-lisp= block
Date: Tue, 22 Feb 2011 19:45:01 +0100 [thread overview]
Message-ID: <87vd0boqmq.fsf@Rainer.invalid> (raw)
In-Reply-To: 87d3mkc5br.fsf@gmail.com
"Eric Schulte" <schulte.eric@gmail.com> writes:
> if you are worried that you don't have the correct version of Org-mode
> installed you can check the output of the `org-version' function. Mine
> reads
>
> "Org-mode version 7.4 (release_7.4.510.g1e35)"
Note: the SHA1 for the git commit is only shown if Orgmode is installed into a
subdirectory of the git working tree. I remember that this puzzled me
at the beginning... After a few tries I've now set up as follows:
- I'm tracking two branches local-maint->origin/maint (latest release)
local->origin/master (developer version) with rebase and just add a
single commit on top with customizations to the Makefile to get the
install for each branch to the correct location
- the latest release version is installed into .../site-lisp/orgmode/
and is the version that gets used when I "just" start emacs
- in the git working tree I'm installing the latest developer snapshot
into a subdirectory dev-lisp; always compile via
make clean install && make clean
otherwise emacs might pick up byte-compiled files even though you've
changed the sources (by checking out another branch or doing a git
pull or just editing something)
- keep a file handy with:
--8<---------------cut here---------------start------------->8---
;; -*- lisp-interaction -*-
(setq load-path (cons (expand-file-name "~/org-mode/lisp") load-path))
(setq load-path (cons (expand-file-name "~/org-mode/dev-lisp") load-path))
(setq load-path (cdr load-path))
--8<---------------cut here---------------end--------------->8---
load this into emacs and do C-j on one of the first two lines to
switch to using either the compiled or uncompiled developer version.
The last lines strips the load-path of the first element, which
switches back to the "standard" load-path provided you didn't do any
other additions to load-path inbetween.
This is obviously customizable in several respects, but it works for me
and lets me track several stages of orgmode development with minimal
effort.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2011-02-22 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 22:08 Two questions about using a =#+begin_src emacs-lisp= block Chris Malone
2011-02-21 17:17 ` Eric Schulte
2011-02-21 18:31 ` Chris Malone
2011-02-21 19:48 ` Eric Schulte
2011-02-22 15:06 ` Chris Malone
2011-02-22 16:54 ` Eric Schulte
2011-02-22 16:57 ` Chris Malone
2011-02-22 18:06 ` Eric Schulte
2011-02-22 18:23 ` chris.m.malone
2011-02-22 18:45 ` Achim Gratz [this message]
2011-02-21 22:19 ` Dan Davison
2011-02-21 22:34 ` Eric Schulte
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=87vd0boqmq.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).