Re: Google displays 2.9 doc

Jan Nieuwenhuizen writes: > I'm not sure the solution to remove al older v2.9 etc. from google is > a smart thing to do. I think it is much better than the alternatives. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org http:

Re: Quit [now definitely O/T]

Carl Sorensen writes: > David, > > I appreciate your persistence in this. I think that you are having part of > the difficulty in this conversation because it's on -user, not on -devel. > > The modifications to anything except input files (which use lilypond code > and embedded scheme) really in

Re: Google displays 2.9 doc

Op donderdag 12-11-2009 om 01:32 uur [tijdzone +], schreef Graham Percival: > On Wed, Nov 11, 2009 at 07:19:02PM +0100, Jan Nieuwenhuizen wrote: > > Op woensdag 11-11-2009 om 17:25 uur [tijdzone +], schreef Graham > > Percival: > > > On Wed, Nov 11, 2009 at 01:12:26PM +0100, Bertalan Fodor

Re: lower-case html names

Op donderdag 12-11-2009 om 01:29 uur [tijdzone +], schreef Graham Percival: Hi Graham, > Could we hold off on the @ref{} and @rgeneral{} changes for a few > days while I take a look at this? Sure. I just think broken links are /bad/ so I always ruthlessly followed-up to 404 reports. Curren

Re: Google displays 2.9 doc

Graham Percival writes: > On Wed, Nov 11, 2009 at 07:19:02PM +0100, Jan Nieuwenhuizen wrote: >> Op woensdag 11-11-2009 om 17:25 uur [tijdzone +], schreef Graham >> Percival: >> > On Wed, Nov 11, 2009 at 01:12:26PM +0100, Bertalan Fodor (LilyPondTool) >> > wrote: >> > > can something be done

Re: problem installing build requirements [Mac OS X 10.4.11]

Hi Graham, I'll bet you a double-double and 20 timbits[1] that this is because of "sudo make", or running sudo at some point when downloading the source? Once you do "sudo make clean; sudo make distclean", all the out/ and out-www/ directories should be gone, and you shouldn't have this problem

Re: [PATCH] Source_file: remove mbrtowc() in favor of utf8_char_len()

On 2009-11-10, Patrick McCarty wrote: > I have uploaded a patch series to Rietveld for review: > > http://codereview.appspot.com/154046/show > > This addresses the following report: > > http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg1.html > > and keeps compatibility with the

Re: problem installing build requirements [Mac OS X 10.4.11]

On Wed, Nov 11, 2009 at 09:35:35PM -0500, Kieren MacMillan wrote: > Hi Graham, > >> - why modify configure.make ?! that shouldn't be necessary. > > I tried make, and had problems — specifically, > > mkdir -p ./out > echo 2.13.8 > out/VERSION > /bin/sh: line 1: out/VERSION: Permission denied > make

Re: problem installing build requirements [Mac OS X 10.4.11]

Hi Graham, - why modify configure.make ?! that shouldn't be necessary. I tried make, and had problems — specifically, mkdir -p ./out echo 2.13.8 > out/VERSION /bin/sh: line 1: out/VERSION: Permission denied make: *** [out/VERSION] Error 1 On

Re: problem installing build requirements [Mac OS X 10.4.11]

On Wed, Nov 11, 2009 at 09:11:28PM -0500, Kieren MacMillan wrote: > Hi John (et al), > >> can't you grab and install last TeXlive release? (2008, 2009 beta, or >> 2009 in case it's out) > > I [apparently] installed texlive. > > Now, after doing the ./autogen stuff and modifying configure.make, I d

Re: problem installing build requirements [Mac OS X 10.4.11]

Hi John (et al), can't you grab and install last TeXlive release? (2008, 2009 beta, or 2009 in case it's out) I [apparently] installed texlive. Now, after doing the ./autogen stuff and modifying configure.make, I do sudo make and get chmod 755 out/lilypond-invoke-editor /Users/kmac/Docu

Re: Fixing issue 800 (extender ending early if other voices present)

