From: Brett Viren <bv@bnl.gov>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Reverse lookup from pdf to org?
Date: Tue, 25 Mar 2014 16:29:27 -0400 [thread overview]
Message-ID: <ir4ppladntk.fsf@lycastus.phy.bnl.gov> (raw)
In-Reply-To: <871txqgla1.fsf@alphaville.bos.redhat.com> (Nick Dokos's message of "Tue, 25 Mar 2014 14:56:06 -0400")
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
Nick Dokos <ndokos@gmail.com> writes:
> One more (half-)possibility is as follows: produce the tex file and
> compile it not with pdflatex, but with plain latex, producing a DVI
> file. Passing the -src option to the latex invocation inserts "source
> specials" into the DVI file that some DVI viewers (in particular, xdvi)
> can interpret to jump back from the DVI view to the (approximate)
> corresponding location in the tex file:
>
> latex --shell-escape -src foo.tex
> xdvi foo.dvi
Okay, here is a crazy idea. Maybe one can use hyperref and place \url{}
and/or \href{}{} macros in the org file. These will turn into clickable
links in the final PDF. In them place URLs that look like:
file:///path/to/foo.tex.orglink?line=42
And then use .mailcap (or whatever MIME config that xpdf/evince/etc
honors) to map the .orglink extension to a script that parses the URL
(does that full URL get passed?) and invokes emacs to open foo.tex at
line 42?
If that much can be made to work (big if!) I see one problem in that the
/path/to will break if the source is moved.
Chance of success: 10%
-Brett.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-03-25 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 10:07 Reverse lookup from pdf to org? Rainer M Krug
2014-03-25 13:11 ` Suvayu Ali
2014-03-27 8:18 ` Rainer M Krug
2014-03-27 8:59 ` Suvayu Ali
2014-03-27 9:04 ` Rainer M Krug
2014-03-25 17:17 ` Brett Viren
2014-03-25 18:56 ` Nick Dokos
2014-03-25 20:29 ` Brett Viren [this message]
2014-03-27 9:12 ` Rainer M Krug
2014-03-27 14:30 ` Brett Viren
2014-03-27 14:43 ` Rainer M Krug
2014-03-27 14:53 ` Nick Dokos
2014-03-27 15:00 ` Rainer M Krug
2014-03-28 4:49 ` Marcin Borkowski
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=ir4ppladntk.fsf@lycastus.phy.bnl.gov \
--to=bv@bnl.gov \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@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).