From: Carsten Dominik <C.Dominik@uva.nl>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: can't get source code editing working
Date: Mon, 26 May 2008 00:33:10 +0200 [thread overview]
Message-ID: <18C65FA2-2FD3-480D-BCF3-0B526DD475A6@uva.nl> (raw)
In-Reply-To: <20080525200408.GA28173@stats.ox.ac.uk>
On May 25, 2008, at 10:04 PM, Dan Davison wrote:
> I agree, this sounds great. I was just about to start trying to
> combine org and latex usage in any case. However I'm being dense.
> I've done git pull && make && make install, and I have org-version
> equal to 6.04b. OK so far, right? Now I create an org file containing
>
> * section 1
> #+BEGIN_SRC latex
> \log p(z|x,\theta)
> #+END_SRC
> * section 2
> #+BEGIN_SRC r
> xor <- function(a,b) (a | b) & !(a & b)
> #+END_SRC
> * section 3
> #+BEGIN_SRC emacs-lisp
> (defun org-xor (a b)
> "Exclusive or."
> (if a (not b) b))
> #+END_SRC
>
> but despite repeated invocations of /C-c '/ and org-edit-special and
> org-edit-src-example, with point in various places, I haven't
> brought up a narrowed buffer in the requested mode. Instead I get
> C-c ' can do nothing useful here. (from C-c ' and org-edit-special)
> and silence from org-edit-src-example
>
The #+begin and #+end lines must start in column 0,
you have whitespace in front of them.
If you load the org-mtags.el module, you can also use
a Muse-like syntax:
<src lang="latex">
</src>
these may be indented.
HTH
- Carsten
next prev parent reply other threads:[~2008-05-25 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48398dc2.1235640a.21e3.ffffbe00SMTPIN_ADDED@mx.google.com>
2008-05-25 16:25 ` Emacs-orgmode Digest, Vol 27, Issue 47 Charles Martin
2008-05-25 20:04 ` can't get source code editing working Dan Davison
2008-05-25 22:33 ` Carsten Dominik [this message]
2008-05-25 16:39 ` Emacs-orgmode Digest, Vol 27, Issue 47 Charles Martin
2008-05-25 16:59 ` Carsten Dominik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18C65FA2-2FD3-480D-BCF3-0B526DD475A6@uva.nl \
--to=c.dominik@uva.nl \
--cc=davison@stats.ox.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.