On Wed, 2009-11-11 at 14:41 -0500, Chris Snyder wrote: > >> 1) Change melisma_busy() to return true if in the middle of a note > >> 2) Alternatively, add the check in > >> Extender_engraver::stop_translation_timestep instead > > > > I'm confused: isn't the current check in > > Extender_engrave

Re: Google displays 2.9 doc

On Wed, Nov 11, 2009 at 07:19:02PM +0100, Jan Nieuwenhuizen wrote: > Op woensdag 11-11-2009 om 17:25 uur [tijdzone +], schreef Graham > Percival: > > On Wed, Nov 11, 2009 at 01:12:26PM +0100, Bertalan Fodor (LilyPondTool) > > wrote: > > > can something be done to make Google display latest doc

lower-case html names

Jan, I like the changes to the @uref{} links, but we should be able to make all the html filenames lower-case by changing 2 or 3 lines in the texi2html-init file. I'm still not certain whether makeinfo / info is happy with lower-case node names, so I think the perl lc() function is better than ma

Re: Tracker 836: Add facility to change output file-name for a \book block

A few whitespace errors (tab following spaces) and one indenting mistake. Then I think it's good to go. http://codereview.appspot.com/150044/diff/11/1015 File ly/music-functions-init.ly (right): http://codereview.appspot.com/150044/diff/11/1015#newcode611 ly/music-functions-init.ly:611: (fil

Re: serious doubts about waf

On Wed, 11 Nov 2009, Graham Percival wrote: > What's the advantage of automake over the current system? (I'm not > even certain what the current system is called!) If anyone goes into this, could they PLEASE, PLEASE, document it slightly better? [I'm almost certainly I'm doing insane things when I

Re: Quit [now definitely O/T]

David, I appreciate your persistence in this. I think that you are having part of the difficulty in this conversation because it's on -user, not on -devel. The modifications to anything except input files (which use lilypond code and embedded scheme) really involve knowledge that's primarily dis

Re: problem installing build requirements [Mac OS X 10.4.11]

>can't you grab and install last TeXlive release? (2008, 2009 > beta, or 2009 in case it's out) 2009's just been released. Wholeheartedly agreed on advising against teTeX. It has been a great distribution, but there's no point in sticking to it today, years after support has been di

Re: problem installing build requirements [Mac OS X 10.4.11]

On Thu, Nov 12, 2009 at 01:15:35AM +0100, John Mandereau wrote: > Hi Kieren, > Le mercredi 11 novembre 2009 à 19:05 -0500, Kieren MacMillan a écrit : > > I'm trying to get a local build system in place (in order to edit the > > docs), and can't seem to get past some install errors — specifically

Re: problem installing build requirements [Mac OS X 10.4.11]

On Wed, Nov 11, 2009 at 07:05:18PM -0500, Kieren MacMillan wrote: > I'm trying to get a local build system in place (in order to edit the > docs), and can't seem to get past some install errors — specifically > >sudo port install tetex I can't see anything obviously wrong in the output... I

Re: problem installing build requirements [Mac OS X 10.4.11]

Hi Kieren, Le mercredi 11 novembre 2009 à 19:05 -0500, Kieren MacMillan a écrit : > I'm trying to get a local build system in place (in order to edit the > docs), and can't seem to get past some install errors — specifically > > sudo port install tetex I don't have a Mac and I have never us

problem installing build requirements [Mac OS X 10.4.11]

Hello all, I'm trying to get a local build system in place (in order to edit the docs), and can't seem to get past some install errors — specifically sudo port install tetex leads [eventually] to ---> Extracting teTeX ---> Configuring teTeX ---> Building teTeX Error: Target org.macpor

Re: [PATCH] Re: serious doubts about waf

Le mercredi 11 novembre 2009 à 23:36 +, Graham Percival a écrit : > Hmm. I don't completely follow, but does this explain why waf > always succeeds on the second attempt? If not, it might be > something weirder... but then again, if you're following it up on > the waf-user list, then it's no

Re: serious doubts about waf

