Bastien <bastien.gue...@wikimedia.fr> writes: > Matt Lundin <m...@imapmail.org> writes: > >> Would there be any way to get the Worg publishing script or export of >> source code blocks to fail gracefully in these instances? > > That would be helpful indeed. > > As a first step, we could handle errors in a more clever way by using > the variable `noninteractive', testing if Emacs is running in batch > mode. In batch mode, instead of blocking the export process with a > (error ...), we could just logs problems. > > Let's collect places where errors can block the publishing process.
Sounds like a good approach. I found a few using: $ git log --oneline | grep -i export | egrep -i "fix|issue|broke|problem|error|resolve|correct|publish" All the ones I found were related to Babel. 1) Used "shell" instead of "sh" for the source block mode. Fixed by commit e4ed828. 2) Used "=<<code-block-name>>=" instead of ": <<code-block-name>>". Fixed by commit 90cb8cb. When I tested this with by checking out 90cb8cb and trying to export org-contrib/babel/org-babel.org, I got the error "org-babel-exp-lob-one-liners: Wrong type argument: stringp, nil". 3) Enclosing #+begin_src into #+begin_quote. Fixed by commit fd3bca5. The error is: File mode specification error: (file-error "Cannot open load file" "html-helper-mode") _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
