emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jay Kerns <gjkernsysu@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: worg-new-exporter successful publish locally
Date: Sat, 27 Apr 2013 02:53:46 -0400	[thread overview]
Message-ID: <CAFiLVrZ8W=dLuHdBxfdenZzkUn3QgpHJO28B_56ujqL1=M=UMw@mail.gmail.com> (raw)

Hi there,

The new Worg branch publishes for me without error under Org-mode
version 8.0.1 (release_8.0.1-24-g92f372).  I updated the existing
emacs.el (underlying Worg, IIUC) to the Org 8.0 exporting/publishing
syntax. You can see the latest draft in


which lives in the top-level directory. To test the publish yourself
you'd need to customize the base/publishing directories for your local
machine and then do

emacs -Q -l "/path/to/worg/worgtest-init.el"

followed by

M-x publish-worg

There are changes to some files which are necessary for a successful
publish and which are detailed at the bottom of this email. Have a
look in FIXME.

Given the successful publish locally, I went through and updated all
remaining in-buffer settings that I could find (HTML_HEAD, etc.).  To
the best of my knowledge, everything is DONE, notwithstanding the
comments below.

1. I didn't work on orgmode.org at all.
2. Successful export/publish doesn't say anything about the content
   and/or outdated info in the pages.



- sitemap.org
  - Error: Invalid time-stamp specification
  - The error here has to do with an undocumented function that I
    can't figure out.
  - Status: disabled auto-sitemap in publish-alist

- FIXME/how-to-use-Babel-for-R.org
  - content is out of date, but exports without error
  - Status: updated in-buffer settings but otherwise unchanged

- FIXME/test-for-how-to-use-Babel-for-R.org
  - content is out of date, but exports without error
  - Status: updated buffer settings but otherwise unchanged

- org-contrib/babel/header-args.org
  - Error: local variables in header-args.org and header-args.html
    - eval: org-babel-default-header-args:Python
    - if I hit "n" then Emacs hangs until C-g
    - Status: moved to FIXME

- org-tutorials/org-R/variable-popcon.org
  - Error: none, really, it takes a really long time to export but
    succeeds eventually.
  - Status: unchanged, but somebody might investigate the reason for
    this extended export time, maybe it's just because the file is so

- org-configs/org-customization-survey.org
  - export of this single file takes 1.5 hrs on my laptop
  - I don't know why
  - Status: moved to FIXME

- The following appear to set file local variables
  - code/org-info-js/changes.org
  - code/org-info-js/org-slides/slides.org
  - org-contrib/org-drill.org
  - org-contrib/org-git-link.org
  - org-contrib/babel/examples/drift.org
  - Status updated in buffer settings, but otherwise unchanged.
    Thought you might like to know.

             reply	other threads:[~2013-04-27  6:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27  6:53 Jay Kerns [this message]
2013-04-27  6:59 ` worg-new-exporter successful publish locally Bastien
2013-04-27  8:38   ` Carsten Dominik
2013-04-27  8:40 ` Thorsten Jolitz
2013-04-27 13:33   ` Jay Kerns
2013-04-27 15:43 ` Achim Gratz
2013-04-28 16:44   ` Jay Kerns
2013-04-28 19:12     ` Achim Gratz
2013-04-28 19:43       ` Jay Kerns
2013-04-28 20:21       ` Achim Gratz
2013-04-28 21:17         ` Jay Kerns
2013-05-01 17:51         ` Achim Gratz

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:

  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='CAFiLVrZ8W=dLuHdBxfdenZzkUn3QgpHJO28B_56ujqL1=M=UMw@mail.gmail.com' \
    --to=gjkernsysu@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).