Re: Double-underline markup

[Thomas Morley]

Am Sa., 19. Okt. 2019 um 06:58 Uhr schrieb Andrew Bernard
<address@hidden>:
>
> That's funny - it's the argument I always use for my new complexity work, but 
> it usually gets shouted down quite vocally (refer for example to my 
> requirement for equal width bars!).

Nah, it's not shouted down. ;)
Though, there are two points to consider, imho
(1) I don't understand how equal width bars should work at all, p.e. {
\repeat unfold 32 b32 b1 }
(2) I've no clue how it could be implemented.

Looks like it's not only me...

> Anyway, that's why I offered to put in in openlilylib, there for all to use 
> if desired.
>
> Maybe what we really need is a section on the NR on how to use openlilylib, 
> because people seem to find it difficult (which I find puzzling, but 
> everybody's experience with computers is of different degree). There's 
> precedent for that, almost. We have a section on using lilypond with external 
> programs like editors. That would also have the effect of bringing 
> opnelilylib more into the core consciousness, rather than being an orphan 
> stepchild as it is viewed now, I think.

Well, I have to admit I stumbled across "how am I supposed to use it"
as well. Mostly because I overlooked the Wiki-button, where all is
explained...
Furthermore openlilylib provides an own infrastructure, it is
_designed_ to use it as a whole library.
This is boon and bane at the same time, making it impossible to simply
copy/paste some code (unlike LSR).
I think many people like the design as a git-based library with the
current infrastructure.
Though it has disadvantages as well. The problem with copy/paste short
snippets I already mentioned. Furthermore one can't share ly-code
between people relying on openlilylib-functionality and those not
having installed openlilylib at all.

Well, these are my own thoughts about openlilylib.
Furthermore github is nowadays owned by microsoft. I don't think it is
appropriate for GNU software to point to such site.

I may be wrong here, if I'm wrong we _should_ document how to use it.

My 2 cts,
  Harm