On Wed, Nov 11, 2009 at 02:38:12PM -0800, Patrick McCarty wrote: > I don't have much experience *using* automake, but from what I've > read: > > - A Makefile.am is easier to maintain than an equivalent handcoded > makefile. > - The generated makefiles will be very portable (not reliant on

Re: [PATCH] Re: serious doubts about waf

On Thu, Nov 12, 2009 at 12:21:47AM +0100, John Mandereau wrote: > After hours of debugging and code inspection, I think you did nothing > weird, it's a bug in Waf code: Node.py:Node.find_dir(), which looks up > directories, call bld.rescan() which among others removes nodes of > directories that ha

Re: serious doubts about waf

Le mercredi 11 novembre 2009 à 23:07 +, Graham Percival a écrit : > Given that most of our users are on windows, I defined > "portability" as "it will run on operating system X with Y extra > software installed", where X should be large and Y should be > small. Then SCons and Waf are reasonabl

[PATCH] Re: serious doubts about waf

Le mardi 10 novembre 2009 à 23:34 +, Graham Percival a écrit : > The basic problem is that waf doesn't like to have directories in the > build tree that aren't present in the source tree. After asking for > help, the main author pointed out a not-really-documented function > that allowed me to

Re: serious doubts about waf

On Wed, Nov 11, 2009 at 02:38:12PM -0800, Patrick McCarty wrote: > On 2009-11-11, Graham Percival wrote: > > What's the advantage of automake over the current system? (I'm > > not even certain what the current system is called!) > > I don't have much experience *using* automake, but from what I'v

Re: Tracker 836: Add facility to change output file-name for a \book block

Hi all, Is it O K to push this patch now? If so, can either Carl or Neil push this on origin/master. Cheers and thanks for all the help on this one, Ian http://codereview.appspot.com/150044 ___ lilypond-devel mailing list lilypond-devel@gnu.org http

Re: serious doubts about waf

On 2009-11-11, Graham Percival wrote: > On Tue, Nov 10, 2009 at 06:36:37PM -0800, Patrick McCarty wrote: > > On Tue, Nov 10, 2009 at 3:58 PM, Graham Percival > > wrote: > > > On Tue, Nov 10, 2009 at 11:34:35PM +, Graham Percival wrote: > > >> I'm just about ready to give up on waf. > > > > > >

Re: BOM mark from Windows notepad

On Wed, Nov 11, 2009 at 1:53 PM, Bertalan Fodor (LilyPondTool) wrote: > It is a regression. BOM was supported for sure. Have you experienced this problem, too? -Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailm

Re: BOM mark from Windows notepad

On Wed, Nov 11, 2009 at 11:57 AM, Francisco Vila wrote: > 2009/11/11 Patrick McCarty : >> On 2009-11-11, Francisco Vila wrote: >>> Hello. When LilyPond for Linux encounters a BOM from files made with >>> the Windows notepad, it issues an error. >> >> Has this always been the case, or is this a new

Re: BOM mark from Windows notepad

It is a regression. BOM was supported for sure. Patrick McCarty wrote: On 2009-11-11, Francisco Vila wrote: Hello. When LilyPond for Linux encounters a BOM from files made with the Windows notepad, it issues an error. Has this always been the case, or is this a new issue with 2.13.7?

Re: 8 measures per line

GODILLON wrote: How can I reduce the print size in order to print 8 measures per line instead of 4 . Try #(set-global-staff-size XX) where XX is your staff size; default = 20 see: http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Setting-the-staff-size#Setting-the-staff-size Hope tha

8 measures per line

How can I reduce the print size in order to print 8 measures per line instead of 4 . Thanck you . Odile Godillon ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: BOM mark from Windows notepad

2009/11/11 Patrick McCarty : > On 2009-11-11, Francisco Vila wrote: >> Hello. When LilyPond for Linux encounters a BOM from files made with >> the Windows notepad, it issues an error. > > Has this always been the case, or is this a new issue with 2.13.7? I vaguely remember it happening from 2005.

Re: BOM mark from Windows notepad

On 2009-11-11, Francisco Vila wrote: > Hello. When LilyPond for Linux encounters a BOM from files made with > the Windows notepad, it issues an error. Has this always been the case, or is this a new issue with 2.13.7? > I think it should continue making the PDF anyway, because the file has > an o

