Renaming \setTextCresc, \setHairpinCresc, etc.

2008-04-29 Thread Patrick McCarty
Hi List, I would like to propose that we rename the textual crescendo and decrescendo commands to names that are more intuitive and are more internally consistent. The current implementation uses the "hairpin" commands to revert the "text" commands, but I do not think this solution is very intuit

Re: CVS ERROR: Unable to find file "lily.scm"

2008-04-29 Thread Andrew Wagner
Thanks a lot Mats, My global make install was somehow failing partially and silently. Running a make install inside the lilypond/scm directory cleared up that problem. Sorry I was unable to find any of the helpful replies; for some reason I could only find the initial posts despite a good

Re: CVS ERROR: Unable to find file "lily.scm"

2008-04-29 Thread Mats Bengtsson
I guess you mean "GIT" when you say "CVS". This error message has appeared occasionally on the mailing lists for situations where either the installation has failed or where the automatic setting of some path variables has failed. The file lily.scm together with a large number of other .scm files

CVS ERROR: Unable to find file "lily.scm"

2008-04-29 Thread Andrew Wagner
Hello- I'm experiencing the same problem Tapio did: compiled /ChangeLog/1.4659 from CVS seems to compile OK, but when trying to run 'lilypond' it spits out the following: "GNU LilyPond 2.7.35 ERROR: In procedure primitive-load-path: ERROR: Unable to find file "lily.scm" in load path" what sh

Build hanging on an error.

2008-04-29 Thread Andrew Wagner
Hello- I'm trying to build on os x 10.4.11, and ran into the same problem this fellow did on BSD: http://www.mail-archive.com/[EMAIL PROTECTED]/msg10088.html Nikita <[EMAIL PROTECTED]> writes: > I try to build lilypond on freebsd 6.2 amd64 machine. After installing all > required packages

Re: Action of \unset

2008-04-29 Thread Trevor Daniels
Thanks Mats, You wrote As far as I can see, it removes any settings of the property in the specified context (i.e. in the current context by default). After I posted the query I hunted in the sources a bit and came to the same conclusion. context.cc contains: void Context::unset_property

Introduction

2008-04-29 Thread Andrew Wagner
Hello- Not sure if this list is small enough to warrant it, but I thought I'd introduce myself. I'm Drew Wagner, and I'm trying to build lilypond with the patches for alternative notations (i.e. twinline) on a mac. Another one of my hobbies is building a digital piano with a Janko Layou

Re: Action of \unset

2008-04-29 Thread Valentin Villenave
2008/4/29 Mats Bengtsson <[EMAIL PROTECTED]>: > That's not related to the current issue. What I refered to > at that time was that you can not only unset context property > settings using \unset but also clear all layout object properties > of some layout object, since layout object properties

Re: Action of \unset

2008-04-29 Thread Mats Bengtsson
Valentin Villenave wrote: 2008/4/29 Mats Bengtsson <[EMAIL PROTECTED]>: For a long time, I had the impression that \set and \unset did push and pop on a stack (if you know about these computer science concepts), but apparently I was wrong. Yes, I remember that several months ago http

Re: Action of \unset

2008-04-29 Thread Valentin Villenave
2008/4/29 Mats Bengtsson <[EMAIL PROTECTED]>: > For a long time, I had the impression that \set and \unset did > push and pop on a stack (if you know about these computer > science concepts), but apparently I was wrong. Yes, I remember that several months ago http://lists.gnu.org/archive/html/

Re: Action of \unset

2008-04-29 Thread Mats Bengtsson
As far as I can see, it removes any settings of the property in the specified context (i.e. in the current context by default). The reason that this often means that the setting is reverted to the default value is either 1. that the default is that the property is unset and that LilyPond makes

Re: no more ragged-right in LSR

2008-04-29 Thread Neil Puttock
2008/4/29 Graham Percival <[EMAIL PROTECTED]>: > Valentin, Neil: > > Thanks to the wonderful new ragged-right settings, we'll probably > be removing all ragged-right from LSR. Don't bother doing this > quite yet, but certainly don't deliberately add any more. OK, but I have had to do the oppos

