From Hair-cutter

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

The employee

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

Registration confirmation

2004-02-28 Thread drl
Cya <> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

Ahtung!

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

virus info/fix

2004-02-28 Thread Edward Sanford Sutton, III
The following link has virus details to what I suspect has been flooding lilypond email lists lately. I am only assuming since I have no up to date antivirus system to test them against right now. Confirmations appreciated. Reading the following page can help educate windows users about the v

Re: procedures with setters: patches

2004-02-28 Thread Reuben Thomas
> I'm ambivalent. The danger is that the number of functions to create > and manipulate data structures explodes, and becomes harder to > learn. We have to find a balance between having a small "interface" > and an interface that is ultra-ergonomic to use. I think at the moment that Lilypond is a

Re: \arpeggioup and \arpeggiodown ?

2004-02-28 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > On Sat, 28 Feb 2004, Han-Wen Nienhuys wrote: > > > [EMAIL PROTECTED] writes: > > > > > > Why not to have commands \arpeggioup and \arpeggiodown? > > > They would be handy. > > > > Go ahead. > > Please consider the capitalization standards, though. > > I made functions

Re: \arpeggioup and \arpeggiodown ?

2004-02-28 Thread Heikki Johannes Junes
On Sat, 28 Feb 2004, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > > > Why not to have commands \arpeggioup and \arpeggiodown? > > They would be handy. > > Go ahead. > Please consider the capitalization standards, though. I made functions \arpeggioUp, \arpeggioDown, \arpeggioBoth and \a

Freedom for everyone

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

The employee

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

Price-list

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

New Price-list

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

The employee

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

Weekly activity report

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

The account

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

Monthly incomings summary

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

Weekly activity report

2004-02-28 Thread jeremie
Everything inside the attach <> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

From me

2004-02-28 Thread jeremie
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

patch for make-music

2004-02-28 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > I haven't updated convert-ly (not sure about it). Maybe something like > that should be added (?) > > def conv (str): > str = re.sub ('make-music-by-name', 'make-music',str) > return str > > conversions.append (((2,1,), conv, """More Scheme function

Jessica

2004-02-28 Thread drl
<> ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel

Re: compilation error

2004-02-28 Thread Werner LEMBERG
> We could also generate dummy .txt files to satisfy makeinfo 4.6. Please do so. The less latest-version-or-newer packages are needed, the better. lilypond already needs too much packages to work. Werner ___ Lilypond-devel mailing list [EMAIL P

Re: patch for make-music

2004-02-28 Thread Nicolas Sceaux
> Here is a patch for a new make-music definition. I forgot a (use-modules (ice-9 optargs)) on top of music-functions.scm. There is no error, though, as it is present in new-markups.scm. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.

patch for make-music

2004-02-28 Thread Nicolas Sceaux
Here is a patch for a new make-music definition. I was not sure about what to do with the former make-music-by-name definition, so it is still in define-music-types.scm (after make-music), with a deprecation warning. Maybe this should be removed. One more time, I messed with indentation, adding r

Re: procedures with setters: patches

2004-02-28 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Sat, 28 Feb 2004 11:53:15 +0100, Han-Wen a dit : > > > I'm ambivalent. The danger is that the number of functions to create > > and manipulate data structures explodes, and becomes harder to > > learn. We have to find a balance between having a small "interface" >

Re: procedures with setters: patches

2004-02-28 Thread Nicolas Sceaux
Sat, 28 Feb 2004 11:53:15 +0100, Han-Wen a dit : > I'm ambivalent. The danger is that the number of functions to create > and manipulate data structures explodes, and becomes harder to > learn. We have to find a balance between having a small "interface" > and an interface that is ultra-ergon

Re: procedures with setters: patches

2004-02-28 Thread Nicolas Sceaux
Sat, 28 Feb 2004 11:57:00 +0100, Jan a dit : > Doing style fixes separately requires quite a bit of dicipline and > means extra work (resolving conflicts). It makes little sense to > 'just remember' the files that need style fixes, and fix them in > another CVS tree: then it feels more like

Re: procedures with setters: patches

2004-02-28 Thread Jan Nieuwenhuizen
Nicolas Sceaux writes: > > I like the stylistic patches. /me too, gives warm fuzzy feelings and saves me a bit of work. > > Jan always complains of my style, and > > he's probably right, but if you clean up after me, it frees me to do > > interesting stuff :-). Still, but I would prefer to

Re: procedures with setters: patches

2004-02-28 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > When a pattern is encountered a few times, it is common pratice to > write a macro that will expand to that pattern. For instance: > > and there are several other occurences of that pattern. There could be > something that will allow to write, for instance: > > > w

Re: lilypond.tely problem?

2004-02-28 Thread Jan Nieuwenhuizen
Werner LEMBERG writes: > Currently, I see lines like > > * GNU LilyPond: (./lilypond/lilypond).The GNU music typesetter. >^^^ > Is this really correct? Yes. The info docs are now installed in a separate directory: INFODIR/lilypond (like emacs-21/), toge

Re: compilation error

2004-02-28 Thread Jan Nieuwenhuizen
Werner LEMBERG writes: > The current compilation problem triggers a nasty bug in makeinfo 4.6: > /home/sx0005/lilypond//Documentation/user/out/introduction.texi:95: > @image file `lily-212977279.txt' (for text) unreadable: > No such file or directory. > ... > Too many errors! Gave u

Re: scheme interface for all LilyPond syntactic constructs

2004-02-28 Thread Nicolas Sceaux
Sat, 28 Feb 2004 00:43:00 +0100, Han-Wen a dit : > [EMAIL PROTECTED] writes: >> The goal of course is to help users (hmm, it cannot be only me, there >> must be few others!) creating scheme functions. Collateral damage: >> internal function definitions may also be simpler. >> >> Do you thi

Re: procedures with setters: patches

2004-02-28 Thread Nicolas Sceaux
Sat, 28 Feb 2004 00:38:31 +0100, Han-Wen a dit : > I like the stylistic patches. Jan always complains of my style, and > he's probably right, but if you clean up after me, it frees me to do > interesting stuff :-). Still, but I would prefer to handle them > separately, i.e. try not to mix st