From: John Hendy <jw.hendy@gmail.com>
To: R Jain <rjain.ece@gmail.com>
Cc: "emacs-orgmode gnu.org" <emacs-orgmode@gnu.org>,
Dereje Tefera <tefera@ualberta.ca>
Subject: Re: org mode error "pdf wasn't produced"
Date: Thu, 15 Mar 2018 11:09:12 -0500 [thread overview]
Message-ID: <CA+M2ft-iQrDKX98C+v60WZzaU0=qZFyGGu9Vitam=gZxbbYBKQ@mail.gmail.com> (raw)
In-Reply-To: <local-d171c038-c16e-v1.1.4-22d9f20d@MONKEY>
On Thu, Mar 15, 2018 at 10:06 AM, R Jain <rjain.ece@gmail.com> wrote:
> Hi Dereje,
>
> Two things:
> 1) Pygmentize is a python package. I hope you meant trying to install it for
> python, and not Latex or Emacs.
> http://pygments.org/docs/cmdline/
> 2) Which Tex software are you using? I recall having some compilation errors
> (last year) when I was setting this up with org-mode. Though I can't put my
> finger on what solved the problem, it was after I installed TexMaker. A
> friend suggested that it has a very decent library.
>
> So, if you have installed the vanilla Miktex, or something else, I'd
> recommend giving TexMaker a try. Don't recall ever having to open it up
> though.
I have successfully used MikTex in the past and definitely remember
having an initial setup cycle of trying to export, checking the Org
PDF Latex buffer, identifying the missing package(s), installing via
the MikTex GUI, and repeating until all the errors went away. This may
be purely because I default to a lean system and don't go for these
huge meta-packages. If one chooses to install the [La/Lua/Xe]Tex
world, this might not be the case! I have the same procedure on linux
with TexLive where I have a default starting set of pkgs and just run
tlmgr on whatever errors I encounter.
Just one other data point!
The first step is to make sure "pdflatex" is recognized, period. This
is still not answered.
John
>
> Let us know. Good luck.
>
> --Rishabh
>
>
> On Mar 14 2018, at 3:24 pm, Dereje Tefera <tefera@ualberta.ca> wrote:
>
>
> I saw that there is one error:
>
> "! Package minted Error: You must have `pygmentize' installed to use this
> package." but when I try to install from the package list says no match.
> and a warning:
>
> "Package inputenc Warning: inputenc package ignored with utf8 based
> engines."
>
>
>
> Do you think it would be better to reinstall emacs?
>
>
> Regards
>
> Dereje
>
>
> On Wed, Mar 14, 2018 at 12:28 PM, Eric S Fraga <esflists@gmail.com> wrote:
>
> On Wednesday, 14 Mar 2018 at 11:39, Dereje Tefera wrote:
>> Dear John and R Jain,
>>
>> I have done all required installation for the Latex and it worked for a
>> couple of times but it then crashes. This is the error message I am
>> getting while trying to export to Latex PDF or Beamer. I really appreciate
>> your cooperation but I completely if you are busy.
>
> So, it looks like LaTeX is now being found but that there are errors in
> the LaTeX created by org. Have you looked at the LaTeX output buffer,
> as the error message suggests?
>
>> Debugger entered--Lisp error: (error "File
>> \"c:/Users/deret/Desktop/examp3.pdf\" wasn’t produced. See \"*Org PDF
>> LaTeX Output*\" for details")
>
> The error will likely be near the end of the buffer.
>
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-303-g6cf5fc.dirty
next prev parent reply other threads:[~2018-03-15 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 21:40 org mode error "pdf wasn't produced" Dereje Tefera
2018-03-13 12:28 ` Eric S Fraga
2018-03-13 12:28 ` R Jain
2018-03-13 23:37 ` Dereje Tefera
2018-03-14 0:05 ` John Kitchin
2018-03-14 0:29 ` Dereje Tefera
2018-03-14 1:28 ` John Hendy
2018-03-14 1:29 ` John Hendy
2018-03-14 17:39 ` Dereje Tefera
2018-03-14 18:28 ` Eric S Fraga
2018-03-14 19:24 ` Dereje Tefera
2018-03-14 19:33 ` John Kitchin
2018-03-15 15:06 ` R Jain
2018-03-15 16:09 ` John Hendy [this message]
2018-03-15 16:13 ` Dereje Tefera
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-iQrDKX98C+v60WZzaU0=qZFyGGu9Vitam=gZxbbYBKQ@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rjain.ece@gmail.com \
--cc=tefera@ualberta.ca \
/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).