Re: begin-repeat and end-repeat signs print inconsistently

2009-12-01 Thread -Eluze
peftypefty wrote: > > Depending on context, a particular begin-repeat sign or end-repeat sign > will > refuse to print even though others are printing fine within the same > document. > > Please share any insights on this difficulty and its possible solutions. > why don't you let Lilyponds bu

Right-to-Left

2009-12-01 Thread Hosam Adeeb Nashed
Yes, you read correctly! I always had a love-hate feeling towards Lilypond... It looks undeniably superb, but learning it is like hell. So, although most of my needs are well catered for by another open-source programme, PMW, I sometimes wish I could use Lilypond, if only to be able to benefit fr

Re: Right-to-Left

2009-12-01 Thread Valentin Villenave
On Tue, Dec 1, 2009 at 10:12 AM, Hosam Adeeb Nashed wrote: > So, is there any way this feature could be added to the arsenal?  I must admit > I'm impressed by the other features, notable hybrid key signatures, and > quarter-tones in the MIDI output. Greetings, I can add it as a feature request,

invisible tremolo beams

2009-12-01 Thread Stefan Thomas
Dear community, how can I make tremolo-beams invisible? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: invisible tremolo beams

2009-12-01 Thread Alexander Kobel
Stefan Thomas wrote: Dear community, how can I make tremolo-beams invisible? \override Beam #'transparent = ##t. But you won't recognize them as tremolos anymore, so you can just leave out the tremolo, right? Cheers, Alexander ___ lilypond-user

Re: \set vs \override

2009-12-01 Thread Anthony W. Youngman
In message <4b0bc390.1080...@internode.on.net>, Nick Payne writes Carl Sorensen wrote: On 11/24/09 2:57 AM, "Nick Payne" wrote: James Worlton wrote: Hi! In 2.13.6 I did a project and used: \set Score.markFormatter = #format-mark-box-alphabet and I got the boxes and the letter I (all in

bogus (and or missing) error messages

2009-12-01 Thread Hugh Myers
Often I get the following pattern--- say I'm working on bar 59 and make a mistake. After the compilation process, the error message refers to bar 22! Given that I'm working in relative mode, I'm confused as to how code that was moments before correct is now in error? Another pattern I see frequent

bar numbering

2009-12-01 Thread Hugh Myers
Clearly this doesn't work: \version "2.13.7" upper = { b c d } lower = { < gis, d e, >2. } { \time 3/4 << \new Staff \relative c'' { << \set Score.barAlways = ##t \set Score.defaultBarType = "|" \new Voice = "1" { \voiceOne \upper } \new Voice = "2" { \voice

vertical staff and tab

2009-12-01 Thread Hugh Myers
I've yet to chase down a working example that given: \version "2.13.7" upper = { e,, f g a b c d e f g a b c d e f g a b c d e s2 } lower = { s2. s2. s2. s2. s2. s2. s2. s2. } { \time 3/4 << \new Staff \relative c'' { << \new Voice = "1" { \voiceOn

Re: bar numbering

2009-12-01 Thread Brett Duncan
Hugh Myers wrote: Clearly this doesn't work: \version "2.13.7" upper = { b c d } lower = { < gis, d e, >2. } { \time 3/4 << \new Staff \relative c'' { << \set Score.barAlways = ##t \set Score.defaultBarType = "|" \new Voice = "1" { \voiceOne \upper } \new

Re: bar numbering

2009-12-01 Thread Hugh Myers
So for the truly picky, insert: \set Score.barNumberVisibility = #all-bar-numbers-visible \bar "" just before you change and let the bar numbers fall where they may! Much thanks Brett... --hsm On Tue, Dec 1, 2009 at 9:17 PM, Brett Duncan wrote: > Hugh Myers wrote: >> >> Clearly th

page break failure

2009-12-01 Thread Hugh Myers
Pardon the length of the piece of code, but clearly demonstrates the problem where as other pieces don't (got to be a page long for instance...): % % malaguena.ly -- q&d testbed for mixed notation score and tab. % \version "2.13.7" \header { title = "Malaguena" subtitle = "none" composer = "

Re: page break failure

