Now that I've got my git stuff working (thanks Johannes, Patrick, and Reinhold)
and the
fret-diagram-details refactor in place, I'm ready to start working on my next
project, which
is to make the FretBoards context print out predefined fret-diagrams instead of
calculating
them from the notes.
M
Sorry about the top-posting -- I'm stuck on microsoft webmail for right now.
I looked at python/convert-rules.py. That's how I arrived at the proposed rule
at the bottom of my text file. If I have done it wrong, I'd like to know about
it.
Carl
From: Gra
On Wed, 18 Jun 2008 09:55:56 -0600
"Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> I've never written a convert-ly rule before, and I don't know how to
> submit them if I did (I guess I could just change convert-ly on the
> csorensen fork, and then it would be part of the cherry picking).
It's pr
2008/6/18 Jorge Branco <[EMAIL PROTECTED]>:
> Hello
Greetings,
> How would I go to create a midi file from this code? Is there any specific
> code
> to add to my file, or is it any export option?
It's explained on
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/MIDI-output
As Graham
You would read the documentation and/or -user mailist. This isn't
related to the -devel mailist.
- Graham
On Wed, 18 Jun 2008 18:28:58 + (UTC)
Jorge Branco <[EMAIL PROTECTED]> wrote:
> Hello
>
> I have the following code:
>
> \header{
> title = "A scale in LilyPond"
> }
>
> \relative{
2008/6/12 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> the inefficiency of computing things twice is not that important. I'm
> a bit more concerned with duplication of logic, if there is any. Can
> you fold things together into a common function?
As it stands the only duplication would be the code f
Hello
I have the following code:
\header{
title = "A scale in LilyPond"
}
\relative{
c d e
}
How would I go to create a midi file from this code? Is there any specific code
to add to my file, or is it any export option?
Thanks
___
lilypond-dev
2008/6/17 John Mandereau <[EMAIL PROTECTED]>:
> Output files depend on .ly files, .snippet-list files,
> lilypond-snipets.tely and -intro.itely files. If the modification time
> of any of this file is updated (with real changes or with touch),
> lilypond-book, makeinfo and texi2pdf are called aga
Han-Wen,
I've finally got the csorensen fork ready for cherry picking. It includes a
completely revised file input/regression/fret-diagrams.ly, along with
modifications to scm/define-grobs, scm/define-interfaces,
scm/define-grob-properties, and scm/fret-diagrams. It adds a few new
fret-diagr
On Wed, 18 Jun 2008 10:00:43 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/6/17 Mats Bengtsson <[EMAIL PROTECTED]>:
>
> > No, \null doesn't have any vertical extent.
>
> Then instead of always using \hspace #0 as an anchor point, we'd
> better use \null.
Old discussion that might
2008/6/17 Mats Bengtsson <[EMAIL PROTECTED]>:
> Perhaps it's time to continue the thread from
> http://lists.gnu.org/archive/html/bug-lilypond/2006-01/msg00163.html ?
Indeed! \center-align is quite confusing the way it is now.
Fortunately, since the GDP policy prevents me from using the actual
co
2008/6/13 Valentin Villenave <[EMAIL PROTECTED]>:
> Here's a patch against gub to implement a much useful feature for
> those of us who run lilypond from the command line using a bash shell
> (included by default in most linux/BSD distributions).
Hi,
Has anyone had a look at my patch yet?
http:/
On Wed, Jun 18, 2008 at 3:18 AM, Reinhold Kainhofer
<[EMAIL PROTECTED]> wrote:
> Now that musicxml2ly has been noticed as doing quite a good job, I'm thinking
> of adding a MusicXML backend to lilypond, so that we can also produce
> MusicXML and export lilypond scores to e.g. Finale, etc.
>
> Howev
13 matches
Mail list logo
