On Mon Jun 28, 2004 at 12:05:47AM +0200, Jan Nieuwenhuizen wrote:
> > Anyway, source specials is not working well in my box (cvs emacs,
> > server.el untouched). Sometimes it works, sometimes I click in an
> > instrument in the xdvi and the code shown is of another
> > instrument. Sometimes I get e
Pedro Kroger writes:
> Is the patch for server.el still necessary with cvs emacs?
That depends on your version.
> I get 3 out of 4 hunks failed when applying the patch. The code of
> server.el is not equal of the patch, but it seems to be very
> similar.
Then your version already has the patch.
Nicolas Sceaux writes:
>> I'm trying to compile the GNOME output but I got this error message:
Please do not use GUILE CVS yet. It has been broken the past few
weeks. I thought the troubles were over, but apparently they are not.
The point #3 [removed] in the guile-gnome.sh script used to be,
Pedro Kroger <[EMAIL PROTECTED]> writes:
> Hi,
>
> I'm trying to compile the GNOME output but I got this error message:
>
> make[3]: Entrando no diret#rio
> `/home/kroger/lilypond/lilypond/buildscripts/test/guile-gnome/=build/glib/gnome/gw'
> guile -c \
> "(debug-set! stack 20) \
>(use
Hi,
Is the patch for server.el still necessary with cvs emacs? I get 3 out
of 4 hunks failed when applying the patch. The code of server.el is
not equal of the patch, but it seems to be very similar.
Anyway, source specials is not working well in my box (cvs emacs,
server.el untouched). Sometimes
Hi,
I'm trying to compile the GNOME output but I got this error message:
make[3]: Entrando no diret#rio
`/home/kroger/lilypond/lilypond/buildscripts/test/guile-gnome/=build/glib/gnome/gw'
guile -c \
"(debug-set! stack 20) \
(use-modules (g-wrap)) \
(use-modules (gnome gw gobject-spe
Erik Sandberg writes:
> I'm using Jan's here-lily script to set paths etc, has anything important
> changed in the directory structure of the source tree?
You'll probably have to rm -rf ./share; the symlink tree.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typeset
Hi,
with the latest dev versions, I get this error message when I invoke lilypond.
I'm using Jan's here-lily script to set paths etc, has anything important
changed in the directory structure of the source tree?
lilytest:~/lily/lilypond/bugs$ lilypond
Traceback (most recent call last):
File "