Re: Accidentals tied over a system break

2015-10-08 Thread Urs Liska
Am 8. Oktober 2015 19:59:57 MESZ, schrieb Sven : >Sorry, I didn't know this is a known issue. > >And thanks for correcting me on how to actually remove the second >sharp, >Urs: \once \omit Accidental get's rid of the bugger, while \once \hide >Accidental makes it transparent, leaving its space in

Re: Accidentals tied over a system break

2015-10-08 Thread Sven
Sorry, I didn't know this is a known issue. And thanks for correcting me on how to actually remove the second sharp, Urs: \once \omit Accidental get's rid of the bugger, while \once \hide Accidental makes it transparent, leaving its space in tact. Sven 2015-10-08 19:14 GMT+02:00 David Kastrup :

Re: Accidentals tied over a system break

2015-10-08 Thread David Kastrup
Simon Albrecht writes: > On 08.10.2015 16:38, Trevor Daniels wrote: >> Furthermore, if the tie is removed the sharp on the final fis >> is also removed. The issue is, without the \break the final fis >> needs the sharp as the second fis doesn't have one, being tied >> to the first fis. Adding t

Re: Accidentals tied over a system break

2015-10-08 Thread Simon Albrecht
On 08.10.2015 16:38, Trevor Daniels wrote: Furthermore, if the tie is removed the sharp on the final fis is also removed. The issue is, without the \break the final fis needs the sharp as the second fis doesn't have one, being tied to the first fis. Adding the \break causes the second fis to ne

Re: Accidentals tied over a system break

2015-10-08 Thread Urs Liska
Am 08.10.2015 um 15:40 schrieb Sven: > Reading my way through Behind Bars by Elaine Gould, I'm trying to > replicate some of the examples in LilyPond. One of them contains a tie > over a system break: > > \version "2.18.2" > > \relative c'' { > r2. fis,4~ | \break > fis8 a16

Re: Accidentals tied over a system break

2015-10-08 Thread Trevor Daniels
Phil Holmes wrote Thursday, October 08, 2015 3:21 PM > From: "Thomas Morley" > To: "Sven" > Cc: "lilypond-user" > Sent: Thursday, October 08, 2015 3:10 PM > Subject: Re: Accidentals tied over a system break > > >> 2015-10-08 15:40 G

Re: Accidentals tied over a system break

2015-10-08 Thread David Kastrup
Thomas Morley writes: > 2015-10-08 15:40 GMT+02:00 Sven : >> Reading my way through Behind Bars by Elaine Gould, I'm trying to replicate >> some of the examples in LilyPond. One of them contains a tie over a system >> break: >> >> \version "2.18.2" >> >> \relative c'' { >> r2. fis,4~ | \break >

Re: Accidentals tied over a system break

2015-10-08 Thread Phil Holmes
- Original Message - From: "Thomas Morley" To: "Sven" Cc: "lilypond-user" Sent: Thursday, October 08, 2015 3:10 PM Subject: Re: Accidentals tied over a system break 2015-10-08 15:40 GMT+02:00 Sven : Reading my way through Behind Bars by Elaine Gould,

Re: Accidentals tied over a system break

2015-10-08 Thread Thomas Morley
2015-10-08 15:40 GMT+02:00 Sven : > Reading my way through Behind Bars by Elaine Gould, I'm trying to replicate > some of the examples in LilyPond. One of them contains a tie over a system > break: > > \version "2.18.2" > > \relative c'' { > r2. fis,4~ | \break > fis8 a16 fis r8 r2 \bar "|." >

Accidentals tied over a system break

2015-10-08 Thread Sven
Reading my way through Behind Bars by Elaine Gould, I'm trying to replicate some of the examples in LilyPond. One of them contains a tie over a system break: \version "2.18.2" \relative c'' { r2. fis,4~ | \break fis8 a16 fis r8 r2 \bar "|." } LP puts a sharp in front of the first f# in me