together pleasing to my eye.
yes, i see what you mean. though in a very limited pedagological
context, where you want to show the viewer of the exported document what
an org-in-org file looks like in an emacs .org buffer, i guess you might
want this.
for my use, your solution for org-in-org is exactly what i need.
cheers, Greg
Greg,
> On Mar 7, 2021, at 11:44 PM, Greg Minshall wrote:
>
> i guess when i used the term "recursive execute function" (i tend to
> confuse "execute" and "export"), i was thinking of something like: when
> i export an org file, and it runs into an
port"), i was thinking of something like: when
i export an org file, and it runs into an org-in-org block to export,
then your code runs on that block. the recursive part is that, when
your code is runninng on the org-in-org block, and runs into an
"org-in-org-in-org" block (that is also m
> On Mar 7, 2021, at 8:14 AM, Greg Minshall wrote:
>
> Charles,
>
> thanks. any thing you'd like to add to the R-via-ESS/org-mode
> repository, that would be great.
>
> in general, afaik, the contents of org-in-org buffers export okay. at
> least plain one
Charles,
thanks. any thing you'd like to add to the R-via-ESS/org-mode
repository, that would be great.
in general, afaik, the contents of org-in-org buffers export okay. at
least plain ones. would could like to have the embedded code blocks go
through some pretty-printer, but curren
> ,#+END_SRC
> #+END_SRC
iiuc, this will embed the org-in-org block ("readdata-code") in the
outer org document. and, if i open the org-in-org block, and C-c C-c to
execute it, the results will likewise be available in the outer org
document, and can be exported, etc.
this is v
Erik,
> I am not sure if this would be useful to your efforts, but I have an "R in
> org-mode" tutorial on github:
> https://github.com/erikriverson/org-mode-R-tutorial
thanks. that gives me a model to look at in terms of structure and
content.
Greg
credit goes to
https://raw.githubusercontent.com/vikasrawal/orgpaper/master/orgpapers.org
Best regards,
Jeremie
On Tuesday, 23 Feb 2021 at 17:24, Greg Minshall wrote:
> i have a question about org-in-org source blocks. i volunteered to help
> in an effort to provide a tutorial of using the E
all wrote:
> i have a question about org-in-org source blocks. i volunteered to help
> in an effort to provide a tutorial of using the ESS (Emacs Speaks
> Statistics) package for R, in particular, from org mode.
>
> i'd like to write my contribution as a .org file. i'd like
Greg,
See inline
> On Feb 23, 2021, at 6:24 AM, Greg Minshall wrote:
>
> i have a question about org-in-org source blocks. i volunteered to help
> in an effort to provide a tutorial of using the ESS (Emacs Speaks
> Statistics) package for R, in particular, from org mode.
&
i have a question about org-in-org source blocks. i volunteered to help
in an effort to provide a tutorial of using the ESS (Emacs Speaks
Statistics) package for R, in particular, from org mode.
i'd like to write my contribution as a .org file. i'd like to include
fragments o
Ok, I am giving it a shot. Here is my setup:
;;; org path
(defvar org-load-path
(list (file-name-as-directory
(expand-file-name "org" starter-kit-dir)))
"List of directories to find org-files that
`org-babel-load-file' can load code from")
(defun org-require (feature)
"Load a FEATURE
Hi John and Rainer,
Rainer M Krug writes:
>> What if we created a new directory in the repository called "org" which
>> contains these kinds of files? It would be analogous to the "lisp"
>> directory. I don't think we need to have both ob-R.org and ob-R.el in the
>> repository.
>
> I think that
John Kitchin writes:
> What if we created a new directory in the repository called "org" which
> contains these kinds of files? It would be analogous to the "lisp"
> directory. I don't think we need to have both ob-R.org and ob-R.el in the
> repository.
I think that would be a very good idea fo
What if we created a new directory in the repository called "org" which
contains these kinds of files? It would be analogous to the "lisp"
directory. I don't think we need to have both ob-R.org and ob-R.el in the
repository.
For example I wrote org-ref.org, and I load it like this in my init file
Hi Thorsten
Thorsten Jolitz writes:
> Rainer M Krug 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 wi
Rainer M Krug 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)
Bastien writes:
> Rainer M Krug writes:
>
>> But as I am not the one who has to maintain it, it is easy for me to
>> suggest it.
>
> :)
>
> Even if we find a solution for keeping everything in sync easily,
> there is still the problem of enforcing a convention on potentially
> many contributors.
On Thu, May 22, 2014 at 3:30 AM, Rainer M Krug wrote:
> If I understand you correctly, you are using Vagrant to develop your code
> and to generate the release - that is a good idea. But isn't this an
> overkill in the case of the context here? org (and emacs) should be
> stable enough to tangle
Josh Berry writes:
> On Thu, May 22, 2014 at 5:54 AM, Rainer M Krug wrote:
>
>> 4) and if it is working, detangled into ob-org
>>
>
> Apologies for jumping in as a lurker. When you say "detangled", is there a
> process for doing this? I know that working with cweb files the tangled
Yes -
On Thu, May 22, 2014 at 5:54 AM, Rainer M Krug wrote:
> 4) and if it is working, detangled into ob-org
>
Apologies for jumping in as a lurker. When you say "detangled", is there a
process for doing this? I know that working with cweb files the tangled
output included some markers to indica
Rainer M Krug writes:
> But as I am not the one who has to maintain it, it is easy for me to
> suggest it.
:)
Even if we find a solution for keeping everything in sync easily,
there is still the problem of enforcing a convention on potentially
many contributors.
Maybe you can publish your ob-R
Bastien writes:
> Rainer M Krug writes:
>
>> So the reason why I think it would be advantageous to have these files
>> in org does not lie with the programmer familiar with emacs-lisp, but
>> with somebody familiar with the other side.
>
> Sorry I was too terse in my previous answer: I completel
Rainer M Krug writes:
> So the reason why I think it would be advantageous to have these files
> in org does not lie with the programmer familiar with emacs-lisp, but
> with somebody familiar with the other side.
Sorry I was too terse in my previous answer: I completely agree with
the goal you d
Bastien writes:
> Rainer M Krug writes:
>
>> So I would argue that in ob-LANGUAGE.el files the non-elisp-expert is more
>> likely to look and work then in the core org files wherefore an
>> a more familiar interface for these changes (literate programming in
>> org) would provide more advantages
Rainer M Krug writes:
> So I would argue that in ob-LANGUAGE.el files the non-elisp-expert is more
> likely to look and work then in the core org files wherefore an
> a more familiar interface for these changes (literate programming in
> org) would provide more advantages then in the org-core fil
Bastien writes:
> Hi Rainer and Aaron,
>
> Aaron Ecay writes:
>
>> I am not so convinced that having all the elisp code in an org file
>> would be convenient, since I am worried that would break the interactive
>> features of elisp programming.
>
> My point of view too.
>
> On top of this, I see
Hi Rainer and Aaron,
Aaron Ecay writes:
> I am not so convinced that having all the elisp code in an org file
> would be convenient, since I am worried that would break the interactive
> features of elisp programming.
My point of view too.
On top of this, I see two problems:
1. there is the p
Grant Rettke writes:
> On Wed, May 21, 2014 at 3:21 PM, Rainer M Krug wrote:
>> I am sure this would be possible, but would this be feasible? A good
>> idea? Or would it be better to have an additional directory
>> (e.g. lisp.org) which contains the corresponding .org files?
>
> Great question.
Aaron Ecay writes:
> Hi Rainer,
>
> I have wondered about what you suggest as well, from the point of view
> of trying to modify the long pieces of R code which are embedded in
> strings in ob-R.el. I think this would be easier if they could be
> tangled from R code blocks in an org file. So fr
On Wed, May 21, 2014 at 3:21 PM, Rainer M Krug wrote:
> I am sure this would be possible, but would this be feasible? A good
> idea? Or would it be better to have an additional directory
> (e.g. lisp.org) which contains the corresponding .org files?
Great question. Anybody tangling with org-mode
Hi Rainer,
I have wondered about what you suggest as well, from the point of view
of trying to modify the long pieces of R code which are embedded in
strings in ob-R.el. I think this would be easier if they could be
tangled from R code blocks in an org file. So from that point of view
the idea h
Hi
I am just getting into the ob-R.el file and am making some changes which
will make it easier to customize the behaviour and possibly mre
transparent how variable transfer and wrapping of graph generation is
done.
But as I am struggling with elisp, I would like to put the ob-R.el file
into an o
33 matches
Mail list logo
