this happens outside netrel with 2.3.6, too. Arno
On Sun, 20 Jun 2004 12:44:55 +0200, Bertalan Fodor <[EMAIL PROTECTED]>
wrote:
I tried to make the package. I get a Signal 11 when running the command:
cd /netrel/build/lilypond-2.3.4//Documentation/user/out &&
/netrel/build/lilyp
ond-2.3.4/lily/out/
I tried to make the package. I get a Signal 11 when running the command:
cd /netrel/build/lilypond-2.3.4//Documentation/user/out &&
/netrel/build/lilyp
ond-2.3.4/lily/out/lilypond-bin --verbose
/netrel/src/lilypond-2.3.4/ly/generate
-documentation
lilypond_datadir: `/usr/share/lilypond'
local_lil
Tried to build 2.3.1 once, but not succeed. I will try it again (perhaps
tomorrow).
Bert
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Bert,
How about it. Could you prepare a cygwin build for lilypond 2.3.4?
Thanks,
Carl Sorensen
From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
Sent: Fri 6/18/2004 4:23 PM
To: Carl D. Sorensen
Cc: [EMAIL PROTECTED]
Subject: RE: Fret Diagram markup
On Mon, 14 Jun 2004 18:01:43 -0600 "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> So I suppose we could do as you propose, and have the note in Tablature
> be replaced by the fret in FretDiagrams. That seems reasonable. Under
> this scenario, things become position independent, because we have
[EMAIL PROTECTED] writes:
>
>
> > -Original Message-
> > From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> >
>
> > Still some minor points:
> >
> > * font-name/font-magnification is not the preferred interface
> > for finding fonts. We try to use
> > font-family/font-series/font-shap
> -Original Message-
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
>
> Still some minor points:
>
> * font-name/font-magnification is not the preferred interface
> for finding fonts. We try to use
> font-family/font-series/font-shape/font-size. font-name is
> for those who wish
> -Original Message-
> From: Heikki Johannes Junes [mailto:[EMAIL PROTECTED]
> I agree that the that it is good the maintain the information
> about the strings. So, that part is resolved ;)
>
> As usual, I should be more precise on what was confusing me
> (before starting to inventin
> I suppose I'm also a bit hesitant to move away from explicit string
> definition because it seems to me to be more likely to be confusing.
> For example, if we finger the c major scale you've identified above, we
> might get something like:
>
> ";3-3;0 2-2 3-3;0 2-2;0 1-1;;"
>
> Which to me is
[EMAIL PROTECTED] writes:
> * scm/fret-diagrams.scm: add fret-diagram-verbose markup;
> modified fret-parse-string so it prepares for calls to
> fret-diagram-verbose
> Changed display constants to props so they are available for
> \override.
OK! Maybe you can adapt the fret-diag
> -Original Message-
> From: Heikki Johannes Junes [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 31, 2004 12:52 AM
> To: Carl D. Sorensen
> Cc: [EMAIL PROTECTED]
> Subject: RE: Fret Diagram markup
>
Thanks for your comments!
> Some remarks of the possib
IMHO, the \fret-diagram-verbose syntax is the direction to go. But the syntax,
which uses \fret-diagram-verbose should be optimized. Here is one, even less
verbose syntax than what is presented previously:
Some remarks of the possible syntax:
- number of ';' marks could give the number of strings,
[EMAIL PROTECTED] writes:
>
> As a result of this work, I have almost eliminated arbitrary constants
> from the code. There is still one set. I could eliminate them if I
> could make a centered stencil from text -- i.e. one that has extents
> equal to (-a . a) for both X and Y. There used to be
[EMAIL PROTECTED] writes:
> \override.
>
> I created a diff file, which is attached.
You've just sent a 700k diff of ChangeLog. I suggest to make the diff
using
diff -u the-file-downloaded-from-cvs.scm my-file.scm
(there's boudn to be a way to do this with CVS, but I'm no CVS expert).
[EMAIL PROTECTED] writes:
> > to a Scheme list.
> >
> > * The diagram items include settings for linethickness, height,
> >width, etc.
> >
> >It would be better style to put these settings into properties, so
> >you could do
> >
> >\translator { \StaffContext
> > \
> -Original Message-
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 25, 2004 2:20 PM
>
> This was also an opportunity for me to take a closer look at
> your code. I still have some remarks:
>
> * We want to separate formatting machinery from syntax.
> Your
> -Original Message-
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 25, 2004 2:20 PM
>
> This was also an opportunity for me to take a closer look at
> your code. I still have some remarks:
>
> * We want to separate formatting machinery from syntax.
> Your fre
[EMAIL PROTECTED] writes:
> > #'((cross 6) (cross 5) (open 4) (barre 1 2))
> >
>
> I'm delighted to make this change. Thanks for the input on how you'd
> like it to work. Do you think it would be best to make a
> \fret-diagram-verbose in addition to the current \fret-diagram, or
> should I
[EMAIL PROTECTED] writes:
> > -Original Message-
> > From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, May 18, 2004 2:10 PM
> >
> > I would like to start integrating your file into scm/fret-diagrams.scm
> > - however, could I ask you to use hyphenated chord names?
> > W
[EMAIL PROTECTED] writes:
> [EMAIL PROTECTED] writes:
> > > -Original Message-
> > > From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, May 18, 2004 2:10 PM
> > >
> > > I would like to start integrating your file into scm/fret-diagrams.scm
> > > - however, could I ask y
> -Original Message-
> From: Heikki Johannes Junes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 19, 2004 3:37 AM
>
> Next thing is to merge it to lilypond, make missing glyphs,
> polish the output, and consider what is the most suitable
> syntax (before people start to make masses
> I have not been able to test with 2.3, because it's not yet packaged
> for
> Cygwin (IIRC, because of some bug in Cygwin). Heikki, could you put
> Han-Wen's code in and test it with 2.3?
Yes, works smoothly. The names of the variables also are now much better.
Next thing is to merge it to li
> -Original Message-
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 18, 2004 2:10 PM
>
> I would like to start integrating your file into scm/fret-diagrams.scm
> - however, could I ask you to use hyphenated chord names?
> When fret-diagrams.scm enters the Lilypon
[EMAIL PROTECTED] writes:
>
>
> > -Original Message-
> > From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> > [...]
> > I would like to start integrating your file into scm/fret-diagrams.scm
> > - however, could I ask you to use hyphenated chord names?
> > When fret-diagrams.scm enters
On Tue, 18 May 2004 15:43:07 -0600 "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
>
>
> > -Original Message-
> > From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> > [...]
> > I would like to start integrating your file into
> scm/fret-diagrams.scm
> > - however, could I ask you to use h
> -Original Message-
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> [...]
> I would like to start integrating your file into scm/fret-diagrams.scm
> - however, could I ask you to use hyphenated chord names?
> When fret-diagrams.scm enters the Lilypond distribution, we
> have to t
[EMAIL PROTECTED] writes:
> > directory. Then one can use the script you
> > wrote by adding just one line in the beginning of the file:
> >
> > \include "fret-diagram-init.ly"
> >
> > By adding this line into "ly/declarations-init.ly", one may
> > use the scripts even without any extra
> -Original Message-
> From: Heikki Johannes Junes [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 17, 2004 4:35 PM
> To: Carl D. Sorensen
> Cc: [EMAIL PROTECTED]
> Subject: RE: Fret Diagram markup
>
>
>
> > > /home/hjunes/fret-diagrams.ly:222:3
> > /home/hjunes/fret-diagrams.ly:222:36: Unbound variable: fontify-text
> >
> > Where does the fontify-text function originate from? I should
> > have missed something.
>
> In my distribution, fontify-text is found in scm/stencil.scm
I guess that it is not against CVS. Some fontify command
> -Original Message-
> From: Nicolas Sceaux [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 17, 2004 1:24 PM
> To: Carl D. Sorensen
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Fret Diagram markup
>
>
> The following remarks are purely
> -Original Message-
> From: Nicolas Sceaux [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 17, 2004 1:24 PM
> To: Carl D. Sorensen
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Fret Diagram markup
>
>
> Mon, 17 May 2004 12:33:31 -0600, Carl a dit :
> -Original Message-
> From: Heikki Johannes Junes [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 17, 2004 1:46 PM
> To: Carl D. Sorensen
> Cc: [EMAIL PROTECTED]
> Subject: Re: Fret Diagram markup
>
>
>
> > It's a fairly lengthy chunk of code to
Mon, 17 May 2004 12:33:31 -0600, Carl a dit :
> Attached is a copy of the latest fret diagram markup function. [...]
The following remarks are purely stylistic. You may want to:
- use hyphens in variable and function names, eg subtract-base-fret
instead of subtractbasefret;
- use less ge
> It's a fairly lengthy chunk of code to include at the front of a
> lilypond file. I think it might be reasonable to add as a scheme file
> to the lilypond distribution, and create a new kind of standard markup,
> fret-diagram-markup, rather than using a user-defined markup. I don't
> have
34 matches
Mail list logo
