lytex document following line: \lipsum \the\linewidth) and then report the value into the line-width option. I tried also to print the value of \linewidth ( i.e. I tried \lilypondfile (and with \textwidth). A similar question is reported in the lilypond mailing list, but the solution is to manually adjust the line-width that is imho not satisfactory. Of course, I am not using the quote option of \lilypondfile.
#Lilypond mailing list how to
In other terms, how to make the blue lines match the red ones in following example: My question: How to make the snippet justified, i.e. some music staffs) embedded within a document containing text. so that you can spend less time notating music and more time creating music. It automates most of your typesetting workflow. Elysium puts the fun back to using LilyPond. So I'd still say that the primary location for basic lilypond usage questions is Musical Practice & Performance.Īs a final note, prompted by PeterBjuhr comments/answer, one of the reasons why there are so few questions is because lilypond has an active and helpful mailing list and you're likely to get better answers there (at least for now).I have a lilypond snippet (i.e. Welcome to Elysium, the Zen Garden of LilyPond Feeling inefficient or unproductive when working on sheet music with LilyPond Relax. However, to date it looks like all of the questions are "how do I get lilypond to output what I want" (Music Practice) rather than "how do I do complicated programming within a lilypond file" (SuperUser), Program in guile within their lilypond files, could be more of a Superuser or Stack Overflow type of question. I can see an argument that more complicated lilypond scripting, i.e. I'm certain that there are many users who are experience in how to read lay-out music notation in general, and there are a few who are using lilypond specifically. I've always considered lilypond to be directly on topic for Musical Practice & Performance, given the indication that "usage of specific music software" is on topic. commentary that is too long to format as a comment): Of course, we could just conclude that they're off-topic everywhere on SE at the moment, and so should be confined to the LilyPond mailing list, but that sounds overly dogmatic and inflexible to me.Įxpanding on Frankston's answer (i.e. Due to the nature of our products if your order is not picked up as scheduled there will be a restocking fee of either 25 or 20, whichever is higher. It doesn't seem sensible to ask questions in "the right place", when they stand a better chance of being answered in "the slightly less right place". On the other, you could argue that a non-programmer on Music.SE is much more likely to be using the GUI than LilyPond anyway, and - depending on the complexity of the required solution - not equipped to actually formulate an answer by writing code. On the one hand, this is similar in principle to asking how to use a particularly complex GUI to achieve the same result, making the question purely about usage and so off-topic for SO.
#Lilypond mailing list code
There's an argument to be made that - as they effectively contain code - LilyPond input files can become so inscrutable to anyone but programmers, that questions about them are (a) unlikely to find answers on Music.SE (or, to a lesser extent, SuperUser), and (b) on-topic as programming questions for Stack Overflow (though this is maybe a bit more controversial).
0 kommentar(er)
