Re: Fonts from the former fonts.openlilylib.org

I have found the orignial SIL-licensed files available on the internet, and have made a new GitHub organization and corresponding repositories for the fonts themselves. Please see https://github.com/OpenLilyPondFonts I've included all that I could find from fonts.openlilylib.org, as well as

LilyBin.com wedged?

It looks like lilybin.com is internally wedged or something? The right hand side is just showing a "please wait" spinner for me, and the "Preview" button is greyed. Steve ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Good recipe for numeric scale degree? (numerals with hat/caret)

Wow that looks pretty great, thanks! On Wed, Dec 16, 2015 at 2:06 PM, Klaus Blum wrote: > Hi Steve, > > what about > > % -- > #(set-global-staff-size 48) > > #(define-markup-command (hat layout props text) (markup? ) >

Clashing ties & slurs with tieWaitForNote

Any thoughts on avoiding these clashes without having to manually tweak all the slurs? [image: Inline image 1] http://lilybin.com/5sfp1b/1 \score{ { \set tieWaitForNote = ##t c''2 \( ~ b'4 \) c''4 c''2 ~ b'4 \( c''4 \) } \layout{} \midi{} } ___

Re: Clashing ties & slurs with tieWaitForNote

pe=node=183908=0>> wrote: > >> >> >> Am 21.11.2015 um 18:18 schrieb Steve Lacy: >> >> Any thoughts on avoiding these clashes without having to manually tweak >> all the slurs? >> >> >> Yes, writing semantically correct notes, like thi

Re: Emacs lilypond-mode and also point-and-click

On Thu, Oct 15, 2015 at 8:03 AM, T. Michael Sommers wrote: > On 10/15/2015 7:24 AM, Andrew Bernard wrote: > >> >> I’m aware that the emacs lilypond-mode needs attention, but I wonder >> if anybody has seen this. When I enter a ‘>’ character to complete a >> chord, emacs

Gallery of Interesting Music Notation

I found this fascinating: http://homes.soic.indiana.edu/donbyrd/InterestingMusicNotation.html I wonder if anyone here (or elsewhere) has tried to engrave some of these, even as musical fragments? I'm sure it would be an eye-opening process. :) Steve

Re: Fwd: [smufl-discuss] SMuFL development moves to the new W3C Music Notation Community Group

I've experimented with this a bit on WikiPedia directly, but it seemed to me to be a limited set of LilyPond functionality, but I didn't dig much farther than that. You can see this extension in action here, on the page for Beethoven's 5th: https://en.wikipedia.org/wiki/Symphony_No._5_(Beethoven)

Re: Fwd: [smufl-discuss] SMuFL development moves to the new W3C Music Notation Community Group

tisimst.lilyp...@gmail.com wrote: On Wed, Jul 29, 2015 at 11:32 AM, Steve Lacy [via Lilypond] [hidden email] http:///user/SendEmail.jtp?type=nodenode=179139i=0 wrote: You're incorrect in saying that this requires Lilypond on the Users machine. It does require LilyPond on the serving machine(s

Re: OT: (Web) server administration advice

Web server mailman are pretty straightforward, even with a fairly large number of domains. Once you get the first one done, you can pretty much cut paste to generate the rest of the configs with unique DocumentRoots, or however you're structuring things. Make sure to use apache2's conf.d

Re: How many lilypond users are there?

Not that this is any indication of install userbase, but there are 117 repositories on GitHub that match language:LilyPond https://github.com/search?utf8=%E2%9C%93q=language%3ALilyPond Additionally, there are 90 people subscribed to the LilyPond subreddit on reddit.com:

Re: What is the problem with \relative? (Was: Do we really offer the future?)

+1 to Keith's idea. In fact, I remember first learning about \relative and being *amazed* that it didn't work as described. I'm mostly transcribing/re-engraving for solo violin, and most pieces stay within a small 2-octave range. The \relative c'''{ ...} syntax was exactly what I wanted. Steve

Re: ugly default output

On Sat, Feb 28, 2015 at 3:11 PM, Urs Liska u...@openlilylib.org wrote: Yes, but I'd repeat that this is less LilyPond's fault than a problem of having an amount of music that is inherently unsuitable to be typeset nicely on one system. I'll have to say that I find this perspective a bit

Re: Git/Lilypond workflow

Hi, I'm a software engineer by trade and have been using git for software development for quite some time. Let me first start saying that there are *many* different possible workflows, and each user needs to come up with their own workflow that they're comfortable with. With respect to

Re: tie to {} \\ {}

Putting the d~ and ees~ inside the ... block gets a bit closer. You can see the ties, but has other differences from your original example. I'm not sure exactly what your final goal is: \relative c' { { d16~ \once \override NoteColumn.force-hshift = #-0.6 \once \override Stem.direction = #DOWN

Re: How to pack notes very tightly?

-shortest-duration is the variable that really needs to be tweaked. Steve On Mon, Jan 19, 2015 at 11:07 PM, Urs Liska u...@openlilylib.org wrote: Am 20. Januar 2015 07:47:20 MEZ, schrieb Steve Lacy sl...@slacy.com: I'm transcribing a Mendelssohn score, and am trying to get Lilypond to pack notes

How to pack notes very tightly?

I'm transcribing a Mendelssohn score, and am trying to get Lilypond to pack notes about as densely as they are in the original score. For example, trying to fit a snippet like this onto a single line: \version 2.16.2 \language english \relative c''' { \key e \minor \mark \default \time 2/2

Vertical alignment of text added to notes.

Hi, I'm engraving some simple music for beginning violin students who are learning to read music. I would prefer if the text added to notes were vertically aligned on each line, but by default they are quite jagged: [image: Inline image 1] (http://lilybin.com/to3r9r/3) I had thought about using

Re: Vertical alignment of text added to notes.

Ah, perfect thank you very much! On Thu, Jan 8, 2015 at 11:28 AM, David Nalesnik david.nales...@gmail.com wrote: Hi Steve, On Thu, Jan 8, 2015 at 1:11 PM, Steve Lacy sl...@slacy.com wrote: Hi, I'm engraving some simple music for beginning violin students who are learning to read music. I