From: Rainer M Krug <Rainer@krugs.de>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Writing .el files for org in org?
Date: Tue, 27 May 2014 11:07:03 +0200 [thread overview]
Message-ID: <m2ha4blhe0.fsf@krugs.de> (raw)
In-Reply-To: <8738fv1ufv.fsf@gmail.com> (Thorsten Jolitz's message of "Tue, 27 May 2014 10:45:24 +0200")
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
Hi Thorsten
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Rainer M Krug <Rainer@krugs.de> writes:
>
> Hi Rainer,
>
>> But as I am struggling with elisp, I would like to put the ob-R.el file
>> into an org file which is then tangled into the ob-R.el file.
>
> again, this is the main use case for outshine & outorg.
>
> They work with old-school and outshine (= outcommented org-mode)
> headlines, so you just have to structure ob-R.el with some headlines,
> either like this:
>
> ,--------------
> | ;;; Level 1
> | ;;;; Level 2
> `--------------
>
> or like this
>
> ,---------------
> | ;; * Level 1
> | ;; ** Level 2
> `---------------
>
> (just like you structure an Org file) and then you can switch between
> emacs-lisp-mode and org-mode with
>
> ,-----------------------------
> | M-# M-# (outorg-edit-as-org)
> `-----------------------------
>
> and
>
> ,---------------------------------
> | M-# (outorg-copy-edits-and-exit)
> `---------------------------------
>
> Org-mode and emacs-lisp-mode thus become two different views on the same
> (well-structured) file, and you can easily switch between them.
I got it working - looks very nice. Definitely an option.
Thanks,
Rainer
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
PGP: 0x0F52F982
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
prev parent reply other threads:[~2014-05-27 9:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 20:21 Writing .el files for org in org? Rainer M Krug
2014-05-21 23:25 ` Aaron Ecay
2014-05-22 8:12 ` Rainer M Krug
2014-05-22 8:56 ` Bastien
2014-05-22 9:25 ` Rainer M Krug
2014-05-22 9:29 ` Bastien
2014-05-22 9:54 ` Rainer M Krug
2014-05-22 11:04 ` Bastien
2014-05-22 11:42 ` Rainer M Krug
2014-05-22 15:10 ` Bastien
2014-05-23 7:29 ` Rainer M Krug
2014-06-02 11:22 ` John Kitchin
2014-06-02 14:00 ` Rainer M Krug
2014-07-27 21:50 ` Bastien
2014-07-30 2:04 ` John Kitchin
2014-05-22 15:44 ` Josh Berry
2014-05-22 18:49 ` Rainer M Krug
2014-05-22 0:30 ` Grant Rettke
2014-05-22 8:30 ` Rainer M Krug
2014-05-22 23:34 ` Grant Rettke
2014-05-27 8:45 ` Thorsten Jolitz
2014-05-27 9:07 ` Rainer M Krug [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=m2ha4blhe0.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@gmail.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).