emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Wrong type argument on latex/pdf export after git pull (9.0.2-136)
Date: Thu, 22 Dec 2016 10:34:00 -0600	[thread overview]
Message-ID: <CA+M2ft_pVJT8WpA7keRffVKYQ9eRVqokvh=S4RM5CPSB6cA3cA@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft9_n043QffG_Uf0zGOac=H-tJc=ZrCcOUQM1mb=dcgSvw@mail.gmail.com>

I'd been looking into debugging in a separate tab, got distracted, and
sent this after forgetting I was going to do that. My apologies for
the second email... I followed the feedback instructions and got this
output:[1]

Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
  replace-regexp-in-string("[^-0-9a-zA-Z_./\n]" "\\\\\\&" nil)
  shell-quote-argument(nil)
  org-compile-file("test.tex" ("%L -interaction nonstopmode
-output-directory %o %f" "%L -interaction nonstopmode
-output-directory %o %f" "%L -interaction nonstopmode
-output-directory %o %f") "pdf" "See \"*Org PDF LaTeX Output*\" for
details" #<buffer *Org PDF LaTeX Output*> ((66 . "bibtex") (76 .
"pdflatex")))
  org-latex-compile("test.tex")
  #[257 "\300 !\207" [org-latex-compile] 3 "\n\n(fn FILE)"]("test.tex")
  org-export-to-file(latex "test.tex" nil nil nil nil nil #[257
"\300 !\207" [org-latex-compile] 3 "\n\n(fn FILE)"])
  org-latex-export-to-pdf(nil nil nil nil)
  org-export-dispatch(nil)
  funcall-interactively(org-export-dispatch nil)
  call-interactively(org-export-dispatch nil nil)
  command-execute(org-export-dispatch)


Thanks for any suggestions,
John

[1] "Activate debugging" chunk added to top of min-config file already shared.
- http://orgmode.org/manual/Feedback.html

On Thu, Dec 22, 2016 at 10:29 AM, John Hendy <jw.hendy@gmail.com> wrote:
> Greetings,
>
>
> I'm finishing up a 30 page end of year work report and perhaps
> stupidly decided I'd git pull on my various emacs packages last night.
> I went to work on it today and I'm getting the following error:
>
> C-c C-e l p
> shell-quote-argument: Wrong type argument: arrayp, nil
>
> I fiddled with tagging various headlines in my real report with
> :noexport: with no success in finding something in the file causing
> this. I then made a simple test file and min config which also creates
> the behavior (emacs -Q, M-x load min-config):
>
> #+begin_src min-config
> (add-to-list 'load-path "~/.elisp/org/lisp/")
> (add-to-list 'load-path "~/.elisp/org/contrib/lisp")
>
> (require 'ox-latex)
> #+end_src
>
> #+begin_src org
> * heading 1
>
> blah blah blah
> #+end_src
>
> M-x org-version
> Org mode version 9.0.2 (release_9.0.2-136-g7fd61c @
> /home/jwhendy/.elisp/org/lisp/)
>
> Is there a way to debug further?
>
>
> Thanks!
> John
>
> P.S. When I pulled last night using =git pull= I got a message back
> that I wasn't on a specified branch, and listed 5 if I recall. I have
> never gotten this before and just did =git pull origin master=
> afterward successfully. Could I be on the incorrect branch?

  reply	other threads:[~2016-12-22 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 16:29 Wrong type argument on latex/pdf export after git pull (9.0.2-136) John Hendy
2016-12-22 16:34 ` John Hendy [this message]
2016-12-22 16:52 ` John Hendy

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='CA+M2ft_pVJT8WpA7keRffVKYQ9eRVqokvh=S4RM5CPSB6cA3cA@mail.gmail.com' \
    --to=jw.hendy@gmail.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).