From: Christopher W Ryan <cryan@binghamton.edu>
To: emacs-orgmode@gnu.org
Subject: Re: how do scientists use org mode?
Date: Tue, 31 Jan 2012 14:20:10 -0500 [thread overview]
Message-ID: <CAM+rpYky46hGuv4qiGpfSSdLLcj9YCu-E5-oBLjGX+X5E=Ae_w@mail.gmail.com> (raw)
In-Reply-To: <87k449j7f0.fsf@tajo.ucsd.edu>
Ah, now I'm beginning to understand: I can export a *part* of an
org-mode file; I'm not limited to exporting the whole thing. Cool!
I also use bibtex/biblatex a lot. I've started to read that these
tools work with Org-mode also. Can anyone speak to that from
experience?
Thanks.
--Chris
On Mon, Jan 30, 2012 at 2:51 PM, <cberry@tajo.ucsd.edu> wrote:
> "Christopher W. Ryan" <cryan@binghamton.edu> writes:
>
>> I'm fairly experienced with emacs, ESS, Sweave, and R, but I've only
>> started to dabble in Org mode in the past couple of weeks. Just as
>> Christoph is, I'm trying to decide whether/how Org-mode might be useful
>> in organizing and carrying out research projects, presentations, etc. So
>> this thread has been very useful and timely.
>>
>> I'm trying to envision what a small research project, managed via a
>> single Org file, might look like. There would be notes from meetings,
>> thoughts from brainstorming sessions, scheduled appointments, data, R
>> code, R output, and manuscript/presentation prose. Some of this might be
>> destined for a manuscript, some for a beamer presentation, and some only
>> for "internal consumption." How are all these pieces differentiated in
>> the Org file, so that Org knows what to put in the
>> presentation/manuscript, and what not to? Could anyone share or point to
>> a short, perhaps fictional, example?
>
> Have you looked at
>
> http://orgmode.org/worg/org-contrib/babel/uses.html
> ??
>
> There are almost too many possibilities --- it is a bit overwhelming.
>
> Here are three things I find useful:
>
> 1) The ability to export a subtree allows you to have many documents
> within the *.org file. Setting EXPORT_* properties for the subtree gives
> you a lot of flexibility. And it is easy to do with TAB completion to
> prompt you to fill in the needed pieces.
>
> 2) Internal hyperlinks are really useful in staying on course in a big,
> complicated document.
>
> 3) Noweb syntax allows you to mix and match different parts of the
> document. Below is a minimal example. The latex chunks can be used
> anywhere I need them. Navigating to '* mini report' and typing
>
> 'C-c @ C-c C-e l'
>
> produces mini.tex.
>
>
> ,----
> | * COMMENT latex chunks
> |
> | #+name: chunk1
> | #+begin_src latex
> | \begin{displaymath}
> | y = r\sin\theta
> | \end{displaymath}
> | #+end_src
> |
> | #+name: chunk2
> | #+begin_src latex
> | \begin{displaymath}
> | x = s\cos\theta
> | \end{displaymath}
> | #+end_src
> |
> |
> | * mini report
> | :PROPERTIES:
> | :EXPORT_FILE_NAME: mini.tex
> | :EXPORT_TITLE: Minimal Report
> | :EXPORT_AUTHOR: Mister CCB
> | :END:
> |
> | #+begin_src latex :noweb yes
> | <<chunk1>>
> | <<chunk2>>
> | #+end_src
> `----
>
> HTH,
>
> Chuck
>
>>
>> Thanks very much.
>>
>> --Chris
>
> [snip]
>
> --
> Charles C. Berry Dept of Family/Preventive Medicine
> cberry at ucsd edu UC San Diego
> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>
>
next prev parent reply other threads:[~2012-01-31 19:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 21:21 how do scientists use org mode? GMX Christoph 13
2012-01-27 1:35 ` Thomas S. Dye
2012-01-27 17:07 ` Eric S Fraga
2012-01-27 18:27 ` John Hendy
2012-01-28 17:39 ` Tomas Grigera
2012-01-30 17:37 ` Christopher W. Ryan
2012-01-30 19:51 ` cberry
2012-01-31 19:20 ` Christopher W Ryan [this message]
2012-01-31 20:13 ` Thomas S. Dye
2012-02-02 17:19 ` Christopher W. Ryan
2012-01-31 19:58 ` Simon Thum
2012-02-02 4:25 ` Christopher W. Ryan
2012-02-02 5:10 ` Nick Dokos
2012-01-28 15:38 ` Bodhi
2012-02-01 8:41 ` Sven Bretfeld
-- strict thread matches above, loose matches on Subject: below --
2012-02-03 21:06 GMX Christoph 13
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='CAM+rpYky46hGuv4qiGpfSSdLLcj9YCu-E5-oBLjGX+X5E=Ae_w@mail.gmail.com' \
--to=cryan@binghamton.edu \
--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.