[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: convert-ly question

From: Martin Tarenskeen
Subject: Re: convert-ly question
Date: Sun, 18 May 2014 21:20:30 +0200 (CEST)
User-agent: Alpine 2.11 (LFD 23 2013-08-11)

On Sun, 18 May 2014, Graham King wrote:

 On Sun, 18 May 2014 08:38:09 +0200 (CEST) Martin Tarenskeen wrote:
>  Luckily I don't need this kind of commandline virtuosity. I
       think I
>  can do what I need with one of the first and easiest
> > convert-ly -e **/*.ly

 One more tidbit of painfully-gained experience in this area:  If using a
 solution that walks the directory tree, starting convert-ly processes, it's
 important to do it in a way that limits the number of concurrent invocations
 of convert-ly.  I've managed to wedge OSX by using a tool that failed to do
 that :(

Would this be safer?

ls **/*.ly | while read f; do -e "${f}"; done

Which leads me to another Linux commandline topic:

Which would be faster, on a machine with a multicore cpu and enough RAM?

lilypond & lilypond & lilypond & lilypond
lilypond && lilypond && lilypond.c && lilypond

Thinking of it, I can test this myself.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]