From: Rainer M Krug <Rainer@krugs.de>
To: Brett Viren <bv@bnl.gov>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Reverse lookup from pdf to org?
Date: Thu, 27 Mar 2014 15:43:45 +0100 [thread overview]
Message-ID: <m2eh1nwvku.fsf@krugs.de> (raw)
In-Reply-To: <ir438i3btny.fsf@lycastus.phy.bnl.gov> (Brett Viren's message of "Thu, 27 Mar 2014 10:30:41 -0400")
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Brett Viren <bv@bnl.gov> writes:
> Rainer M Krug <Rainer@krugs.de> writes:
>
>> Brett Viren <bv@bnl.gov> writes:
>>> file:///path/to/foo.tex.orglink?line=42
>
>> But jumping to the .org file would be the aim - right?
>
> Yes, right. Maybe a better example is:
>
> file://foo.orglink?line=42
calling
,----
| emacs +42 foo.org
`----
should open the file foo.org and put the cursor in line 42.
>
> which might get interpreted as "go to line 42 in ./foo.org".
>
> This example is also a relative link which would be less brittle as long
> as foo.org and foo.pdf are kept together in the same directory.
Yes - that would be quite useful.
>
>>> Chance of success: 10%
>>
>> I guess higher?
>
> I like your optimism!
I am an optimist :-)
Cheers,
Rainer
>
> -Brett.
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4474 bytes --]
next prev parent reply other threads:[~2014-03-27 14:43 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
2014-03-27 9:12 ` Rainer M Krug
2014-03-27 14:30 ` Brett Viren
2014-03-27 14:43 ` Rainer M Krug [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2eh1nwvku.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=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 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.