Dear Harm, wow! I've never seen such display of sheer coding virtuosity! I can spend years trying to understand what you have done. Thank you very much and hope to see this implemented in some release soon. I will apply in my typesettings and if something strange happens -I don't think so-, I'll write to you.
Thanks again, F. > ---------- Forwarded message ---------- > From: Thomas Morley <[email protected]> > To: Lukas-Fabian Moser <[email protected]> > Cc: Federico Sarudiansky <[email protected]>, lilypond-user < > [email protected]> > Bcc: > Date: Sun, 18 Apr 2021 17:53:09 +0200 > Subject: Re: Chromatic clashes > > > Am Sa., 17. Apr. 2021 um 14:15 Uhr schrieb Lukas-Fabian Moser <[email protected] > >: > >> Hi Federico, >> Am 17.04.21 um 01:10 schrieb Federico Sarudiansky: >> >> Hi, >> >> in addition to that, I've on occations had to engrave >> [image: image.png] >> >> Yes, that would have been the follow-up to my question: This is even >> worse, for LilyPond turns >> >> \version "2.22.0" >> >> { <c' cis' d'> } >> >> into >> >> But there are interesting snippets and postings for that: >> >> >> https://lilypond.org/doc/v2.22/Documentation/snippets/chords.html#chords-displaying-complex-chords >> https://lists.gnu.org/archive/html/lilypond-user/2012-07/msg00336.html >> https://archiv.lilypondforum.de/index.php/topic,1176.msg6932.html#msg6932 >> >> In particular, Harm's coding in the third link (although marked for >> version 2.16.0) still compiles with 2.22 >> >> Lukas >> >> >> Somewhere on the list there might be a newer coding of mine. > Anyway, I took the opportunity to rework it. > See attached. > I'm pretty sure there are still bugs in it, please report them here on the > list. > > Cheers, > Harm > _______________________________________________ > lilypond-user mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/lilypond-user >
