Colin Cotter <[EMAIL PROTECTED]> writes:
> I have reposted my question with the source attached. I hope that you can
> spot what I am doing wrong!
Yes, it was my first suggestion: add a \paper block. You should also
put the two pieces in separate files; lilypond-book will include only
the firs
[EMAIL PROTECTED] writes:
> I don't believe that the mess was the result of
> users trying to cut down on typing, I just don't.
No, but having both a functional programming form of extending lily
and a macro oriented form will lead to confusion, and there is enough
of that already in Lily as we
I'm a little confused - I do have a \paper command in my ly file.
Can you explain what the format is?
Colin
> Colin Cotter <[EMAIL PROTECTED]> writes:
>
> > I have reposted my question with the source attached. I hope that you can
> > spot what I am doing wrong!
>
> Yes, it was my first suggest
On Mon, 09 Sep 2002 08:49:45 Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > I don't believe that the mess was the result of
> > users trying to cut down on typing, I just don't.
>
> No, but having both a functional programming form of extending lily
> and a macro oriented form will lead
I think you and I have a different idea of `macro'.
The problem with TeX, m4, YODL and metafont is that they are syntax
oriented and not function oriented. I'm too busy to formalise exactly
what I mean, but maybe this example explains what I mean
\def\foo{20}
\def\bar{20}
The python bug that caused some problems when using Lilypond with
python 2.2 has been fixed.
--- Begin Message ---
Bugs item #604803, was opened at 2002-09-05 01:20
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=604803&group_id=5470
Category: Regul
On Mon, 09 Sep 2002 13:33:41 Han-Wen Nienhuys wrote:
>
> I think you and I have a different idea of `macro'.
You must admit that it's a fairly inclusive word.
I think I should have said `identifier'.
All I mean is:
novobracket = {\property Staff.VoltaBracket = \turnOff}
If I have more than tw
Hello,
I know it's pretty "bleeding-edge", but I have recently upgraded my
system to gcc-3.2 and encounter problems when trying to compile lilypond
1.6.2 (as expected after the reading of INSTALL.txt)...
So, I've followed the instructions given for gcc-3.1... :
I attache the log file...
Has
Actually, there seem to be two workarounds:
1) use the lilypond-profile that comes with building from 1.6.2 source
on Linux (this creates the TEXMF variable among other things)
2) use -P as you said, then convert separately to PDF.
So, perhaps the cygwin installation needs to have those
startup
I would all documentation for the lilypond. I am the second director of
the Conservatorio di Musica "G. Martucci" di Salerno, and I would
editing the opera omnia of Martucci with lilypond, and the scores of the
'700 and '800 of the composers of Neapols school's.
I'm sorry for the low level of t
"Alex Langley" <[EMAIL PROTECTED]> writes:
> Just want to report that using -P instead of -p solved both
> the problem of no lyrics in Lilypond on Cygwin (1.6.0), and
> no note heads in Lilypond (1.6.2) on Redhat.
Ok. In that case you probably have an installation problem on Red Hat
Linux. PD
"Alex Langley" <[EMAIL PROTECTED]> writes:
> Actually, there seem to be two workarounds:
>
> 1) use the lilypond-profile that comes with building from 1.6.2 source
> on Linux (this creates the TEXMF variable among other things)
> 2) use -P as you said, then convert separately to PDF.
>
> So, perh
francesco de mattia <[EMAIL PROTECTED]> writes:
> I would all documentation for the lilypond.
You just want to read the documentation, as a user?
To learn using LilyPond, the tutorial:
http://lilypond.org/stable/Documentation/user/out-www/lilypond/Tutorial.html
The user manual:
http:/
Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote:
> "Alex Langley" <[EMAIL PROTECTED]> writes:
> > Can -p (going all the way to PDF) be fixed by creating the
> > proper fonts?
>
> They should be available, ie, there should be nothing 'to fix' on
> Linux. Did you build LilyPond yourself? Did you
Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote:
> "Alex Langley" <[EMAIL PROTECTED]> writes:
>
> > Actually, there seem to be two workarounds:
> >
> > 1) use the lilypond-profile that comes with building from 1.6.2 source
> > on Linux (this creates the TEXMF variable among other things)
> > 2)
I guess I still don't understanding (judging from the mktexpk
commands I see from ly2dvi --verbose) why -P tells it to use
a 600 dpi device ljfour, but -p tells it to use an 8000 dpi
device:
kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000
--dpi 8000
cmbx10
mktexpk: Mismatched
"Alex Langley" <[EMAIL PROTECTED]> wrote:
> Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote:
> > They should be available, ie, there should be nothing 'to fix' on
> > Linux. Did you build LilyPond yourself? Did you build and install
> > the pfa fonts? Maybe we need better instructions for
[EMAIL PROTECTED] writes:
> We just want to be able to pass a value to things already
> identifiable. Of course lily would choke on a stem length
> two inches long. So what? You are assuming that we are
> total gluttons for punishment. 'Taint so.
You have the perspective of a well-behaved u
18 matches
Mail list logo
