Dear all,
in case there are people like me interested in having a basic syntax for
inputting text spanners, I wrote three simple functions for that matter:
\textSpan, \textSpanArrow and \textSpanDoubleArrow. They replace in
practice following overrides with user input:
\override TextSpanner.bound
Am So., 20. Sept. 2020 um 17:30 Uhr schrieb Xavier Scheuer
:
>
> On Sun, 20 Sep 2020 at 13:03, Thomas Morley wrote:
> >
> > Hi Martin,
> >
> > in general I'm more with Aaron.
> > P.e., I have no clue which default text one could think of for
> > TextSpanner's left/right-text!?
> > Otoh, I'd wish w
On Sun, 20 Sep 2020 at 13:03, Thomas Morley
wrote:
>
> Hi Martin,
>
> in general I'm more with Aaron.
> P.e., I have no clue which default text one could think of for
> TextSpanner's left/right-text!?
> Otoh, I'd wish we'd have a LilyPond-data-structure to assign a list of
> key/value pairs in ly-
Hi Thomas,
thank you for your interest in this very constructive discussion with Aaron!
> in general I'm more with Aaron.
> P.e., I have no clue which default text one could think of for
> TextSpanner's left/right-text!?
Exactly, me neither. Forcing the default to be empty text without giving the
Am So., 20. Sept. 2020 um 12:05 Uhr schrieb Martín Rincón Botero
:
>
> In short, you and I simply
>
> disagree on what is satisfactory for syntax.
>
>
> Well, it seems we already agreed on one satisfactory syntax with the way you
> finished the script in the other thread, so I suppose it’s not imp
> In short, you and I simply
> disagree on what is satisfactory for syntax.
Well, it seems we already agreed on one satisfactory syntax with the way you
finished the script in the other thread, so I suppose it’s not impossible to
agree on something ;-).
> We just come to LilyPond from two differ
On 2020-09-19 12:31 am, Martín Rincón Botero wrote:
[ . . . ]
I was going to comment on your reply in greater detail, but I realized
it would not be terribly productive. In short, you and I simply
disagree on what is satisfactory for syntax. And that is not a bad
thing. We just come to Li
> I am uncertain what you mean by "proper" markup syntax.
Sorry, I meant syntax for markup tagging.
> while interesting, is invalid syntax and surely not proper. Perhaps
> you simply meant something that *looks* like it could be valid LilyPond.
how can a proposed syntax (for which functions have
On 2020-09-18 2:06 pm, Martín Rincón Botero wrote:
[...] There are two
unsatisfactory problems for usability involved from my point of view.
One
is the impossibility to use proper markup syntax for text spanners.
I am uncertain what you mean by "proper" markup syntax. Even though
they are c