Re: Fixing issue 800 (extender ending early if other voices present)

>> 1) Change melisma_busy() to return true if in the middle of a note >> 2) Alternatively, add the check in >> Extender_engraver::stop_translation_timestep instead > > I'm confused: isn't the current check in > Extender_engraver::stop_translation_timestep? For solution #2, I meant that we can add

Re: Fixing issue 800 (extender ending early if other voices present)

On Wed, 2009-11-11 at 10:33 -0500, Chris Snyder wrote: > I've done some work towards fixing issue 800, and at least now > understand what's happening: > > The patch that introduced the bug added a check in > Extender_engraver::stop_translation_timestep() to check if the current > voice was in t

BOM mark from Windows notepad

Hello. When LilyPond for Linux encounters a BOM from files made with the Windows notepad, it issues an error. I think it should continue making the PDF anyway, because the file has an otherwise correct syntax; what do you think? -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.

Re: Google displays 2.9 doc

Op woensdag 11-11-2009 om 17:25 uur [tijdzone +], schreef Graham Percival: > On Wed, Nov 11, 2009 at 01:12:26PM +0100, Bertalan Fodor (LilyPondTool) wrote: > > can something be done to make Google display latest doc and not 2.9? > > It's a known bug in the issue tracker. Patches appreciated.

Re: Google displays 2.9 doc

On Wed, Nov 11, 2009 at 01:12:26PM +0100, Bertalan Fodor (LilyPondTool) wrote: > can something be done to make Google display latest doc and not 2.9? It's a known bug in the issue tracker. Patches appreciated. Cheers, - Graham ___ lilypond-devel mail

Fixing issue 800 (extender ending early if other voices present)

I've done some work towards fixing issue 800, and at least now understand what's happening: The patch that introduced the bug added a check in Extender_engraver::stop_translation_timestep() to check if the current voice was in the middle of a melisma (calling melisma_busy(voice) ) and, if not

Re: Fixes issue 786, "Extenders in lyrics stop prematurely if a single underscore is found."

I've uploaded a patch that reverts the "fix" for issue 800, as it reintroduced the neverending-extender bug. I also added some comments in the code as requested. http://codereview.appspot.com/150067 ___ lilypond-devel mailing list lilypond-devel@gnu.o

Re: chord names in piano staff

Guten tag, Henrik: In addition to the [correct] answer already given, I thought you should know that r1 | r1 | r1 | r1 | \break should be R1 | R1 | R1 | R1 (i.e., uppercase R). Hope this helps! Kieren. ___ lilypond-devel ma

Re: Google displays 2.9 doc

Op woensdag 11-11-2009 om 13:12 uur [tijdzone +0100], schreef Bertalan Fodor (LilyPondTool): > can something be done to make Google display latest doc and not 2.9? Use the search box on lilypond.org, it adds +v2.12 +site:lilypond.org At least, it should do that. Greetings, Jan -- who rememb

Google displays 2.9 doc

Hi, can something be done to make Google display latest doc and not 2.9? Thanks, Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: serious doubts about waf

On Tue, Nov 10, 2009 at 06:36:37PM -0800, Patrick McCarty wrote: > On Tue, Nov 10, 2009 at 3:58 PM, Graham Percival > wrote: > > On Tue, Nov 10, 2009 at 11:34:35PM +, Graham Percival wrote: > >> I'm just about ready to give up on waf. > > > > As Jan put it, "a new build system should be a brea

Re: Build failure on OS X 10.6: libguile missing

Op dinsdag 10-11-2009 om 23:38 uur [tijdzone +0100], schreef Harmath Dénes: > checking GUILE rational bugfix... ok >From this message, it seems that the right Guile installation is found. However, as these earlier messages show, > checking for scm_boot_guile in -lguile... no > checking for scm_

chord names in piano staff

hi, i wonder where to find the solution for my problem. i guess a lot of others do too. i want the chord names above the piano staff: guitarChords = \chordmode { c1 | c | c | c | f | f | c | c | g | f | c | g } upper = \relative c' { \clef treble \key