From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Re: Error when exporting LaTeX
Date: Wed, 24 Jun 2015 08:45:39 -0400 [thread overview]
Message-ID: <6sw6c7fv5hcm18.fsf@pfdstudio.com> (raw)
In-Reply-To: <6sw6c7k2utcmuc.fsf@pfdstudio.com> (Peter Davis's message of "Wed, 24 Jun 2015 08:28:11 -0400")
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
Peter Davis <pfd@pfdstudio.com> writes:
> I'm writing a fairly simple document with some #+BEGIN_SRC/#+END_SRC
> blocks, and when I try to export to LaTeX/PDF, I get:
>
> org-latex-src-block: Wrong type argument: stringp, nil
>
> Does this ring any bells? I can try to cobble together a "neutralized"
> sample to reproduce the problem, but I thought I'd see if anyone
> recognized it.
Ok, here's a sample file and image that reproduces the problem. Any help
appreciated.
Thank you.
-pd
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: org file that triggers "wrong type argument" error --]
[-- Type: text/x-org, Size: 2923 bytes --]
#+STARTUP: showeverything logdone
#+options: num:nil
#+OPTIONS: H:5 num:t \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t
#+LaTeX_CLASS: koma-article
#+LaTeX_HEADER: \usepackage{listings}
#+LATEX_HEADER: \setlength{\parskip}{2ex plus 4pt minus 2pt}
#+LATEX_HEADER: \setlength{\parindent}{0pt}
#+LATEX_HEADER: \renewcommand{\baselinestretch}{1.0}
#+LATEX_HEADER: \setlength{\topsep}{-10pt}
#+LATEX_HEADER: \setlength{\partopsep}{0pt}
#+LaTeX_HEADER: \usepackage{xcolor}
#+LaTeX_HEADER: \lstset{
#+LaTeX_HEADER: basicstyle=\ttfamily,
#+LaTeX_HEADER: breaklines=true,
#+LaTeX_HEADER: prebreak=\mbox{\ensuremath{\color{red}\hookleftarrow}},
#+LaTeX_HEADER: postbreak=\raisebox{0ex}[0ex][0ex]{\ensuremath{\color{red}\hookrightarrow\space}},
#+LaTeX_HEADER: columns=fullflexible,
#+LaTeX_HEADER: keepspaces=true
#+LaTeX_HEADER: }
#+LaTeX_CLASS_OPTIONS: [article,letterpaper,times,12pt,listings-bw,microtype]
#+author: Peter Davis
#+title: LaTeX export issue
* Overview
Many applications using the XYZCo API will follow a sequence of operations like this:
** User logs in, establishing identity and access privileges
The login page is invoked via an http request, such as:
#+BEGIN_SRC js
GET http://local.xyzco.com:3000/sample/login
#+END_SRC
In the Sample App, this results in a page showing four buttons:
[[./pd-logo-jelly-small.gif]]
** Login with XYZ
If the user selects "Login with XYZ", the Sample App invokes this URL:
#+BEGIN_SRC
GET http://local.xyzco.com:3000/sample/auth/xyz
#+END_SRC
The response, 302, results in a redirect to a new page prompting for username and password is presented[1]:
#+BEGIN_SRC js
GET http://sandbox.api.xyzco.com:8080/openid-connect/v2/authorize?response_type=code&redirect_uri=http%3A%2F%2Flocal.xyzco.com%3A3000%2Fsample%2Fauth%2Fxyz%2Fcallback&scope=openid&client_id=152ced50-1369-4b19-8b26-8f3d5d9bfd6a.xyzco.com
#+END_SRC
[[./pd-logo-jelly-small.gif]]
Entering a username and password here results in this request:
#+BEGIN_SRC js
POST http://sandbox.api.xyzco.com:8080/openid-connect/j_spring_security_check?response_type=code&redirect_uri=http%3A%2F%2Flocal.xyzco.com%3A3000%2Fsample%2Fauth%2Fxyz%2Fcallback&scope=openid&client_id=152ced50-1369-4b19-8b26-8f3d5d9bfd6a.xyzco.com
#+END_SRC
[[./pd-logo-jelly-small.gif]]
** The application provides security information (e.g., OAuth2 token) to enable access to information
#+BEGIN_SRC js
GET http://sandbox.api.xyzco.com:8080/openid-connect/v2/authorize?response_type=code&redirect_uri=http%3A%2F%2Flocal.xyzco.com%3A3000%2Fsample%2Fauth%2Fxyz%2Fcallback&scope=openid&client_id=152ced50-1369-4b19-8b26-8f3d5d9bfd6a.xyzco.com
#+END_SRC
#+BEGIN_SRC js
GET http://local.xyzco.com:3000/sample/auth/xyz/callback?code=eyJhbGciOiLlif_vla6jwjA ...
#+END_SRC
From this point, the application can present other options to the user.
[1] If the user is not already logged in, he or she will see the login page
[-- Attachment #3: sample image for use with error file --]
[-- Type: image/gif, Size: 13395 bytes --]
next prev parent reply other threads:[~2015-06-24 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 12:28 Error when exporting LaTeX Peter Davis
2015-06-24 12:45 ` Peter Davis [this message]
2015-06-24 12:47 ` Alan Schmitt
2015-06-24 12:50 ` 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=6sw6c7fv5hcm18.fsf@pfdstudio.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
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).