emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jay Kerns <gjkernsysu@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Updating Worg: call to Worg authors
Date: Thu, 25 Apr 2013 19:18:44 -0400	[thread overview]
Message-ID: <CAFiLVrZwHwv9dDVUdCw-oJXCFXKOezmBdqEANYjrontdoYMPXA@mail.gmail.com> (raw)
In-Reply-To: <87obd48emr.fsf@gmail.com>

Greetings,

First: thanks to Nicholas Goaziou and Thorsten Jolitz. There is
a bunch of work already completed - indeed, out of the 83
currently existing headlines, 63 are marked DONE.

But there is a lot of updating that remains.  And the longer the
process continues, the further the two branches will diverge so all
the more difficult the eventual merge of the two branches will be.

Moving forward, I would like to start marking *.org files DONE if they
export cleanly on my machine with no change. To this end, it occurred
to me that just because a file exports cleanly on *my* machine doesn't
necessarily mean that it would be OK on Worg. (This occurred to me
when I noticed Babel code evaluating during export, something not
permitted on Worg).

For testing purposes, we should be using a minimal config, consistent
with the one on Worg, right? This let me to here:

http://orgmode.org/worg/sources/emacs.el

Though that one, of course, has a bunch of extra stuff which isn't
relevant for the time being (publishing, etc.). In addition, that one
is not necessarily compatible with Org 8.0 and the new exporter.

I've made a first stab at a minimal init file, copy-pasted below. I've
also put a soft copy called

worgtest-init.el

which lives right beside worgmap.org in the top-level of the
worg-new-exporter branch. It would seem that the new asynchronous
export would make it relatively easy to test files uniformly and
minimally for Org 8.0 by doing something like

$ emacs -Q -l "~/git/worg/worgtest-init.el"

and testing from there.

Here are my questions:

1. Is this overkill?
2. Is there something extra/missing in worgtest-init.el?
3. Anything I should be asking but amn't?

-- 
Jay


#+BEGIN_SRC emacs-lisp
(custom-set-variables
 '(org-modules (quote (org-jsinfo)))
 '(safe-local-variable-values
   (quote ((org-tags-column . -80)
	   (org-export-html-style . "<link rel=\"stylesheet\"
type=\"text/css\" href=\"stylesheet.css\" />")
	   (org-export-html-style-extra . "<link rel=stylesheet
href=\"org-faq.css\" type=\"text/css\"> <style type=\"text/css\">
</style>")
	   (org-export-html-style . "<link rel=stylesheet
href=\"freeshell2.css\" type=\"text/css\"> <style type=\"text/css\">
.tag { color: red; font-weight:bold}</style>")))))

(add-to-list 'load-path "~/git/org-mode/lisp/")
(add-to-list 'load-path "~/git/org-mode/contrib/lisp/")

(show-paren-mode 1)
(menu-bar-mode 0)

(require 'org)
(require 'htmlize)

(setq org-export-in-background t)
(setq org-export-async-init-file "~/git/worg/worgtest-init.el")
(setq org-export-async-debug t)

(setq org-export-default-language "en"
      org-export-html-extension "html"
      org-export-with-timestamps nil
      org-export-with-section-numbers nil
      org-export-with-tags 'not-in-toc
      org-export-skip-text-before-1st-heading nil
      org-export-with-sub-superscripts '{}
      org-export-with-LaTeX-fragments t
      org-export-with-archived-trees nil
      org-export-highlight-first-table-line t
      org-export-html-style-include-default nil
      org-export-htmlize-output-type 'css
      org-startup-folded nil
      org-export-allow-BIND t
      org-export-babel-evaluate nil
      org-confirm-babel-evaluate nil)
#+END_SRC

  reply	other threads:[~2013-04-25 23:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 20:57 Jay Kerns
2013-04-24  7:25 ` Suvayu Ali
2013-04-24  7:44   ` Bastien
2013-04-24  7:52     ` Suvayu Ali
2013-04-24  7:53 ` Carsten Dominik
2013-04-24  9:25 ` Thorsten Jolitz
2013-04-25 23:18   ` Jay Kerns [this message]
2013-04-25 23:26     ` Jay Kerns

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=CAFiLVrZwHwv9dDVUdCw-oJXCFXKOezmBdqEANYjrontdoYMPXA@mail.gmail.com \
    --to=gjkernsysu@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tjolitz@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).