emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Misc. questions
Date: Tue, 04 Oct 2016 15:02:56 -0400	[thread overview]
Message-ID: <1475607776.3238953.745790809.290F05FA@webmail.messagingengine.com> (raw)

I apologize in advance for the flood of questions, but I'm using org in
new ways now for creating documentation, and running into a lot of
issues.

1) Is there a way to automatically say "yes" to all the "Evaluate code
block...?" questions when I export, so I don't have to keep typing "yes"
over and over again?

2) How does the export menu get set? I'm loading, for example,
ox-texinfo, but I don't see the option to export texinfo when I type C-c
C-e.  I'm also loading ox-pandoc, which shows me a slew of export
formats on my Mac, but only two, file and buffer, on my Win10 machine.

3) Still trying to find a way to get to DocBook XML (4, it turns out). I
know the export page says to output texi (see #2 above) and then convert
with makeinfo, but I have my doubts.  Of course, once I get texi working
I'll be able to see for myself what information, if any, is lost.

4) Is json a valid language for #+BEGIN_SRC? I don't see any syntax
highlighting in HTML or LaTeX/PDF output, and I'm getting errors from
LaTeX:

! Package Listings Error: language json undefined.

Come to think of it, I think the org-mode doc lists both JavaScript (js)
and JSON (json) as supported languages for code blocks, but the Listings
LaTeX package doesn't list either of these.

Thanks!
-pd

-- 
  Peter Davis
  www.techcurmudgeon.com

next             reply	other threads:[~2016-10-04 19:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 19:02 Peter Davis [this message]
2016-10-04 19:57 ` Misc. questions John Hendy
2016-10-04 20:26   ` Peter Davis
2016-10-04 20:50     ` Thomas S. Dye
2016-10-05 10:22   ` Colin Baxter
2016-10-04 19:58 ` Thomas S. Dye
2016-10-04 20:21 ` Stig Brautaset
2016-10-05 13:08   ` Peter Davis
2016-10-05 17:35 ` Peter Davis

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=1475607776.3238953.745790809.290F05FA@webmail.messagingengine.com \
    --to=pfd@pfdstudio.com \
    --cc=emacs-orgmode@gnu.org \
    /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

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