Re: Force a bar number to appear

2005-07-28 Thread Graham Percival
On 21-Jul-05, at 8:24 AM, Phillip Kirlin wrote: My apologies if this is a simple question to answer, but I recently upgraded to 2.6.1, and some of my 2.4.x files have their bar numbers disappearing, even when run through convert-ly. This looks like a bug. scm/output-lib.scm contains this li

Re: missing term in Icking glossary

2005-07-28 Thread Graham Percival
On 14-Jul-05, at 4:15 AM, M. den Teuling wrote: Christian Mondrup suggested to me to report a missing term in the gossary : tenuto. I had the term myself forgotten even in Dutch, and so I really missed it. Its opposite staccato is present. If there is a term (in Dutch or English or whatsoever

Re: ghostscript dependancy in the autopackage

2005-07-28 Thread Erik Sandberg
On Thursday 28 July 2005 11.38, Jan Nieuwenhuizen wrote: > Erik Sandberg writes: > > I have the same problem (I reported it earlier), with the full package. I > > get the following message when installing: > > > > # Checking for Ghostscript ... failed > > # FAILED: > > # Package 'Ghostscript' was f

Re: Barline bug with Staff Timing_engraver?

2005-07-28 Thread Erik Sandberg
On Wednesday 27 July 2005 17.13, Trevor Baca wrote: > Looking at the final barline in this 2.7.0 snippet ... See the section on bar lines in the manual. You need to use \set Staff.whichBar = "|." BTW, you might want to use ChoirStaff iso. StaffGroup, this way there will never be a barline drawn

Re: Bad spacing with short notes before the bar line

2005-07-28 Thread Erik Sandberg
On Wednesday 27 July 2005 11.07, John Mandereau wrote: > Hi, > > Although LilyPond is generally very good at spacing, I've found > that 1/32 notes at the end of a measure are often displayed much too > close from the bar, especially if they are down-stemed. > > I've had a look at some traditionally

Re: ghostscript dependancy in the autopackage

2005-07-28 Thread Paul Scott
Jan Nieuwenhuizen wrote: Erik Sandberg writes: I have the same problem (I reported it earlier), with the full package. I get the following message when installing: # Checking for Ghostscript ... failed # FAILED: # Package 'Ghostscript' was found but was of the wrong version and the correc

RE: What is the proper way of printing the current date? Also bug report

2005-07-28 Thread Sven Axelsson
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED] > Sent: den 28 juli 2005 14:39 > To: Sven Axelsson > Cc: lilypond-user@gnu.org; 'bug-lilypond' > Subject: Re: What is the proper way of printing the current > date? Also bug report > > Sven Axelsson wrote: > > I have been using > > > > #(use-mo

Re: What is the proper way of printing the current date? Also bug report

2005-07-28 Thread Han-Wen Nienhuys
Sven Axelsson wrote: It is even quainter. Running lilypond from the command prompt does generate correct output and no Wrong type error. Doubleclicking the *.ly file generates no output and a clean log, since warnings and errors are printed on stderr and doesn't end up in that log file. Using my

Re: lily/parser.yy rev 1.476

2005-07-28 Thread Han-Wen Nienhuys
Sven Axelsson wrote: But not \score { \header { title = "foo" } { c'4 } } then? indeed. Feels a bit illogical to put the header after the music, but if this is how it's going to be, then ok. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___

Re: What is the proper way of printing the current date? Also bug report

2005-07-28 Thread Han-Wen Nienhuys
Sven Axelsson wrote: I have been using #(use-modules (srfi srfi-19)) today = #(date->string (current-date) "~B ~d, ~Y") to get the current date so I can include that in the tagline of my music. This does cause the message WARNING: #f: imported module (srfi srfi-19) overrides core binding `curr

Minor barcheck and \partial interaction bug

2005-07-28 Thread Trevor Baca
Hello, I didn't think I'd ever need a partial measure in the middle of an ongoing line of music, but, as it happens, the 7th Bach chorale melody changes from 4/4 to 3/4 after measure 4 and begins the 3/4 section with a 1 beat \partial in the middle of the line. LilyPond handles this fine, with th

PianoStaff dashed bars bug?

2005-07-28 Thread Trevor Baca
Hi, At the risk of double-posting to the list I'm sending this observation and potential bug to the list again. [The original message hit the *archive* (user archive, actually, because I realized only afterwards that I should have posted to the bug list) with a Tuesday timestamp (Tue, 26 Jul 2005

What is the proper way of printing the current date? Also bug report

2005-07-28 Thread Sven Axelsson
I have been using #(use-modules (srfi srfi-19)) today = #(date->string (current-date) "~B ~d, ~Y") to get the current date so I can include that in the tagline of my music. This does cause the message WARNING: #f: imported module (srfi srfi-19) overrides core binding `current-time' in the log, b

Re: ghostscript dependancy in the autopackage

2005-07-28 Thread Jan Nieuwenhuizen
Erik Sandberg writes: > I have the same problem (I reported it earlier), with the full package. I get > the following message when installing: > > # Checking for Ghostscript ... failed > # FAILED: > # Package 'Ghostscript' was found but was of the wrong version and the correct > version could not

RE: lily/parser.yy rev 1.476

2005-07-28 Thread Sven Axelsson
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED] > Sent: den 28 juli 2005 10:41 > To: Graham Percival > Cc: Sven Axelsson; bug-lilypond > Subject: Re: lily/parser.yy rev 1.476 > > Graham Percival wrote: > > > > On 27-Jul-05, at 4:10 AM, Sven Axelsson wrote: > > > >> * lily/parser.yy (score_bo

Re: lily/parser.yy rev 1.476

2005-07-28 Thread Han-Wen Nienhuys
Graham Percival wrote: On 27-Jul-05, at 4:10 AM, Sven Axelsson wrote: * lily/parser.yy (score_body): \score can only begin with Music. No, it can begin with \header too, and this change (i think) is causing errors when I try version 2.7.3. I believe that this is a new feature. Han-Wen, co

Re: ghostscript dependancy in the autopackage

2005-07-28 Thread Erik Sandberg
On Thursday 28 July 2005 08.37, Jan Nieuwenhuizen wrote: > Guy Banay writes: > > The Lilypond autopackage (version 2.6.1) will not install on systems > > without Ghostscript >= 8.15 despite GS being an optional runtime > > dependancy and lilypond can run without it. > > What does `will not install'