Re: Music font switching question
Christopher R. Maden wrote Add the new different things at the *end* of the list, not the beginning, so that code that used to work continues to work. Otherwise, it seems good to me... Well, it's not really new because it already happens first under the covers. It's just hard-coded to the emmentaler fonts. Regards, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Music-font-switching-question-tp164224p164227.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Music font switching question
Hi,
2014-07-09 0:16 GMT+02:00 tisimst tisi...@gmail.com:
Let me explain. When one wants to change the text fonts _globally_, there is
the very useful Scheme function make-pango-font-tree, which looks
something like this when used:
\paper {
#(define fonts
(make-pango-font-tree
FreeSerif ; the serif font
FreeSans ; the sans-serif font
Inconsolata ; the mono-space font
(/ staff-height pt 20)))
}
You simply put this block into you .ly file and now you get those fonts
instead of the defaults. /What if/, using a similar syntax we could change
the music and brace fonts like this (additions highlighted):
\paper {
#(define fonts
(make-pango-font-tree
/*gonville ; the music notation font
emmentaler ; the music brace font*/
FreeSerif ; the serif font
FreeSans ; the sans-serif font
Inconsolata ; the mono-space font
(/ staff-height pt 20)))
}
I think something like this would be perfectly acceptable.
cheers,
Janek
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Music font switching question
On 07/08/2014 05:16 PM, tisimst wrote: You simply put this block into you .ly file and now you get those fonts instead of the defaults. /What if/, using a similar syntax we could change the music and brace fonts like this (additions highlighted): Add the new different things at the *end* of the list, not the beginning, so that code that used to work continues to work. Otherwise, it seems good to me... ~crism -- Chris Maden, text nerd URL: http://crism.maden.org/ Surround hate and force it to surrender. GnuPG fingerprint: DB08 CF6C 2583 7F55 3BE9 A210 4A51 DBAC 5C5C 3D5E ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Music font switching question
tisimst wrote I just thought I'd ask the question... BTW, if it wasn't clear, this question is for everyone who receives it :) -Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Music-font-switching-question-tp164171p164172.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
user vs. user (was: User vs Developer: Round 2 (and half-time?) (was: Re: music font)
On Tue, Jan 24, 2012 at 01:50:13AM +0100, Janek Warchoł wrote: 2012/1/23 Xavier Scheuer x.sche...@gmail.com: why I never *demand* developers to fix an issue, even if it is one that is really annoying my ego in almost every score I typeset. One thing comes to my mind: you are talking about bugs that annoy many people, and they waste a lot of your own time. Have you considered organizing a collective bounty to fix that bug? We now have a webpage for this: http://lilypond.org/sponsoring.html My main goal was to attract attention to Emilio's nice project of music font with LilyPond. I attracted Graham's attention on me instead. Well, you asked for Graham's attention when you cc'd him. I think cc'ing him was a mistake, Me, and a bunch of other long-time developers. I'd have probably ignored the email if he hadn't done this. bitten by the red ants' queen! That's not a surprise. Graham's sensitivity is well-known, especially in this context. Yes, because it annoys me when people complain at the wrong target. Xavier mentioned having to submit a bug report 3 times because the emails kept on being lost/forgotten. That is indeed a serious problem -- but wait, that's a problem with users, not developers! The bug squad is composed (mainly) of users. It needs no technical skill, no git access, nothing like that. All it needs is people who can use email and a web browser and are willing to spend 20 minutes each week. Let's take a look at the current statistics, shall we? http://lilypond.org/~graham/maybe-missing-emails.html [from 2011 Dec 01 to 2012 Jan 24] Response category Number Percent of total Less than 24 hours 50 68.49% 24 to 48 hours 6 8.22% More than 48 hours 8 10.96% Never replied 9 12.33% Those numbers aren't great. Maybe Xavier could find 20 minutes each week to help improve them? hmm, looking at the never replied emails, I'd say that 3 were not actually bug reports. So things aren't quite as bad as those numbers suggest. Also, if we look at the later statistics, we see that of the 8 emails that were responded to later than 48 hours, 5 were done by Phil Holmes (who does bug squad on Sunday), 2 were done by Ralph Palmer, and 1 was done by Mark Klein. If we had somebody who was willing to seriously deal with emails that had gotten forgotten on Wednesdays and Thursdays (i.e. half a week away from Sunday), then we might be able to reliably respond to missing bug reports within 96 hours! Of course, a 96-hour reponse rate isn't precisely fantastic, but it's a start. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: user vs. user (was: User vs Developer: Round 2 (and half-time?)(was: Re: music font)
- Original Message - From: Graham Percival gra...@percival-music.ca To: Janek Warchoł janek.lilyp...@gmail.com Cc: lilypond-de...@gnu.org; lilypond-user lilypond-user@gnu.org Sent: Tuesday, January 24, 2012 11:57 AM Subject: user vs. user (was: User vs Developer: Round 2 (and half-time?)(was: Re: music font) Let's take a look at the current statistics, shall we? http://lilypond.org/~graham/maybe-missing-emails.html [from 2011 Dec 01 to 2012 Jan 24] Response category Number Percent of total Less than 24 hours 50 68.49% 24 to 48 hours6 8.22% More than 48 hours 8 10.96% Never replied 9 12.33% FWIW, the script isn't always correct - some replies seem to get missed in the mail download. I spent a few minutes looking at this earlier but couldn't work out why. Anyway, let's look at the missed ones: Issue 1377 should be pushed now? 10 Dec I replied I see James has now said it won't patch master, and so is back to needs work Beam subdivision bug in 2.15.22 Xavier replied same day, Carl followed up. hot potato bug handling I replied 18 Dec error: auto beaming in tuplets after dotted semiquaver Carl replied same day Engravers cannot be added at the StaffGroup level Janek replied same day PianoStaff, time and grace duplicates the time display Xavier replied same day Reorganize NR 1.3 Expressive marks Fair cop - it was addressed directly to James, though make doc-stage-1 barfs Julien replied same day. wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers Janek replied same day; Carl followed up. We may need to add Janek and Xavier to the list of associates. Of course, a 96-hour reponse rate isn't precisely fantastic, but it's a start. Well - TBH time isn't of the essence as a general rule. Whether a bug gets added to the tracker in one day or 3 rarely affects the overall development. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: user vs. user (was: User vs Developer: Round 2 (and half-time?)(was: Re: music font)
On Tue, Jan 24, 2012 at 12:27:56PM -, Phil Holmes wrote: Of course, a 96-hour reponse rate isn't precisely fantastic, but it's a start. Well - TBH time isn't of the essence as a general rule. Whether a bug gets added to the tracker in one day or 3 rarely affects the overall development. Our published materials says 24 hours: http://lilypond.org/bug-reports.html (step 4: wait for a response) If the norm is 72 hours, or 96, or 168 hours, we should update that accordingly. I don't mind what the number is, just as long as we give users an honest appraisal of how long they should wait. IMO taking a 95% cutoff is reasonable -- i.e. if 95% of emails are replied to within 80 hours, let's publish please allow up to 80 hours. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: user vs. user (was: User vs Developer: Round 2 (and half-time?)(was: Re: music font)
2012/1/24 Graham Percival gra...@percival-music.ca: Our published materials says 24 hours: [...] we should update that accordingly. http://codereview.appspot.com/5575047/ and stop worrying. :) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: user vs. user (was: User vs Developer: Round 2 (and half-time?) (was: Re: music font)
On Jan 24, 2012, at 5:57 AM, Graham Percival wrote: On Tue, Jan 24, 2012 at 01:50:13AM +0100, Janek Warchoł wrote: 2012/1/23 Xavier Scheuer x.sche...@gmail.com: why I never *demand* developers to fix an issue, even if it is one that is really annoying my ego in almost every score I typeset. One thing comes to my mind: you are talking about bugs that annoy many people, and they waste a lot of your own time. Have you considered organizing a collective bounty to fix that bug? We now have a webpage for this: http://lilypond.org/sponsoring.html Good idea! As a non-programmer, offering feedback and money are the best options I have for supporting Lilypond development. It's not clear how to offer a bounty on a specific issue through the Website, if that is even possible. Also, it's not clear there is any way to contribute to some sort of general fund to pay for server space, bandwidth, other operating expenses. Maybe those things are covered already, I don't know. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: user vs. user (was: User vs Developer: Round 2 (and half-time?) (was: Re: music font)
2012/1/24 Tim McNamara tim...@bitstream.net: On Jan 24, 2012, at 5:57 AM, Graham Percival wrote: On Tue, Jan 24, 2012 at 01:50:13AM +0100, Janek Warchoł wrote: 2012/1/23 Xavier Scheuer x.sche...@gmail.com: why I never *demand* developers to fix an issue, even if it is one that is really annoying my ego in almost every score I typeset. One thing comes to my mind: you are talking about bugs that annoy many people, and they waste a lot of your own time. Have you considered organizing a collective bounty to fix that bug? We now have a webpage for this: http://lilypond.org/sponsoring.html Good idea! As a non-programmer, offering feedback and money are the best options I have for supporting Lilypond development. It's not clear how to offer a bounty on a specific issue through the Website, if that is even possible. Also, it's not clear there is any way to contribute to some sort of general fund to pay for server space, bandwidth, other operating expenses. Maybe those things are covered already, I don't know. The bounties are handled in the tracker: http://code.google.com/p/lilypond/issues/list Paste in the search bar of the tracker: label:Bounty and you'll see them. I think that the bounties should be advertised on the sponsoring page. A brief description and a link to http://code.google.com/p/lilypond/issues/list?can=2q=label%3ABounty What do you think? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: user vs. user (was: User vs Developer: Round 2 (and half-time?) (was: Re: music font)
Sounds like a really useful idea. It would just need a bounty hunter, i.e., someone to clearly put the offered sum or sums in a readily apparent spot. Shane On Tue, Jan 24, 2012 at 11:07 AM, Federico Bruni fedel...@gmail.com wrote: 2012/1/24 Tim McNamara tim...@bitstream.net: On Jan 24, 2012, at 5:57 AM, Graham Percival wrote: On Tue, Jan 24, 2012 at 01:50:13AM +0100, Janek Warchoł wrote: 2012/1/23 Xavier Scheuer x.sche...@gmail.com: why I never *demand* developers to fix an issue, even if it is one that is really annoying my ego in almost every score I typeset. One thing comes to my mind: you are talking about bugs that annoy many people, and they waste a lot of your own time. Have you considered organizing a collective bounty to fix that bug? We now have a webpage for this: http://lilypond.org/sponsoring.html Good idea! As a non-programmer, offering feedback and money are the best options I have for supporting Lilypond development. It's not clear how to offer a bounty on a specific issue through the Website, if that is even possible. Also, it's not clear there is any way to contribute to some sort of general fund to pay for server space, bandwidth, other operating expenses. Maybe those things are covered already, I don't know. The bounties are handled in the tracker: http://code.google.com/p/lilypond/issues/list Paste in the search bar of the tracker: label:Bounty and you'll see them. I think that the bounties should be advertised on the sponsoring page. A brief description and a link to http://code.google.com/p/lilypond/issues/list?can=2q=label%3ABounty What do you think? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: User vs Developer: Round 2 (and half-time?) (was: Re: music font)
Dear Xavier, hereby i'd like to thank you for your time spent on helping LilyPond! It's true that user's work often is not appreciated enough. 2012/1/23 Xavier Scheuer x.sche...@gmail.com: Dear Graham, dear Developers, why I never *demand* developers to fix an issue, even if it is one that is really annoying my ego in almost every score I typeset. Sometimes when an issue has been unfixed for years and when I see people often being troubled by this issue I post a message stating it and thus moving this issue from the bottom of the pile. One thing comes to my mind: you are talking about bugs that annoy many people, and they waste a lot of your own time. Have you considered organizing a collective bounty to fix that bug? If i remember correctly, David is interested in working on Lily for money; there may be others. If you find 20 people annoyed by a bug and each one gives 10$, that's something! For example i'm interested in sponsoring bugfixes and new features, but there's no way i can afford to hire someone myself (200-500$? i'm a student!). But i'm definately interested in giving 10$ for each of the bugs that affect my Lily workflow. My main goal was to attract attention to Emilio's nice project of music font with LilyPond. I attracted Graham's attention on me instead. Well, you asked for Graham's attention when you cc'd him. I think cc'ing him was a mistake, because: - his function as administrator means that he won't do stuff like this (help someone with music font) - he clearly declared that he won't even try to talk other people into doing anything. Thus, no point in cc'ing Graham - expect for being bitten by the red ants' queen! That's not a surprise. Graham's sensitivity is well-known, especially in this context. I know that you didn't want to offend Graham (i wouldn't be offended if i were on Graham's place), but nevertheless Graham felt offended. The only thing we can do about it is to write e-mails in a way that not only seems polite to us, but also will be received as polite by Graham (or whoever the recipient is) - it's hard, i know. (actually i think things would be easier for Graham if he were less sensitive, but it's his choice and he can do whatever he likes - even if it's difficult for us) Recently i seriously offended David without intentions to do so at all - it was also a miscommunication :( cheers, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
User vs Developer: Round 2 (and half-time?) (was: Re: music font)
This is a split reply from the thread music font. http://lists.gnu.org/archive/html/lilypond-devel/2012-01/msg00752.html The title is a reference to the fist Users versus developers flame war of which I appear to be also at the origin. http://lists.gnu.org/archive/html/lilypond-user/2009-05/msg00551.html Dear Graham, dear Developers, On 22 January 2012 00:35, Graham Percival gra...@percival-music.ca wrote: And I'm a bit disappointed that you keep on whining about developers not doing what you want them to do. Argh, bitten by the red ants' queen! I guess I asked for it. I am not your slave. The fact that I have volunteered thousands of hours working on lilypond does not make me your slave. I am really sorry if I have hurt some of you, that was not my intention. I did not crawl out of my mother's womb knowing about lilypond internals, or even about programming at all. Any knowledge I have was from hard work: reading source code, reading public emails on the list archives, and learning about programming in general. I am a bit dissapointed that *you* have not done that. Please do not consider users as under men. We use LilyPond—probably more often than some developers—and hence are fully aware of its strengths, but also of its missing features, most annoying bugs, etc. Yes I am a simple user, not developing, programming and doing all this hard work. I admit I have currently higher priorities than learning Scheme, C++, etc. I *use* LilyPond, I try to help in a certain way (see below), I promote LilyPond around me and make scores for my university orchestra using LilyPond. I do not pretend to the title of Lead Developer, Release Meister or whatever. If we report issues, regressions and make new features requests, it is not simply because we wallow in keep on whining or because we take a sadistic pleasure in giving some more work to the developers. I use LilyPond quite often, I try to help users both on the French users mailing list and on the international one. I report bugs, regressions, make new feature request, both from my experience with LilyPond and making the link between Developers/Users from the international lists and French Users on lilypond-user-fr (by announcing in French new features, fixed issues, important ongoing discussions French user might be concerned about, but also in the reverse way, by transmitting upstream issues discovered by French users or popular requests in the French users community). Yesterday I posted several messages on different LilyPond mailing lists. I replied to some users' questions/issues, I reported a regression bug type-critical and… I started a fight with Graham! I received at the same time thanks you from users (in English and French) and infuriation from devel. I received also acknowledgements and congratulations about the quality of the score I made with LilyPond from musicians of my orchestra. You want something done? Do it yourself. That's what open source means -- you have the legal right to do it yourself. It does not mean that other people are obligated to do it for you. I understand LilyPond is an open source project, lead by volunteers. That's why I do not complaint when I have to send by three times a bug report because it was first lost/forgotten, why I never *demand* developers to fix an issue, even if it is one that is really annoying my ego in almost every score I typeset. Sometimes when an issue has been unfixed for years and when I see people often being troubled by this issue I post a message stating it and thus moving this issue from the bottom of the pile. And sometimes a kind developer see this issue and start fixing it! :-) You have la liberté, not royauté. Users usually never get any kind of acknowledgements or sign of gratitude from developers for volunteering [also] few hours trying to help other users, reporting back issues/requests, trying to make the link between high skilled developers and lambda user. I expressed my deep feelings. Yes I was disappointed, like when I see a reply like a RTFM smack in the face of a new user, or as a no as only-argument answer to a request/suggestion. My main goal was to attract attention to Emilio's nice project of music font with LilyPond. I attracted Graham's attention on me instead. I guess my message was as much discouraging (or even more) as being told each time you make a suggestion You want something done? Do it yourself. Learn programming!. I do not want to fight with some developers. I think we all have the same objective: to improve LilyPond. And each one has its own way to contribute, at different levels and different implications. I would be delighted to offer our finest Belgian beer to LilyPond developers which I could meet at FOSDEM 2012. I am afraid my student budget does not allow me to pay developers to work full time on LilyPond. Cheers, Whining Xavier -- Xavier Scheuer x.sche...@gmail.com
Re: User vs Developer: Round 2 (and half-time?) (was: Re: music font)
Sometimes it happens that a non-programer user reports some issue or makes some request and gets metaphorically punched by a developer. This occurs in all open-source projects. Some developers are much tetchier than the Lilypond developers (such as the GNU Emacs developers. Whoa. Their attitude is if you can't fix it yourself, you shouldn't be using the software.)! Lilypond developers work hard, usually in their spare time and almost always for free. The end result is that Lilypond produces the best looking scores (IMHO) of any music engraving software package available. Users work hard to try to figure out how to use what is still a very challenging application with a very steep learning curve. Like me, many users have no idea how to code anything in C, C++, Scheme, etc. In my case, as is probably true of many others, I have a full time (plus) occupation that leaves me no time to learn how to write Scheme, C++, etc. We can only offer feedback on how it works (and, of course, if it works well there is probably no feedback!). Sometimes developers and users tread on each others' toes. The task for all of us is to not take too much umbrage when that happens. Life goes on, Lilypond gets better. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: User vs Developer: Round 2 (and half-time?) (was: Re: music font)
On 01/22/2012 07:15 PM, Xavier Scheuer wrote a long message about tensions between users and developers. Well said, Xavier. We users certainly appreciate the many, many hours and the deep expertise put in by the developers to make such an excellent tool. And I think the developers (if I may, not being one) do appreciate the expertise that the users bring to interesting edge cases around music engraving and typesetting. The users don’t always say so, and so sometimes we all forget that the silent users are the happy users, merrily plugging along with a wonderful tool. That means that the users are most likely to speak when something is wrong, and it is easy to mistake that for complaining. LilyPond is a great tool with great developers and a great user base. Thank you, Xavier, for posting a very nicely balanced essay, a great rarity on the Internet. (-: And thank you, users and developers, for both contributing to such a fantastically wonderful tool. ~Chris -- Chris Maden, text nerd URL: http://crism.maden.org/ “Be wary of great leaders. Hope that there are many, many small leaders.” — Pete Seeger ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: music font
Hey, I have the same problem installing version 1.5.57 and 1.5.58 under
SuSE Linux 7.0 with Guile 1.4.1 installed. If I try the simplest file:
--
\score {
\notes \relative c' { c4 d e f | g1 }
}
--
then ly2dvi starts complaying about a wrong use of 'eval':
--
GNU LilyPond 1.5.58
Now processing: `test.ly'
Analisi...
Interpretazione della musica...[3]
Pre-elaborazione...
Calcolo delle posizioni della colonne...
paper output to `test.tex'...Backtrace:
0* [tex-output-expression # #output: test.tex 3]
1* [display ...
2* [eval # #]
ERROR: In procedure eval in expression
(my-eval-in-module expr this-module):
ERROR: Wrong number of arguments to #primitive-procedure eval
--
This error happens also if I call `lilypond' directly, and also if I
use the `-f ps' or `-f pdftex' option (instead of `tex-output-
expression', it complains about `ps-output-expression' and 'pdftex-
output-expression' respectively). The problem seems to be in file
scm/tex.scm, lines 283-285:
--
(define-public (tex-output-expression expr port)
(display (my-eval-in-module expr this-module) port )
)
--
In fact, if I try to run `guile' and I execute this command (perfectly
legal: I took it from the Scheme Revised^5 Report):
--
(eval '(* 7 3) (current-module))
--
then `guile' will give the following error message:
--
standard input:1:1: In procedure eval in expression
(eval (quote #) (current-module)):
standard input:1:1: Wrong number of arguments to
#primitive-procedure eval
ABORT: (wrong-number-of-args)
--
My guile accepts only two parameters for `eval':
--
(eval '(* 7 3))
--
prints 21.
So, I think the problem is in guile, not in lilypond. On my SuSE Linux
7.0 guile 1.3.x was installed. In order to use lilypond, I removed it
completely using the Yast installation program, then I installed guile
1.4.1 by unpacking the tarball under my home directory and creating the
binaries via a `./configure ; make ; make install' command. Is this
sufficient to install guile? The shipped INSTALL file is not very clear
about doing upgrades.
Also, should I (re)install a new version of SLIB? I found this
library in `/usr/lib/scheme/slib', but I do not know if it was
installed by SuSE a long time ago or by guile 1.4.1 today.
Thanks
Maurizio
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: music font
I think I got the solution! The NEWS file shipped with Guile 1.5.6 says: ** Backward incompatible change: eval EXP ENVIRONMENT-SPECIFIER `eval' is now R5RS, that is it takes two arguments. The second argument is an environment specifier, i.e. either (scheme-report-environment 5) (null-environment 5) (interaction-environment) or any module. So, my guile 1.4.1 supports only the one-argument-syntax for `eval'. On the computer I am using here there is Guile 1.5.6, and there is no problem evaluating the same expression (eval '(* 7 3) (current-module)) which gives problems with guile 1.4.x So, I think the scm/tex.scm file was written for Guile 1.5.x, not for Guile 1.4.x (although the INSTALL.txt file shipped with Lilypond says 1.4 is good). I am at work now, but this evening I will try to install the 1.5.6 version on my home computer, and I will see what happen. I suggest you to do the same. Bye Maurizio ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: music-font
On Tue, 2002-05-28 at 11:08, Mats Bengtsson wrote: OK, what probably happens is that your newly compiled lilypond program reads the initialization files from a previous installation in /usr/share/lilypond/... Did you run 'make install' and where did it install the files? Do you have the same problem as Maurizio that not even ly2dvi works (having run 'make install')? i ran ./configure --prefix=/usr; the files were then installed into the directory /usr/share/lilypond -- which is where my previous version of lilypond is/was. ly2dvi broke off with the same error. However, this is a bug in the make files, since it should be possible to build a new version without removing an existing installation. The strange thing is that the Makefiles indeed set temporary environment variables that should solve problem. We discussed it on the mailing list some week ago and Han-Wen didn't manage to repeat the bug. Could you please try the following (assuming that you still have files from some older Lilypond version in /usr/share/lilypond/): i first moved the 1.5 version to /usr/share/lilypond-1.5.58, renamed the binaries and then installed version 1.4.13 to /usr/share/lilypond. this worked without any problems, and i could generate the sheet of music that i needed - and the documentation using the make -C Documentation/user out/lilypond.dvi command. - First of all, make sure that the environment variables $LILYPONDPREFIX and $LILYINCLUDE are undefined. If they were defined, we have hopefully found the problem. these variables are at the moment undefined. - Set the environment variable LILYPONDPREFIX to the full path of the lilypond-1.5.58/ directory and try to rerun the make command. [root@box lilypond-1.5.58]$ LILYPONDPREFIX=/usr/share/lilypond-1.5.58 [root@box lilypond-1.5.58]$ LILYINCLUDE=$LILYPONDPREFIX/ly - Set the environment variable LILYINCLUDE to $LILYPONDPREFIX/ly and try to rerun the make command. same error as before: GNU LilyPond 1.5.58 Now processing: `out/lily-333851501.ly' Parsing... Interpreting music...[1] Preprocessing elements... Calculating column positions... [2] paper output to `out/lily-333851501.tex'...Backtrace: 0* [tex-output-expression # #output: out/lily-333851501.tex 3] 1* [display ... 2* [eval # #] ERROR: In procedure eval in expression (my-eval-in-module expr this-module): ERROR: Wrong number of arguments to #primitive-procedure eval make: *** [out/lily-333851501.tex] Error 2 make: Leaving directory `/big-one/public/programs/LINUX/music/lilypond/lilypond-1.5.58/Documentation/user' i will try what maurizio suggested and update my guile libraries. greetings, simon. -- Confucius say, man who live in glass house shower in basement. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: music-font
hello, is there any way to see all of the symbols that are in the font used for musical and all other symbols? For the development version, they are listed in an appendix of the manual, goto lilypond.org/development click on Documentation: other ... and look at the PS or PDF version of the manual. Unfortunately the list is truncated in the on-line HTML version since it spans more than one page. This documentation of the font symbols is not yet included in the stable version (I will fix it), but for the moment, you can find a list at http://www.s3.kth.se/~matsb/lilypond/. and how can i generate the documentation for all of the scheme-properties? An Info version is generated as soon as you run make in Documentation/user/out/lilypond-internals.info*. To produce the HTML version, run 'make web' and to produce a .dvi version run 'make -C Documentation/user out/lilypond.dvi'. /Mats ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
