From: John Kitchin <jkitchin@andrew.cmu.edu>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Org latex pdf syncing
Date: Sun, 17 Sep 2017 18:55:27 -0700 [thread overview]
Message-ID: <m2inggkbxs.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <m2tw01yzkm.fsf@tsdye.com>
I used this minor mode:
https://github.com/jkitchin/scimax/blob/master/ox-manuscript/ox-manuscript.el#L949
long enough to see that it kind of worked. It basically launched an
async export every time you saved an org file. If you have a pdf viewer
that will refresh when it changes on disk, it is pretty close to real
time syncing if your pdf doesn't take long to build. There is no jumping
back and forth though.
Thomas S. Dye writes:
> Nick Dokos writes:
>
>> Amos Bird <amosbird@gmail.com> writes:
>>
>>> Hi,
>>>
>>> Is there a way to support pdf syncing when exporting and opening pdf in org mode?
>>>
>>
>> Meaning that if you make a change to the org file, you see the change immediately
>> in the displayed PDF? I don't think there is a built-in way to do that.
>
> Or, if syncing means what SyncTeX does for TeX source code, so that it
> is possible to jump back and forth to the same place in the TeX and pdf
> documents, the answer is the same as Nick's, that there is no built in
> way to do that in Org mode.
>
> All the best,
> Tom
--
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
next prev parent reply other threads:[~2017-09-18 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 17:07 Org latex pdf syncing Amos Bird
2017-09-17 17:53 ` Nick Dokos
2017-09-17 18:01 ` Thomas S. Dye
2017-09-18 1:55 ` John Kitchin [this message]
2017-09-18 2:50 ` Eduardo Mercovich
2017-09-18 2:58 ` Amos Bird
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2inggkbxs.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
--cc=tsd@tsdye.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.