Re: Changed behaviour of point-and-click

[David Kastrup]

Urs Liska <address@hidden> writes:

> As reported by Mark Knoop in
> http://lists.gnu.org/archive/html/bug-lilypond/2016-05/msg00005.html
> this commit
>
> commit f30a8189adbbeefa2103e2c2e194040f66bc2291
> Author: Urs Liska <address@hidden>
> Date:   Tue Jan 19 10:52:33 2016 +0100
>
>     #4747: Remove (all) uses of is-absolute?
>    
>     The check for absolute paths in  in output-ps.scm
>     and -svg.scm is unnecessary because
>     (car ly:input-file-line-char-column a-location)
>     always returns an absolute, slashified path
>    
>     Now is-absolute? is not used anymore by LilyPond itself.
>
>
> has the side-effect of affecting the point-and-click links. If the file
> path passed to LilyPond is relative the point-and-click links are
> relative as well.
>
> Of course this is an unwanted side-effect of my patch, but I would like
> to discuss if this is a feature rather than a bug.

If it's a feature, the links still need to point to the source
regardless of where LilyPond places the PDF, even if sources are found
through some search path or an include relative from the starting
directory or the including file.  If the PDF path is specified
absolutely, no relative links should be produced: only if the original
connection between source and PDF is relative, the result should be
relative.

Doing this correctly is not easy.  It very likely won't happen by
accident.

-- 
David Kastrup