>>> The pseudoIndent wiki has acquired errors in several places, not
>>> just the .ily code but also the instructions and the demo code.
>>
>> This can easily happen, but...
>
> I then think: what a damning admission!
>
> The LSR wasn't like that for me.
Well, it's a fact that LSR is no longer available. Jean kindly
provides a Wiki.
> - Gardener Harm did his rounds at each stable version
Gardener Harm is very busy with other things. Right now, he doesn't
participate at all in the Wiki.
>> ... why not update the Wiki accordingly?
>
> because that doesn't solve the problem that 'This can easily
> happen'.
I don't see the problem. Contrary to the LSR, the Wiki comes with a
complete history of every change, which is a *huge* improvement. With
a single mouse click you can restore an older version if ever
necessary.
> And when it does happen, it wastes the time of an unsuspecting user,
> wastes my time helping out and starts giving pseudoIndent a bad
> name.
Do you speak from experience? If so, please elaborate.
>>> The purged wiki page need only provide a link to the update series
>>> [3], but maybe also displaying the demo.pdf would be appropriate.
>>
>> There must be a very good reason to do that,
>
> There is. It solves the problem that 'This can easily happen'.
> Not in a trendy way, but very effective - and no scraping
> required!!!
I strongly disagree. Sending modifications of a snippet repeatedly to
the lilypond-user mailing list is a nightmare in the long run. Doing
it once or twice is OK, but everything else pollutes the mailing list
IMHO. If you really want to maintain a snippet outside of the Wiki,
please set up a git repository. We can then update the Wiki with a
recent version from the git, also adding a link to get a PDF version
(in case Wiki's SVG version isn't good enough).
Werner
