> "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
Han-Wen> I would be very grateful if someone could take care of
Han-Wen> announcing lily on the following remaining channels,
Han-Wen> [EMAIL PROTECTED]
I did abcusers.
--
Laura (mailto:[EMAIL PROTECTED] , http:/
Again, Debian, Sid, 2.4.0.
rm -f ./out/lexer.dep; DEPENDENCIES_OUTPUT="./out/lexer.dep ./out/lexer.o" g++ -c
-DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out -I../flower/include
-I../flower/./out -I../flower/include -O2 -finline-functions -g -pipe
-I/usr/include/python2.3 -O
Hi Y'all,
I've just posted the LilyPond 2.4 release announcement to the
following channels,
News:
rec.music.compose
comp.os.linux.announce
comp.music.research
comp.text.tex
Mail:
[EMAIL PROTECTED]
I'm building 2.4.0 on a pretty brand new Debian Sid system, so I had to
install some things. One thing that neither INSTALL.txt nor
./configure caught that I didn't have was guile-devel. The error from
make was:
g++ -shared -o out/midi.so out/midi.lo -lguile -lguile-ltdl -lqthreads -lpthr
[EMAIL PROTECTED] writes:
> Could somebody take a look at the following three sections?
>
> 4.7: talks about lilypond-latex and using the "old" wrapper that uses
> latex, unlike current LilyPond. Is that info correct, or should it be
> commented out until 3.0 arrives? (I've changed "3.0" to "2
On 24-Oct-04, at 6:20 PM, Erik Sandberg wrote:
That's fine with me, as long as it is well documented. IMHO the BUGS
section
of the quoting docu should warn its readers that grace note quoting is
broken
& even can cause lily to hang. (Graham?)
Fixed in CVS.
Cheers,
- Graham
__
Between 2.3.18 or so (maybe as late as .20 or .22) and .25,
lilypond-book no longer indents the first line in long (two-page)
scores in latex documents.
If that's a design decision, groovy; I'll change section 9.5
accordingly. If it's a bug (and marked "wontfixyet"), then I should
add a BUGS
Could somebody take a look at the following three sections?
4.7: talks about lilypond-latex and using the "old" wrapper that uses
latex, unlike current LilyPond. Is that info correct, or should it be
commented out until 3.0 arrives? (I've changed "3.0" to "2.4" in the
text, but otherwise left
On Sat, 2004-10-30 at 03:45, Han-Wen Nienhuys wrote:
> Further steps are:
>
> Integrate this with (parts of) the program reference manual.
>
>
> > Internal documentation of the scheme accessors is found at
> > @internalsref{ly:stencil-add}.
>
> Yup, but that documentation should be moved
Hi,
On Sat, 30 Oct 2004, Han-Wen Nienhuys wrote:
> Perhaps this should also be told to the [EMAIL PROTECTED]
I did, didn't I? Maybe I was a bit confuse because of the hours of
hacking...
Ciao,
Dscho
___
lilypond-devel mailing list
[EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
> Hi,
>
> after many hours of doing and probing and trying, python stopped throwing
> invalid pages on cygwin with Windows 98. What it probably boils down to is
> a newer gcc. I attached the cygintl-2.dll, which you have to copy into
> your /bin/, if you don't want to com
Hi,
after many hours of doing and probing and trying, python stopped throwing
invalid pages on cygwin with Windows 98. What it probably boils down to is
a newer gcc. I attached the cygintl-2.dll, which you have to copy into
your /bin/, if you don't want to compile it yourself (which takes quite a
Hi,
On Fri, 29 Oct 2004, Carl Sorensen wrote:
> I've tried to organize this information and add to it a bit of my
> understanding. I believe that it may be useful to new developers
> trying to get up to speed in LilyPond.
Well done!
> OTOH, if its only value is to help me clarify my thoughts,
> > I've revised lilypond-book to improve the option handling (still
> > not perfect but...). Please test.
>
> Can you tell us what changed? It's hard to make out from the
> changelog.
This, for example, should work now:
\begin[ indent = 2.0\mm , noindent, fragment, nofragment ]{lilypond}
not
Alle 01:28, sabato 30 ottobre 2004, Han-Wen Nienhuys ha scritto:
> sorry, was in a grumpy mood. I've committed a fix, no promises that
> it works, though.
It's easy at 00:32 am ;-)
Thanks, i'll check in next release
___
lilypond-devel mailing list
[E
[EMAIL PROTECTED] writes:
> I've been spending a little bit of time again trying to understand
> enough about LilyPond that I can create a Fret_diagram context.
>
> I've been back and reviewed Han-Wen's earlier answer about program
> functionality
> (http://lists.gnu.org/archive/html/lilypond-dev
16 matches
Mail list logo