2009-12-01 Thread Graham Percival
On Tue, Dec 01, 2009 at 09:57:00PM -0700, Hugh Myers wrote: > Pardon the length of the piece of code, but clearly demonstrates the > problem where as other pieces don't (got to be a page long for > instance...): > \version "2.13.7" I hope that you realize that 2.13.7 is an UNSTABLE, DEVELOPMENT r

Re: bogus (and or missing) error messages

2009-12-01 Thread Francisco Vila
2009/12/2 Hugh Myers : > Often I get the following pattern--- say I'm working on bar 59 and > make a mistake. After the compilation process, the error message > refers to bar 22! Given that I'm working in relative mode, I'm > confused as to how code that was moments before correct is now in > error

Re: bogus (and or missing) error messages

2009-12-01 Thread Hugh Myers
I'll see what I can do--- lucky for me my editor has unlimited undos. --hsm On Tue, Dec 1, 2009 at 11:12 PM, Francisco Vila wrote: > 2009/12/2 Hugh Myers : >> Often I get the following pattern--- say I'm working on bar 59 and >> make a mistake. After the compilation process, the error message >>

Re: page break failure

2009-12-01 Thread Hugh Myers
Second point taken. I hope you realize that 2.13 has bug fixes for 2.12--- yes? Without those, there is no project... I don't suppose you took a look? Did you notice that in included tablature? If you had, then you would perhaps have sent me a different 'Most spacing bugs can be reproduced...' Also

Re: page break failure

2009-12-01 Thread Hugh Myers
Here is the shortest template I use: \version "2.13.7" upper = { b c d } lower = { < gis, d e, >2. } { \time 3/4 << \new Staff \relative c'' { << \set Score.barNumberVisibility = #all-bar-numbers-visible \bar "" \override Score.BarNumber #'break-visibility = #'#(#

Re: page break failure

2009-12-01 Thread Marc Hohl
Hugh Myers schrieb: Second point taken. I hope you realize that 2.13 has bug fixes for 2.12--- yes? Yes, but 2.13.x is work in progress. There is a new layout engine which is still under improvement, as far as I know. So the layout may change considerably between 2.13.x and 2.13.y. 2.12.x is s

Re: bogus (and or missing) error messages

2009-12-01 Thread Hugh Myers
After some length of time, I've determined the 'undo' method won't get me there! This will have to wait until it happens again. --hsm On Wed, Dec 2, 2009 at 12:08 AM, Hugh Myers wrote: > I'll see what I can do--- lucky for me my editor has unlimited undos. > > --hsm > > On Tue, Dec 1, 2009 at 11

Re: page break failure

2009-12-01 Thread Marc Hohl
Hugh Myers schrieb: Here is the shortest template I use: \version "2.13.7" upper = { b c d } Use upper = { \repeat unfold 100 { b c d } } lower = { < gis, d e, >2. } and lower = { \repeat unfold 100 { < gis, d e, >. } } respectively. Marc { \time 3/4 << \new St

Re: page break failure

2009-12-01 Thread Hugh Myers
Since the project can't be done in 2.12, what do you suggest? --hsm On Wed, Dec 2, 2009 at 12:41 AM, Marc Hohl wrote: > Hugh Myers schrieb: >> >> Second point taken. I hope you realize that 2.13 has bug fixes for >> 2.12--- yes? > > Yes, but 2.13.x is work in progress. There is a new layout engi

Re: page break failure

2009-12-01 Thread Hugh Myers
Ah! That should be easy enough to work with--- I'll see what I can come up with. --hsm On Wed, Dec 2, 2009 at 12:43 AM, Marc Hohl wrote: > Hugh Myers schrieb: >> >> Here is the shortest template I use: >> >> \version "2.13.7" >> upper = { >>  b c d >> } >> > > Use > > upper = { >  \repeat unfold

Re: page break failure

2009-12-01 Thread Marc Hohl
Hugh Myers schrieb: Since the project can't be done in 2.12, what do you suggest? I inserted a paper block after the \header: \paper { indent = 0 between-system-space = 2\cm between-system-padding = #5 ragged-bottom=##f ragged-last-bottom=##f } You can play with the numbers, but at lea