[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cairo_outputter::textedit_link
From: |
Jean Abou Samra |
Subject: |
Re: Cairo_outputter::textedit_link |
Date: |
Sat, 23 Sep 2023 16:42:21 +0200 |
User-agent: |
Evolution 3.48.4 (3.48.4-1.fc38) |
Le samedi 23 septembre 2023 à 14:40 +0000, Werner LEMBERG a écrit :
> > > Is there ever a situation where `Cairo_outputter::textedit_link` is
>
> > > called? I've set a breakpoint on this function and run over all
>
> > > files in `input/regression`, but there wasn't a single hit...
>
> >
>
> > Point-and-click.
>
>
> OK, thanks, but it would be great to have some actual LilyPond input
> code to trigger a call of this function. Do you know how to do that?
>
> > Regtests are compiled without it.
>
>
> This is not relevant. I simply used the files from
> `input/regression` as input data for normal `lilypond` calls, not
> within 'make check' or something similar:
>
> ```
> cd input/regression
> for i in *.ly; do
> gdb \
> -ex "break Cairo_outputter::textedit_link" \
> -ex "run" \
> -ex "quit" \
> --args lilypond $i
> done
> ```
If you use the PS backend like in the command above, you
have no chance of triggering functions in the Cairo backend :P
Just add -dbackend=cairo and it will be hit with the simplest
note like { c' } .
signature.asc
Description: This is a digitally signed message part