to fix up git tags.
Hope this helps.
Cheers
--
Sébastien Gross
diff --git a/debian/README.Debian b/debian/README.Debian
new file mode 100644
index 000..f91910d
--- /dev/null
+++ b/debian/README.Debian
@@ -0,0 +1,26 @@
+Lilypond for Debian
+---
+
+This package is a Debian version
=guitare-pro.git
It is written in python.
Hope you'll enjoy.
Cheers
--
Sébastien Gross
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
in advance.
PS: Please note provided stanza is a whole file with default lilypond
configuration. Nothing but only this.
--
Sébastien Gross
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
On Thu, Dec 21, 2006 at 02:48:24PM -0800, [EMAIL PROTECTED] wrote:
The simple substitution example below should be pretty easy, but I'm in a
pickle, can someone show me how to replace the note name in the transpose
statement with the note specified on the function call (parameter called
On Fri, Dec 22, 2006 at 09:11:04AM -0800, [EMAIL PROTECTED] wrote:
Lilypond desperately needs some king of built-in text pre-process (that
installs with lilypond) to take care of these things, instead of everybody
having to constantly re-write the core lilypond code to do such simple
things.
Hi there,
I am working on a guitar chord library for lily [1] based on the
\fret-diagram command.
The generator is written in python.
The chord configuration file is quite simple:
a section header indicates the chord type. Followin lines a defining a
chord name. If a chord name ends with -b
On Thu, Dec 21, 2006 at 09:05:20AM -0800, [EMAIL PROTECTED] wrote:
Yes, as Mats said please check out the FretBoards context, I sponsored it!
It will allow you to transpose fret diagrams and enter fret diagrams using
standard lilypond notes, it will auto detect the strings for minimal hand
On Thu, Dec 21, 2006 at 12:45:52PM -0800, [EMAIL PROTECTED] wrote:
Here is an example of my non-programmers approach to forming a chord
library: (note this example can only be run in version 2.11.4 or better due
to a crash issue)
Ok I will install 2.11.4. I am still old fashion with 2.11.2
On Thu, Dec 21, 2006 at 03:05:25PM -0800, [EMAIL PROTECTED] wrote:
A define-music-function would be better than tags, then the whole library
would be inside a function where you just specify the chord name as a string
parameter then have a giant IF statement to generate the named chord, (root
On Thu, Dec 21, 2006 at 03:41:19PM -0800, [EMAIL PROTECTED] wrote:
Yes, I was thinking \varMyChordLibrary would not be needed in this case, all
the chords would simply come out of the function each embraced by an IF
statement to match the input parameter (like a giant CASE selection).
On Thu, Dec 21, 2006 at 12:45:52PM -0800, [EMAIL PROTECTED] wrote:
Here is an example of my non-programmers approach to forming a chord
library: (note this example can only be run in version 2.11.4 or better due
to a crash issue)
With this solution, fingering and notation will cause a problem.
On Wed, Dec 06, 2006 at 09:05:53PM +0100, [EMAIL PROTECTED] wrote:
[...]
The first thing to do is to observe what the input music looks like, and
what the output of your function should look like, using
\displayMusic. The purpose of your function will then be to transform
one into the other.
On Fri, Dec 08, 2006 at 05:46:03PM +0100, [EMAIL PROTECTED] wrote:
Maybe the code is ugly (my first scheme routine) and may be enhenced.
I thing about:
- use relative music whitout being messed u by octave shifts
- abbility to change tags
- put all in a scm file instead of
13 matches
Mail list logo