Re: News aggregation on lilypond.org?

2008-04-29 Thread Valentin Villenave
2008/4/29 Graham Percival <[EMAIL PROTECTED]>: > Mao, I hope that this internet meme is as popular in Europe as it > is in North America. If it isn't, google for the last five words > in the above quote from me. Oh, crap; AFAIK, it isn't. At least among young French pianists/contemporary com

Re: News aggregation on lilypond.org?

2008-04-29 Thread Graham Percival
On Tue, 29 Apr 2008 11:50:58 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > 2008/4/29 Graham Percival <[EMAIL PROTECTED]>: > > > I just wanna tell you how I'm feeling. Valentin, I'm never gonna > > give you up. > > Note to myself: remember to collect Graham's mails and turn them into

Re: News aggregation on lilypond.org?

2008-04-29 Thread Valentin Villenave
2008/4/29 Graham Percival <[EMAIL PROTECTED]>: > I just wanna tell you how I'm feeling. Valentin, I'm never gonna > give you up. Note to myself: remember to collect Graham's mails and turn them into an opera someday :-) Cheers, Valentin ___ lilypo

Re: News aggregation on lilypond.org?

2008-04-29 Thread Valentin Villenave
2008/4/29 Jan Nieuwenhuizen <[EMAIL PROTECTED]>: > The idea of an rss feed is nice, but I don't like typing xml feeds > by hand. How about junking old-news.html and just have > news.ihtml and generate both a news-top3.ihtml and the xml from that? John: ... *or* we could just keep news.ihtml a

Re: News aggregation on lilypond.org?

2008-04-29 Thread Jan Nieuwenhuizen
Valentin Villenave writes: > For instance, our news.xml file could look like: > Lots of <:> cruft. The idea of an rss feed is nice, but I don't like typing xml feeds by hand. How about junking old-news.html and just have news.ihtml and generate both a news-top3.ihtml and the xml from that? J

Re: News aggregation on lilypond.org?

2008-04-29 Thread Graham Percival
On Tue, 29 Apr 2008 11:16:03 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > 2008/4/29 Graham Percival <[EMAIL PROTECTED]>: > > > I have no clue about anything else in your email; I just can't > > resist the opportunity to make a sarcastic comment about you. > > Then you should be grat

Re: News aggregation on lilypond.org?

2008-04-29 Thread Valentin Villenave
2008/4/29 Graham Percival <[EMAIL PROTECTED]>: > I have no clue about anything else in your email; I just can't > resist the opportunity to make a sarcastic comment about you. Then you should be grateful to me for having made your day brighter :-) Actually, the old-news file does help me to ma

Re: News aggregation on lilypond.org?

2008-04-29 Thread Graham Percival
On Tue, 29 Apr 2008 10:58:19 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > This way, > - we wouldn't loose the past piece of news (they'd be archived > instead) Try clicking on the "older news" link. Or, if that's too hard to find, look for "actualités passées..." on the French verison

News aggregation on lilypond.org?

2008-04-29 Thread Valentin Villenave
Greetings John, correct me if I'm wrong: currently the news.ihtml on the web branch only contains the three last "news" items, does it? And every time one wants to add some piece of news, one has to delete the last item? My question is the following: Could we (namely you) tweak the format-page.py

Re: no more ragged-right in LSR

2008-04-29 Thread Graham Percival
On Tue, 29 Apr 2008 10:18:12 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > 2008/4/29 Graham Percival <[EMAIL PROTECTED]>: > > Valentin, Neil: > > > > Thanks to the wonderful new ragged-right settings, we'll probably > > be removing all ragged-right from LSR. Don't bother doing this >

Re: no more ragged-right in LSR

2008-04-29 Thread Valentin Villenave
2008/4/29 Graham Percival <[EMAIL PROTECTED]>: > Valentin, Neil: > > Thanks to the wonderful new ragged-right settings, we'll probably > be removing all ragged-right from LSR. Don't bother doing this > quite yet, but certainly don't deliberately add any more. I'd add: *don't* do this yet, unti