Re: Specify page number in hyperlink [to pdf]

["Jan Böcker" <jan.boecker@jboecker.de>]

On 30.04.2010 10:10, Nick Dokos wrote:
> Joe Riel <joer@san.rr.com> wrote:
> 
>> Jan Böcker wrote:

>> A related question; can this extension be used with link abbreviations?
>>
>> I tried
>>
>> #+LINK: sample file:/home/joe/sample.pdf
>>
>> with
>>
>> [[sample::3]]
>>
>> but that does not work.
>>
> 
> 
> This happens in org-link-expand-abbrev: it splits sample::3 into
> "sample" and "3", looks up "sample" in org-link-abbrev-alist and
> performs the replacement, then returns the concatenation of that with
> the "3" part, thereby eliminating the "::" marker that would trigger the
> further processing necessary to open the pdf file at the given page.
> 
> You could try
> 
> #+LINK: sample file:/home/joe/sample.pdf::%s
> 
> This will work with the [[sample::3]] link, but not with [[sample]].

Because org-link-expand-abbrev only swallows up to two colons, this
would work (but does look rather silly):
[[sample::::3]]

The following will work with [[sample::3]] and [[sample]], but relies on
the fact that evince, when asked to display page 0, ignores the invalid
page number and just displays page 1 instead:

#+LINK: sample file:/home/joe/sample.pdf::0%s



> 
> Alternatively, you could modify the function to keep the "::" marker
> (at least conditionally: leave it there if it's already there). That
> would make both of the above work and I think all the examples of
> section 4.6 would work as well. Here is a very lighly tested patch:
> 
> [snip]

Nick, the only thing I can think of right now that this would break is
[[bugzilla::129]] (assuming the settings from manual section 4.6).

However, AFAIK this is undocumented behaviour, because the manual does
not mention that an extra ":" between linkword and tag will be silently
ignored.

I agree that applying your patch would be the way to go (this problem is
not related to the extended regex features in org-file-apps; it also
happens when linking to a line number in a plain text file).

Actually, it's half bugfix half new feature:
the bug here is that [[sample:::3]] does not work (one would assume it
does from reading the manual), and the feature is that instead of
accepting that, the patch requires [[sample::3]] instead.

So +1 from me to apply the patch.

- Jan