Ah, success! (Carl: you probably took out the barline repeat I had at the
Trio, but it just now dawned on me to do that)
Thanks for your help!!!
Mike Dean


On Mon, Oct 26, 2020 at 3:03 PM Mike Dean <dean...@aquinas.edu> wrote:

> Hi Carl:
> Is \include "english.ly" different from \language "english"?
>
> Part of my residing in the weeds is not being sure where \define command
> (and its relatives like \defineBarLine) ought to go...while the
> compilation didn't crash, the bar line construction was ignored in this case
> Mike Dean
>
>
> On Mon, Oct 26, 2020 at 2:56 PM Carl Sorensen <c_soren...@byu.edu> wrote:
>
>> Try this:
>>
>>
>>
>> \version "2.20.00"
>>
>> \include "english.ly"
>>
>> \defineBarLine ".|:-|." #'("|." ".|:" "")
>>
>>
>>
>> {
>>
>>   \repeat volta 2 {
>>
>>   d2 d8 c d e | f4 f8. e16 d2 | e2 e8 d e f | g4 g8. f16 e2 |
>>
>>   a4 a8. g16 f8. g16 a8. f16 | g4 g8. f16 e8. f16 g8. e16 |
>>
>>   g4 a8. g16 f8. f16 e8. e16 | d4 g8. g16 g4 r8 g, |
>>
>>   c4. g8 c4 d | e4. c8 e4 f | g e f d |}
>>
>>   \alternative {
>>
>>    {c c8. c16 c4 r }
>>
>>    {c c8. c16 c4\mark "Fine" r \bar ".|:-|." }
>>
>>   }
>>
>>
>>
>>   \break
>>
>> \mark "Trio" a4.-\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8. e16 |
>>
>>   a4 c  b   e | d8. c16 b8. c16 b2 |
>>
>>   a4. r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16 gs8. e16 |
>>
>>   a4 c  b   e | a,4 a8. a16 a4 r |
>>
>>   }
>>
>>
>>
>> Carl
>>
>>
>>
>>
>>
>> *From: *lilypond-user <lilypond-user-bounces+carl.d.sorensen=
>> gmail....@gnu.org> on behalf of Mike Dean <dean...@aquinas.edu>
>> *Date: *Monday, October 26, 2020 at 3:30 PM
>> *To: *"lilypond-user@gnu.org" <lilypond-user@gnu.org>
>> *Subject: *Re: I ought to have a bar line here...
>>
>>
>>
>> Still stumped....
>>
>> \version "2.20.0"
>>
>> {
>>
>>  \alternative {
>>    {c c8. c16 c4 r }
>>    {c c8. c16 c4\mark "Fine" r
>> \markup \vspace #1
>>
>> \defineBarLine ".|:-|." #'("|." ".|:" #f)
>> \markup \bold \typewriter "\".|:-|.\""
>>     \bar ".|:-|." }
>>   }
>>   \break
>>
>>     \repeat volta 2 {
>>   \bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16 | a4. r16 e a8. e16
>> gs8. e16 |
>>
>> }
>>
>> has generated the following errors
>>
>> *Starting lilypond-windows.exe 2.20.0
>> [March-of-the-Russian-Imperial-Guard.ly]...*
>>
>> Processing `C:/Users/Mike
>> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly'
>>
>> Parsing...
>>
>> C:/Users/Mike
>> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:27:1
>> <http://0>: error: markup outside of text script or \lyricmode
>>
>>
>>
>> \markup \vspace #1
>>
>>
>>
>> C:/Users/Mike
>> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:30:1
>> <http://1>: error: markup outside of text script or \lyricmode
>>
>>
>>
>> \markup \bold \typewriter "\".|:-|.\""
>>
>>
>>
>> Interpreting music...[8][16][24]
>>
>> C:/Users/Mike
>> Dean/AppData/Local/Temp/frescobaldi-ou5fxqul/tmpkydf0fg6/March-of-the-Russian-Imperial-Guard.ly:36:55
>> <http://2>: warning: barcheck failed at: 1/2
>>
>> \bar ".|:"\mark "Trio" a4.\p r16 e a8. e16 gs8. e16
>>
>> | a4. r16 e a8. e16 gs8. e16 |
>>
>>
>>
>>
>>
>> So maybe I'll have to draw it in the PDF, since I seem to be at the point
>> that my understanding of LilyPond is enough to get me stuck in the weeds?
>>
>>
>>
>> (the first of Aaron's suggestions did not generate a bar line before the
>> Trio....would enclosing the piece in two separate pairs of braces be
>> useful?)
>>
>>
>> Mike Dean
>>
>>
>>
>>
>>
>> On Sun, Oct 25, 2020 at 7:19 AM Aaron Hill <lilyp...@hillvisions.com>
>> wrote:
>>
>> On 2020-10-25 6:25 am, Christian Masser wrote:
>> > Aaron Hill <lilyp...@hillvisions.com> schrieb am So., 25. Okt. 2020,
>> > 04:38
>> >
>> >> You have to use a special bar line type when it breaks across a line:
>> >>
>> >> %%%%
>> >> \version "2.20.0"
>> >> \paper { indent = 0 line-width = 3\cm ragged-right = ##f }
>> >>
>> >> \markup \bold \typewriter "\".|:-||\""
>> >> { R1 \bar ".|:-||" \break R1 }
>> >>
>> >
>> > Out of pure interest: does anyone know why this seems to be "in the
>> > wrong
>> > order"? Why does the ". |:" of the second line come in front of the
>> > "||"
>> > which - viewed from a musical standpoint - should happen before?
>>
>> Near as I can tell, the naming convention is "primary-secondary".  Only
>> a bar line breaking across a line will show both styles.  Otherwise, it
>> is the style before the hyphen that is used.
>>
>>
>> -- Aaron Hill
>>
>>

Reply via email to