Re: multistaff use of rhythm mark snippet

Thanks, that is exactly what I was looking for. I simply added the following block from the snippet, which moved the mark to the correct staff. The caveat is it created a space so the music in all staves begins after the mark in that measure. Qian \layout { \context { \Score \re

Re: Widening one measure so that dynamics don't overlap

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 17. August 2009 22:06:46 schrieb Kieren MacMillan: > Hi Reinhold, > > > Grr, it doesn't work so well, though: This will not work in the > > first measure > > of a line or immediately after a time signature change! > > Something like this wou

Re: Automatically checking regtests (was: Re: Minor releases?)

On Mon, Aug 17, 2009 at 7:58 PM, Han-Wen Nienhuys wrote: >> Yes.  All it takes is bookmarking the site, checking it whenever >> there's a release, and reporting any broken examples.  However, >> nobody is willing to commit to do this.  15 minutes whenever >> there's a release, which happens at mos

Re: Automatically checking regtests (was: Re: Minor releases?)

On Mon, Aug 17, 2009 at 6:35 PM, Graham Percival wrote: >> Graham was referring to the fact that nobody seem to bother about looking at >> those automatically-created regression results before or after a release. > > Yes.  All it takes is bookmarking the site, checking it whenever > there's a rele

Re: Automatically checking regtests (was: Re: Minor releases?)

2009/8/17 Graham Percival : > I think that's normal for a .0 release. I assumed the same, but 2.12.0 has results against 2.11.66 (OK, that didn't officially exist since I made a mistake doing a version bump before 2.12) and 2.11.65. > Oh, yet another problem with the lack of release steps.  It'l

Re: Automatically checking regtests (was: Re: Minor releases?)

On Mon, Aug 17, 2009 at 10:55:37PM +0100, Neil Puttock wrote: > 2009/8/17 Graham Percival : > > > Yes.  All it takes is bookmarking the site, checking it whenever > > there's a release, and reporting any broken examples.  However, > > nobody is willing to commit to do this.  15 minutes whenever >

Re: Automatically checking regtests (was: Re: Minor releases?)

2009/8/17 Graham Percival : > Yes.  All it takes is bookmarking the site, checking it whenever > there's a release, and reporting any broken examples.  However, > nobody is willing to commit to do this.  15 minutes whenever > there's a release, which happens at most once every two weeks. It proba

Re: Need some help with \include "makam.ly"

On Mon, Aug 17, 2009 at 10:41:07PM +0100, Trevor Daniels wrote: > > Graham Percival wrote Monday, August 17, 2009 11:30 AM > >>> I know the snippet documentation is meant to be brief but why not >>> add a >>> note-name table >> Trevor: the actual table goes in pitches.itely (obviously), while >>

Re: Automatically checking regtests (was: Re: Minor releases?)

Graham Percival wrote Monday, August 17, 2009 10:35 PM On Mon, Aug 17, 2009 at 05:17:08PM +0200, Reinhold Kainhofer wrote: Am Montag, 17. August 2009 16:08:36 schrieb Michael Käppler: > > > (nobody checks the regression tests for each release, for > > example > > -- and that's trivially don

Re: Need some help with \include "makam.ly"

Graham Percival wrote Monday, August 17, 2009 11:30 AM On Mon, Aug 17, 2009 at 12:07:44PM +0100, Joseph Wakeling wrote: Neil Puttock wrote: > Can you suggest any improvements for this snippet's > documentation? It > does already mention where the pitch names are defined > (ly/makam.ly).

Re: Automatically checking regtests (was: Re: Minor releases?)

On Mon, Aug 17, 2009 at 05:17:08PM +0200, Reinhold Kainhofer wrote: > Am Montag, 17. August 2009 16:08:36 schrieb Michael Käppler: > > > > > (nobody checks the regression tests for each release, for example > > > -- and that's trivially done with a web browser!) > > > > That reminds me of an idea I

Re: multistaff use of rhythm mark snippet

On 17.08.2009, at 22:38, Qian Li wrote: I'm using one of the rhythm marks from the lsr for a multistaff piece. I only want the rhythm mark to show up on one of the staves in transition from a polymetric part back to same meter with the other staves, but the marking always prints over the t

Re: Widening one measure so that dynamics don't overlap

> Grr, it doesn't work so well, though: This will not work in the > first measure of a line or immediately after a time signature > change! What about attaching a markup text consisting of \hspace only, together with \textLengthOn? Werner ___ li

Re: using makam.ly

2009/8/17 Jay Hamilton : > 1] I have no idea where it says "see section etc" as it does not say that > in the snippet rep. It's in the 2.12.2 Snippets List under `Pitches' and `World music': http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/World-music#World-music The direct refere

Re: Wideining one measure so that dynamics don't overlap

On Mon, Aug 17, 2009 at 01:56:04PM -0400, Kieren MacMillan wrote: > Hi Reinhold, > >> How can I make that one measure wider, while all other measures are >> spaced normally? > > Here are a couple of ideas: > 1. \override the NoteColumn #'X-extent > 2. \override the Score.NonMusicalPaperCo

Re: Minor releases?

On Monday 17 August 2009, John Mandereau wrote: > Le dimanche 16 août 2009 à 14:34 -0700, Graham Percival a écrit : > > On Sun, Aug 16, 2009 at 11:48:53AM -0400, David Raleigh Arnold wrote: > > > I don't see any straightforward way of seeing a changelog or > > > anything which tells the difference

Re: using makam.ly

I'm out of this loop in terms of what you all are talking about but 1] I have no idea where it says "see section etc" as it does not say that in the snippet rep. 2] I still don't know what or where initialization file ly/makam.ly for details of pitch names and alterations. is or e

Re: Widening one measure so that dynamics don't overlap

Hi Reinhold, Grr, it doesn't work so well, though: This will not work in the first measure of a line or immediately after a time signature change! Something like this would work anywhere, yes? \version "2.13.3" \paper { line-width = 9\cm } makeSpace = { \once \override Score.BarLine #'

Re: Widening one measure so that dynamics don't overlap

Am Montag, 17. August 2009 21:18:56 schrieb Reinhold Kainhofer: > Am Montag, 17. August 2009 19:56:04 schrieb Kieren MacMillan: > > 4. add a hidden voice with a MultiMeasureRest, and adjust the > > #'minimum-length. > > Ah, thats a nice idea. I had tried a hidden voice with normal notes (like

Re: Widening one measure so that dynamics don't overlap

Am Montag, 17. August 2009 19:56:04 schrieb Kieren MacMillan: > Hi Reinhold, > > > How can I make that one measure wider, while all other measures are > > spaced normally? > > Here are a couple of ideas: > 1. \override the NoteColumn #'X-extent It seems I can't get this to work at all. >

Re: Wideining one measure so that dynamics don't overlap

> I have a score with a whole note with \p on the first beat > and \f on the third > beat of the measure. I'm doing this using parallel music > expressions: >   << { g1} { s2\p s\f} >> | % 42 > > Now, the problem is that the score consists almost entirely > of whole or half > notes, so that meas

Re: Automatically checking regtests

Reinhold Kainhofer wrote: Isn't this exactly what we already have (make test-baseline to create the Argh, how embarrassing! Sorry for the noise. Regards, Michael ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/list

Re: Wideining one measure so that dynamics don't overlap

Hi Reinhold, How can I make that one measure wider, while all other measures are spaced normally? Here are a couple of ideas: 1. \override the NoteColumn #'X-extent 2. \override the Score.NonMusicalPaperColumn #'padding 3. create a new dynamic which includes both dynamics and the

Wideining one measure so that dynamics don't overlap

I have a score with a whole note with \p on the first beat and \f on the third beat of the measure. I'm doing this using parallel music expressions: << { g1} { s2\p s\f} >> | % 42 Now, the problem is that the score consists almost entirely of whole or half notes, so that measure is too small a

Re: PDF

Unfortunately currently no. Freeman Gilmore wrote: Is there a PDF [or all in one HTML]of the LilyPondTool User's Guide? I want to print it. Thanks, fg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinf

Re: Automatically checking regtests (was: Re: Minor releases?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 17. August 2009 16:08:36 schrieb Michael Käppler: > [CC to -devel] > > > (nobody checks the regression tests for each release, for example > > -- and that's trivially done with a web browser!) > > That reminds me of an idea I recently had: W

Re: ? jedit

This is the default path of lilypond.exe on windows. You might have installed LilyPond to a different folder. Freeman Gilmore wrote: Step 4, I did nothing but 'LilyPondTool/Command' has first line 'c\Program Files\LilyPond\usr\bin'; is this the path? - Original Message - From: "Bertal

Re:? jedit

>> Step one complete but JEdit hangs on open at "run startup >> scripts", [V. 4.3pre17]. The same thing happened to me on Vista64, Java 1.6. The solution: when you run the installer you are presented 4 options. One is to install stuff necessary to create your own plugins, you can uncheck it,

Re: Minor releases?

Le dimanche 16 août 2009 à 14:34 -0700, Graham Percival a écrit : > On Sun, Aug 16, 2009 at 11:48:53AM -0400, David Raleigh Arnold wrote: > > I don't see any straightforward way of seeing a changelog or > > anything which tells the differences between minor releases. > > The git log messages. And

Re: Producing a small bar...

Hi Alberto, I saw it more like a double barline that is not shown complete, Then use something like: \version "2.13" shortDB = { \once \override Staff.BarLine #'bar-size = #2 \once \override Staff.BarLine #'Y-offset = #1 \bar "||" } shortBarMusic = \relative c' { c2 b4 r8 \shortDB a

Automatically checking regtests (was: Re: Minor releases?)

[CC to -devel] (nobody checks the regression tests for each release, for example -- and that's trivially done with a web browser!) That reminds me of an idea I recently had: Wouldn't it be possible to automatically generate a sort of "checksum" for each regression-test output-file and compar

Re: ? jedit

Well, quite much if you have a slow connection and jEdit connects to a slow download mirror. It's like 24MB. Freeman Gilmore wrote: Removed the c:\documents and settings\administrator\.jedit\perspective.xml file worked. Step 3, i have a window "Downloading LilyPo...;[LilyPondTool-2.12.897.zip

Re: ? jedit

Then remove the c:\documents and settings\yourname\.jedit\perspective.xml file. Then start jedit 4.3pre17 again. If that doesn't help, remove the entire .jedit folder. Freeman Gilmore wrote: xp (32) pro with all the s.p.'s - Original Message - From: "Bertalan Fodor (LilyPondTool)"

Re: ? jedit

Which OS are you using? Freeman Gilmore wrote: - Original Message - From: "Bertalan Fodor" To: "Mark Polesky" ; ; "Freeman Gilmore" Sent: Monday, August 17, 2009 3:26 AM Subject: Re: ? jedit Please do exactly the following. 0. Remove the jedit what you have installed. 1. Install

Re: Producing a small bar...

Hi Marek Klein wrote: > Hi, > > 2009/8/16 Alberto Simões > > > Hello > > Any hint on how to produce the output similar to the one in the picture? > (regarding the small bar and ff bellow). > > Thanks > Alberto > > > do you mean small

Re: Need some help with \include "makam.ly"

Graham Percival wrote: > I told you how to "build up the available documentation". If > you're not willing to help, then why should anybody else feel > motivated to do it? Did I ever say I wasn't willing? :-) ___ lilypond-user mailing list lilypond-us

Re: Need some help with \include "makam.ly"

Joseph Wakeling wrote: > So it seems worthwhile to gradually build up the > available documentation on them until a more extensive description is > completed and can be incorporated into its own part of the docs. ... as is already the case with Arabic notation (NR 2.9.1). In the long run I could

Re: Need some help with \include "makam.ly"

On Mon, Aug 17, 2009 at 01:02:23PM +0100, Joseph Wakeling wrote: > So it seems worthwhile to gradually build up the > available documentation on them until a more extensive description is > completed and can be incorporated into its own part of the docs. I told you how to "build up the available d

Re: Need some help with \include "makam.ly"

Jay Hamilton wrote: > I'd second the table idea, The link would be helpful or just a "see- LM > 4.6.3" too. 'See LM 4.6.3' is already there, but a link would be nice. :-) Table of note names I think definitely necessary. I don't know what the general consensus is on these snippets, but they illu

Re: Need some help with \include "makam.ly"

Graham Percival wrote: > Interesting. Nobody who touched that part of the docs, including > me, has ever installed lilypond via a package manager. Hopefully > Trevor can modify the section accordingly. In my case this is Ubuntu 9.04. I don't know if it varies with different distros, but the loc

Re: Need some help with \include "makam.ly"

On Mon, Aug 17, 2009 at 12:07:44PM +0100, Joseph Wakeling wrote: > Neil Puttock wrote: > > Can you suggest any improvements for this snippet's documentation? It > > does already mention where the pitch names are defined (ly/makam.ly). > > An actual link to LM section 4.6.3 would help. Also, the

Re: Need some help with \include "makam.ly"

Neil Puttock wrote: > Can you suggest any improvements for this snippet's documentation? It > does already mention where the pitch names are defined (ly/makam.ly). An actual link to LM section 4.6.3 would help. Also, the details of the location of the ly/ folder are not correct. It gives the lo

Re: Producing a small bar...

Hi, 2009/8/16 Alberto Simões > Hello > > Any hint on how to produce the output similar to the one in the picture? > (regarding the small bar and ff bellow). > > Thanks > Alberto > do you mean small barline? I would say it is rather caesura. See this snippet: > -- Marek Klein http://gregorian

Re: ? jedit

Please do exactly the following. 0. Remove the jedit what you have installed. 1. Install the latest development version of jedit. 2. Start jedit and in the plug-in manager install tab check the checkbox for lilypondtool. Click install. 3. After the download finishes close the plug-in manager an