Mark Knoop writes:
>>> The point-and-click link in the resulting pdf is relative:
>>> textedit://testpaths.ly:9:2:3 - and therefore doesn't work.
>>
>>Hm, the PDF you attached *does* give an absolute link, but:
>
> Yes, sorry, testing with different versions and attached the wrong one.
> See atta
>> The point-and-click link in the resulting pdf is relative:
>> textedit://testpaths.ly:9:2:3 - and therefore doesn't work.
>
>Hm, the PDF you attached *does* give an absolute link, but:
Yes, sorry, testing with different versions and attached the wrong one.
See attached pdf now.
>Indeed, this i
Am 17.05.2016 um 09:31 schrieb Mark Knoop:
> Thanks Urs,
>
> At 09:37 on 13 May 2016, Urs Liska wrote:
>> Which version of LilyPond and what Linux exactly do you use (2.19.40
>> binary release?)?
> lilypond 2.19.40, on Fedora 23, distro build (lilypond-2.19.40-1.fc23)
>
> However I have just down
Thanks Urs,
At 09:37 on 13 May 2016, Urs Liska wrote:
>Which version of LilyPond and what Linux exactly do you use (2.19.40
>binary release?)?
lilypond 2.19.40, on Fedora 23, distro build (lilypond-2.19.40-1.fc23)
However I have just downloaded 2.19.41 binary release from lilypond.org
and see th
Which version of LilyPond and what Linux exactly do you use (2.19.40
binary release?)?
Compiling your example with LilyPond built from current master gives me:
Starting lilypond 2.19.42 [Untitled]...
Processing `/tmp/frescobaldi-dW8ldh/tmpTuF3xf/document.ly'
Parsing...
/tmp/frescobaldi-dW8ldh/tmp
The commit below has broken point-and-click links for me on Linux.
Embedded paths are now relative rather than absolute. It seems the
assumption in the commit message that an absolute path is always
returned is incorrect, as can be seen with the following example.
Reverting scm/output-ps.scm fixes
