Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Nick Dokos
Tom Prince wrote: > On Tue, 15 Nov 2011 15:30:25 -0500, Nick Dokos wrot= > e: > > Tom Prince wrote: > >=20 > > > With b43c1c621f52f4a51d8d79cb76c226dfed003998 running > > >=20 > >=20 > > Please use C-u M-x org-version to insert version information in your > > mail. It's not possible to see from

Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Tom Prince
On Tue, 15 Nov 2011 15:30:25 -0500, Nick Dokos wrote: > Tom Prince wrote: > > > With b43c1c621f52f4a51d8d79cb76c226dfed003998 running > > > > Please use C-u M-x org-version to insert version information in your > mail. It's not possible to see from the SHA1 whether it is a recent > version or

Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Nick Dokos
Herbert Sitz wrote: > I've been working with getting the batch quoting working both for bash and for > windows command line (in VimOrganizer clone), trying to keep them as much > alike > as possible. I think I have things working okay for now, but your tips may be > helpful if I end up with som

Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Herbert Sitz
Nick Dokos hp.com> writes: > > That doesn't matter here: both of the above should work fine in a bash > (or similar) shell environment. I prefer the single quote style in > general, since it allows me to leave everything else unchanged[fn:1]. > > But shell quoting is a minefield: when you have t

Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Nick Dokos
Herbert Sitz wrote: > Herbert Sitz gmail.com> writes: > > > > Not sure, but I do something similar with a single --eval: > > > > --eval '(progn (find-file "filename") (org-export-as-html-and-open 3) )' > > > > Except my version has double quotes for --eval argument and backslashes before

Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Nick Dokos
Tom Prince wrote: > With b43c1c621f52f4a51d8d79cb76c226dfed003998 running > Please use C-u M-x org-version to insert version information in your mail. It's not possible to see from the SHA1 whether it is a recent version or an old version without doing git archaelogy. > emacs --no-init-file -

Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Eric Schulte
Tom Prince writes: > With b43c1c621f52f4a51d8d79cb76c226dfed003998 running > > emacs --no-init-file --load min.el --eval '(setq debug-on-error t)' --eval > '(find-file "test.org")' -eval '(org-export-as-html 3)' --batch > > with > > -- min.el > (setq org-babel-load-languages '((emacs-lisp .

Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Herbert Sitz
Herbert Sitz gmail.com> writes: > > Not sure, but I do something similar with a single --eval: > > --eval '(progn (find-file "filename") (org-export-as-html-and-open 3) )' > Except my version has double quotes for --eval argument and backslashes before embedded quotes: --eval "(progn

Re: [O] Failure exporting with emacs --batch

2011-11-15 Thread Herbert Sitz
Tom Prince ualberta.net> writes: > With b43c1c621f52f4a51d8d79cb76c226dfed003998 running > > emacs --no-init-file --load min.el --eval '(setq debug-on-error t)' --eval '(find-file "test.org")' > -eval '(org-export-as-html 3)' --batch > Not sure, but I do something similar with a single --eval

[O] Failure exporting with emacs --batch

2011-11-15 Thread Tom Prince
With b43c1c621f52f4a51d8d79cb76c226dfed003998 running emacs --no-init-file --load min.el --eval '(setq debug-on-error t)' --eval '(find-file "test.org")' -eval '(org-export-as-html 3)' --batch with -- min.el (setq org-babel-load-languages '((emacs-lisp . t) (latex . t))) (setq org-confirm-