From: Jude DaShiell <jdashiel@panix.com>
To: John Hendy <jw.hendy@gmail.com>, Matt Price <moptop99@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: minimal testing setup for pdf export?
Date: Fri, 30 Aug 2019 14:11:12 -0400 [thread overview]
Message-ID: <alpine.NEB.2.21.1908301409590.459@panix1.panix.com> (raw)
In-Reply-To: <CA+M2ft8vstyQ5Cp+txam-EOcL7JnUNWRoUawm=WpyQZMEB6Zmg@mail.gmail.com>
It would be helpful if when pdf get exported from orgmode they have
speech enabled by default.
On Fri, 30 Aug 2019, John Hendy wrote:
> Date: Fri, 30 Aug 2019 10:45:08
> From: John Hendy <jw.hendy@gmail.com>
> To: Matt Price <moptop99@gmail.com>
> Cc: org-mode-email <emacs-orgmode@gnu.org>
> Subject: Re: [O] minimal testing setup for pdf export?
>
> Whew, the world is whole again! No worries, and I've been in the exact
> same situation more than I'd like. We joke at work that if you want to
> fix a problem, just ask someone to come watch it happen and it will
> magically go away :)
>
> Glad you're on your way!
> John
>
> On Fri, Aug 30, 2019 at 9:27 AM Matt Price <moptop99@gmail.com> wrote:
> >
> >
> >
> > On Thu, Aug 29, 2019 at 11:27 AM John Hendy <jw.hendy@gmail.com> wrote:
> >>
> >> On Tue, Aug 27, 2019 at 6:34 PM Matt Price <moptop99@gmail.com> wrote:
> >> >
> >> >
> >> >
> >> > On Tue, Aug 27, 2019 at 1:33 PM John Kitchin <jkitchin@andrew.cmu.edu> wrote:
> >> >>
> >> >> that does suggest that pdflatex is getting called somewhere else.
> >> >>
> >> >> Maybe you can edebug the export function and check the value of default-directory to see where it is getting called.
> >> >>
> >> >> You could also try this
> >> >>
> >> >> #+BEGIN_SRC emacs-lisp
> >> >> (defun my-build (quoted-tex-file)
> >> >> (message "Building %s. Called from %s" quoted-tex-file default-directory))
> >> >>
> >> >> (setq org-latex-pdf-process 'my-build)
> >> >> #+END_SRC
> >> >>
> >> >> It won't build the pdf, but it will tell you in the messages where it was called from. It might help figure out what is happening.
> >> >
> >> >
> >> > huh. that was kinda cool... but the value of default-directory seems to be correct. However, this helped a bit:
> >> >
> >> > #+BEGIN_SRC emacs-lisp
> >> > (shell-command-to-string "echo $PWD")
> >> >
> >> > #+END_SRC
> >> >
> >> >
> >> > #+RESULTS:
> >> > : /home/matt/src/org-mode
> >> >
> >> > Not sure what's going on here, but this value is the same in a regular emacs and "emacs -Q". is this normal?
> >> >
> >>
> >> Did this get solved? It kind of bothers me to think it hasn't. I also
> >> think this is a case where erring on the side of overwhelming details
> >> would help a lot. Could you start from the beginning with the exact
> >> process using emacs -Q, post the full output of *Messages* and *Org
> >> PDF LaTeX Output*? Like in the above, you post the output of $PWD, but
> >> not what the *Messages* buffer contained from John's code. Maybe they
> >> are the same, maybe they are different, but we can't tell.
> >>
> >> Example:
> >> $ cd ~/
> >> $ emacs -Q
> >>
> >> M-x org-version
> >> Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
> >> /usr/share/emacs/26.2/lisp/org/)
> >>
> >> C-x C-f pdf-test.org
> >>
> >> File contents:
> >> * foo
> >> <eof>
> >>
> >> C-x C-s
> >> C-c C-e l p
> >>
> >> $ ls ~/
> >> pdf-test.org
> >> pdf-test.pdf
> >> pdf-test.tex
> >>
> >> Alternatively, insert the code from John Kitchin:
> >>
> >> Wrote /home/jwhendy/pdf-text.org
> >> org-babel-exp process emacs-lisp at position 8...
> >> Saving file /home/jwhendy/pdf-text.tex...
> >> Wrote /home/jwhendy/pdf-text.tex
> >> Processing LaTeX file pdf-text.tex...
> >> Building pdf-text.tex. Called from /home/jwhendy/
> >> org-compile-file: File "/home/jwhendy/pdf-text.pdf" wasn?t produced.
> >> See "*Org PDF LaTeX Output*" for details
> >>
> >> I still don't feel I understand the full nature of your working
> >> directory, what does and doesn't get saved in that directory, etc. I'd
> >> love to help, but am not able to replicate for you!
> >>
> >> Thanks,
> >> John
> >>
> > John H,
> > Thank you so much for the detailed instructions. I had a moment this morning so I updated Emacs, rebooted my laptop, and started to follow your instructions as closely as possible... and I can no longer reproduce my problem. I feel like I should be happier than I am! I wonder if perhaps there was some kind of strange path problem caused by a software update that I didn't pay attention to.
> >
> > In any case, I am as always grateful for the efforts of people on this list -- I learned at least a little bit about latex export and feel that I might finally be getting a little closer to where I need to be.
> >
> > Meanwhile, if the issue shows up again I'll be sure to check back in.
> >
> > Thanks!
> > Matt
> >
> >
> >>
> >>
> >> >
> >> >> John
> >> >>
> >> >> -----------------------------------
> >> >> Professor John Kitchin
> >> >> Doherty Hall A207F
> >> >> Department of Chemical Engineering
> >> >> Carnegie Mellon University
> >> >> Pittsburgh, PA 15213
> >> >> 412-268-7803
> >> >> @johnkitchin
> >> >> http://kitchingroup.cheme.cmu.edu
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Aug 27, 2019 at 8:57 AM Matt Price <moptop99@gmail.com> wrote:
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Tue, Aug 27, 2019 at 8:27 AM John Kitchin <jkitchin@andrew.cmu.edu> wrote:
> >> >>>>
> >> >>>> Can you manually compile the empty.tex file from the command line? eg
> >> >>>>
> >> >>>> pdflatex empty
> >> >>>>
> >> >>> (reposting to group)
> >> >>>
> >> >>> pdflatex empty
> >> >>>
> >> >>> Seems to work fine. Hmmm...
> >> >>>>
> >> >>>> John
> >> >>>>
> >> >>>> -----------------------------------
> >> >>>> Professor John Kitchin
> >> >>>> Doherty Hall A207F
> >> >>>> Department of Chemical Engineering
> >> >>>> Carnegie Mellon University
> >> >>>> Pittsburgh, PA 15213
> >> >>>> 412-268-7803
> >> >>>> @johnkitchin
> >> >>>> http://kitchingroup.cheme.cmu.edu
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> On Tue, Aug 27, 2019 at 7:57 AM Julius Dittmar <Julius.Dittmar@gmx.de> wrote:
> >> >>>>>
> >> >>>>> Am 27.08.19 um 12:34 schrieb Matt Price:
> >> >>>>> > This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch
> >> >>>>> > Linux) (preloaded format=pdflatex)
> >> >>>>> > restricted \write18 enabled.
> >> >>>>> > entering extended mode
> >> >>>>> > ! I can't find file `empty.tex'.
> >> >>>>>
> >> >>>>> So pdflatex is called and found. Then pdflatex can't find empty.tex.
> >> >>>>> That looks like pdflatex is called in another directory than where
> >> >>>>> empty.tex resides. How that could happen, no idea.
> >> >>>>>
> >> >>>>> Julius
> >> >>>>>
>
>
--
next prev parent reply other threads:[~2019-08-30 18:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 1:20 minimal testing setup for pdf export? Matt Price
2019-08-27 3:26 ` Ken Mankoff
2019-08-27 6:14 ` Robert Klein
2019-08-27 10:34 ` Matt Price
2019-08-27 11:55 ` Julius Dittmar
2019-08-27 12:26 ` John Kitchin
2019-08-27 12:57 ` Matt Price
2019-08-27 17:32 ` John Kitchin
2019-08-27 23:33 ` Matt Price
2019-08-28 8:29 ` Julius Dittmar
2019-08-29 15:27 ` John Hendy
2019-08-30 14:13 ` Matt Price
2019-08-30 14:45 ` John Hendy
2019-08-30 18:11 ` Jude DaShiell [this message]
2019-08-30 20:07 ` Nick Dokos
2019-08-30 21:10 ` Jude DaShiell
2019-08-30 23:31 ` Tim Cross
2019-08-30 23:59 ` Jude DaShiell
2019-08-31 1:46 ` Tim Cross
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=alpine.NEB.2.21.1908301409590.459@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
--cc=moptop99@gmail.com \
/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).