From: Jeff Horn <jrhorn424@gmail.com>
To: Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: Texi2dvi: forcing a recompile?
Date: Thu, 2 Dec 2010 17:56:47 -0500 [thread overview]
Message-ID: <AANLkTikX-Q5aYJDZShC8Mm=5cWkXugacDVOaD1HqZHt-@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=ASBt-Rs+xVMjSVG3PtAoWyP4bP7oxmf1iG2Tb@mail.gmail.com>
BTW, the HTML file is updated fine in the output directory. Seems like
it *is* texi2dvi.
Jeff
On Thu, Dec 2, 2010 at 5:55 PM, Jeff Horn <jrhorn424@gmail.com> wrote:
> Just a heads up: it looks like using texi2dvi for
> org-latex-to-pdf-process will not recompile a tex file in certain
> cases. I have different output and source directories, and when I
> publish a changed org file, texi2dvi appears to not process a tex file
> when the pdf is already in the output directory.
>
> I guess this could be an org-mode bug, since that default behavior
> doesn't make sense and texi2dvi doesn't have a "force" flag. To me, it
> appears that org-mode picks up the change in the org file and creates
> the tex document correctly. The pdf isn't recreated unless I delete
> the pdf in the output directory and then call org-publish-project
> again.
>
> Jeff
>
> --
> Jeffrey Horn
> Graduate Lecturer and PhD Student in Economics
> George Mason University
>
> (704) 271-4797
> jhorn@gmu.edu
> jrhorn424@gmail.com
>
> http://www.failuretorefrain.com/jeff/
>
--
Jeffrey Horn
Graduate Lecturer and PhD Student in Economics
George Mason University
(704) 271-4797
jhorn@gmu.edu
jrhorn424@gmail.com
http://www.failuretorefrain.com/jeff/
next prev parent reply other threads:[~2010-12-02 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 22:55 Texi2dvi: forcing a recompile? Jeff Horn
2010-12-02 22:56 ` Jeff Horn [this message]
[not found] ` <4CFAA27C.3020509@pobox.com>
2010-12-04 20:22 ` Jeff Horn
2010-12-04 20:28 ` Jeff Horn
2010-12-04 20:46 ` Joost Kremers
2010-12-04 21:17 ` Jeff Horn
2010-12-04 22:50 ` Mike McLean
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='AANLkTikX-Q5aYJDZShC8Mm=5cWkXugacDVOaD1HqZHt-@mail.gmail.com' \
--to=jrhorn424@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).