emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Jay Kerns <gjkernsysu@gmail.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: ob-doc-R-extended.org
Date: Sat, 23 Feb 2013 09:05:49 +0100	[thread overview]
Message-ID: <87ip5j71cr.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAFiLVraXC5Y0YZsr5y8sgVg_b8sX=OLO6jMoAFwdn2aLjzsnhg@mail.gmail.com> (Jay Kerns's message of "Fri, 22 Feb 2013 21:48:28 -0500")

Hi Jay,

Jay Kerns <gjkernsysu@gmail.com> writes:

> Alright, here goes: it looks like the maint branch does not yet
> include the new exporter (ox-latex.el and such).  

Indeed.

> The whole point of
> my working on this to begin with was to get something compatible with
> the new exporter, so rather than go back all over again to make
> something work with something that's set to be outdated in the coming
> months (weeks?) anyway, I'd rather sit tight on the work done so far
> and patiently look forward to the new exporter's merge from master to
> maint.

This should happen before the end of March.

> In the meantime, the latest updated draft (little more than some
> tweaks of Erik Iverson's original work) is here:
>
> https://github.com/gjkerns/org-mode-R-tutorial

Thanks -- another issue for Worg (on top of the maint/master issue)
is that allowing evaluation of code blocks, R code blocks included,
is not permitted.  So the document can exhibit those R blocks, but
the resulting .png should be produced outside Worg and included
there as pictures.

> I've confirmed just now that it successfully exports to PDF/HTML under
> the new exporter based on a freshly pulled org from git mere minutes
> ago.  There's still work to be done, and I welcome
> suggestions/corrections in the balance of time between now and when
> some rendition of this can safely land on Worg.

I'm offline right now and can't test.  I hope someone else on the list
can help with this.

Thanks,

-- 
 Bastien

  reply	other threads:[~2013-02-23 10:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22  8:55 ob-doc-R-extended.org Andreas Röhler
2013-02-22 12:18 ` ob-doc-R-extended.org Jay Kerns
2013-02-22 13:31   ` ob-doc-R-extended.org Bastien
2013-02-22 21:41     ` ob-doc-R-extended.org Andreas Röhler
2013-02-22 21:58       ` ob-doc-R-extended.org Achim Gratz
2013-02-22 22:04         ` ob-doc-R-extended.org Andreas Röhler
2013-02-23  1:49           ` ob-doc-R-extended.org Jay Kerns
2013-02-23  2:48             ` ob-doc-R-extended.org Jay Kerns
2013-02-23  8:05               ` Bastien [this message]
2013-02-22 13:30 ` ob-doc-R-extended.org Bastien
2013-02-22 13:37   ` BUG, ob-doc-R-extended.org Andreas Röhler

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=87ip5j71cr.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=gjkernsysu@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).