From: "Thomas S. Dye" <tsd@tsdye.com>
To: Graham Smith <myotisone@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] R - variable names in summary
Date: Wed, 9 Dec 2009 10:51:25 -1000 [thread overview]
Message-ID: <662D65B0-43AA-4967-8F7C-3025739494EF@tsdye.com> (raw)
In-Reply-To: <2c75873c0912091233n788df5o86f603922138ad3f@mail.gmail.com>
Hi Graham,
On Dec 9, 2009, at 10:33 AM, Graham Smith wrote:
> Dan,
>
> That's great, I am beginning to grasp how this works
>
>>> But I would never have figured out the :results output method,
>>> however.
>>
>> OK, it would be really helpful if you could let us know how we should
>> improve the documentation of it.
>
> I'm not sure if I'm the one to ask about the documentation, as I
> struggled with most of it, but that is my problem and probably not
> typical. I'm also still very much trying to get to grips with Emacs
> and orgmode.
>
> Not being a programmer, I find the terminology and phrasing of these
> sorts of things difficult to follow, and need examples to copy , and
> then try and extract from the documentation and other examples, how
> things work.
>
> My problem was therefore the lack of examples specific to R. My
> guess is that the majority of emacs/orgmode users won't have the same
> problems.
>
> Graham
I'd like to second Dan's invitation and ask that you drop a note to
the list when you find something difficult to understand in the
documentation. There isn't anything about the use of Org-babel (or
Org-mode) that a non-programmer shouldn't be able to follow.
BTW, I agree with you about the difficult terminology and phrasing in
the Org-babel documentation. It should be possible to make the
definitions of terms and the distinctions they index more accessible.
So, please let the list know when something trips you up.
When you find an example that fills a gap you perceive in the
documentation, please pass that along, too. The more examples the
better.
I'm glad to hear you've made it over the steep part of the Org-babel
learning curve and that it is working for you now. If your experience
is like mine you'll soon be wondering how you ever managed without it.
All the best,
Tom
next prev parent reply other threads:[~2009-12-09 20:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 23:50 [babel] R - variable names in summary Graham Smith
2009-12-09 4:38 ` Austin Frank
2009-12-09 16:46 ` Graham Smith
2009-12-09 16:38 ` Dan Davison
2009-12-09 17:05 ` Graham Smith
2009-12-09 19:14 ` Dan Davison
2009-12-09 20:33 ` Graham Smith
2009-12-09 20:44 ` Dan Davison
2009-12-09 21:00 ` Graham Smith
2009-12-09 20:51 ` Thomas S. Dye [this message]
2009-12-09 21:06 ` Graham Smith
2009-12-09 20:49 ` Austin Frank
2009-12-09 21:12 ` Graham Smith
2009-12-09 22:28 ` Dan Davison
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=662D65B0-43AA-4967-8F7C-3025739494EF@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=myotisone@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).