Re: Bar lines within bars inhibit bar numbering

The way to print the first bar number is explained in the first of the "Selected Snippets" of this section. http://lilypond.org/doc/v2.19/Documentation/notation/bars#bar-numbers On 12/12/2019 17:32, Peter Toye wrote: Re: Bar lines within bars inhibit bar numbering Hi Timothy, J

Re: Bar lines within bars inhibit bar numbering

Hi Timothy, Just done a bit more poking around. According to Internals, all-bar-numbers-visible shows all bar numbers including the first one, but it doesn't seem to as the first bar number isn't printed (not that I want it). I also tried first-bar-number-invisible but that gave the same effec

Re: Bar lines within bars inhibit bar numbering

t bar number is explained in the first of the "Selected Snippets" of this section. http://lilypond.org/doc/v2.19/Documentation/notation/bars#bar-numbers On 12/12/2019 17:32, Peter Toye wrote: Re: Bar lines within bars inhibit bar numbering

Re: Bar lines within bars inhibit bar numbering

Am Do., 12. Dez. 2019 um 17:05 Uhr schrieb Peter Toye : > > The example below shows the issue. The mid-bar line with a \break does not > show the bar number at the beginning of the next line - I would expect '2'. A > \break at the end of a bar gives the expected result. > > Also, the commented ou

Re: Bar lines within bars inhibit bar numbering

Adding the layout block will number partial bars in brackets. \version "2.19.83" \language "english" \layout {   \context { \Score barNumberVisibility = #all-bar-numbers-visible } } \score {   \new Staff {     \clef "treble"     \time 4/4     {   \override BarNumber.break-visibility = ##(

Re: Bar lines within bars inhibit bar numbering

Thursday, December 12, 2019, 4:39:43 PM, Rick Kimpel wrote: Peter You need an extra # \override BarNumber.break-visibility = ##(#t #t #t) So I do. Thanks. One day I'll get to grips with the tweaking syntax. But that doesn't do what you're talking about. I had something similar in a piece with

Re: Bar lines within bars inhibit bar numbering

Thursday, December 12, 2019, 5:10:26 PM, Timothy Lanfear wrote: Adding the layout block will number partial bars in brackets. Brilliant. Thanks. \version "2.19.83" \language "english" \layout { \context { \Score barNumberVisibility = #all-bar-numbers-visible } } \score { \new Staff {

Re: Bar lines within bars inhibit bar numbering

Peter You need an extra # \override BarNumber.break-visibility = ##(#t #t #t) But that doesn't do what you're talking about. I had something similar in a piece with 4/4 + 3/4 time with a dotted barline. I ended up just manually renumbering the bars numbers with: \set Score.currentBarNumber Proba

Re: Bar lines at far left of single staff systens.

On 6/10/18 3:53 PM, Aaron Hill wrote: On 2018-06-10 12:37, Gloops wrote: \version "2.18.2" \new RhythmicStaff \with {    \consists "System_start_delimiter_engraver"    systemStartDelimiter = #'SystemStartBar    \override SystemStartBar.collapse-height = 0    \override SystemStartBar.thickness =

Re: Bar lines at far left of single staff systens.

It works!!! Thank you very much. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bar lines at far left of single staff systens.

On 2018-06-10 12:37, Gloops wrote: \version "2.18.2" \new RhythmicStaff \with { \consists "System_start_delimiter_engraver" systemStartDelimiter = #'SystemStartBar \override SystemStartBar.collapse-height = 0 \override SystemStartBar.thickness = 2 } { c'1 \break c'1 \break c

Re: Bar lines at far left of single staff systens.

%Start of code Hello! \version "2.18.2" \new RhythmicStaff \with { \consists "System_start_delimiter_engraver" systemStartDelimiter = #'SystemStartBar \override SystemStartBar.collapse-height = 0 \override SystemStartBar.thickness = 2 } { c'1 \break c'1 \break c'1

Re: Bar lines at far left of single staff systens.

Hello!Is it possible to do the same with RhythmicStaff please ???Thank you -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bar lines at far left of single staff systens.

Hello! Is it possible to do the same with RhythmicStaff please ??? Thank you -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bar lines at far left of single staff systens.

Hello! Is it possible to do the same with RhythmicStaff please ??? Thank you -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bar lines at far left of single staff systens.

Hello ! Is it possible to do the same for RhythmicStaff ??? Thank you -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bar lines at far left of single staff systens.

Hello! Is it possible to do the same with RhythmicStaff please ??? Thank you -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bar lines at far left of single staff systens.

On 6/5/18 4:20 AM, Thomas Morley wrote: 2018-06-05 7:24 GMT+02:00 dfro : On 6/4/18 11:34 PM, David Wright wrote: On Mon 04 Jun 2018 at 22:38:35 (-0400), dfro wrote: Is there a setting to get bar lines to show on the far left side of single staff systems? I haven't been able to find a way to do

Re: Bar lines at far left of single staff systens.

2018-06-05 7:24 GMT+02:00 dfro : > On 6/4/18 11:34 PM, David Wright wrote: >> >> On Mon 04 Jun 2018 at 22:38:35 (-0400), dfro wrote: >>> >>> Is there a setting to get bar lines to show on the far left side of >>> single staff systems? I haven't been able to find a way to do this, >>> if it is possi

Re: Bar lines at far left of single staff systens.

On 6/4/18 11:34 PM, David Wright wrote: On Mon 04 Jun 2018 at 22:38:35 (-0400), dfro wrote: Is there a setting to get bar lines to show on the far left side of single staff systems? I haven't been able to find a way to do this, if it is possible. Put the staff in a grand staff thus: \new Gr

Re: Bar lines at far left of single staff systens.

On 6/4/18 10:52 PM, Karlin High wrote: On 6/4/2018 9:38 PM, dfro wrote: Is there a setting to get bar lines to show on the far left side of single staff systems? That sounds similar to this thread. From the example there,

Re: Bar lines at far left of single staff systens.

On Mon 04 Jun 2018 at 22:38:35 (-0400), dfro wrote: > Is there a setting to get bar lines to show on the far left side of > single staff systems? I haven't been able to find a way to do this, > if it is possible. Put the staff in a grand staff thus: \new GrandStaff << \new Staff << and add

Re: Bar lines at far left of single staff systens.

On 6/4/2018 9:38 PM, dfro wrote: Is there a setting to get bar lines to show on the far left side of single staff systems? That sounds similar to this thread. From the example there, you can adjust the SystemStartBar.thickn

Re: Bar Lines and Compound Time Signature

Worked like a charm. Thanks! -- View this message in context: http://lilypond.1069038.n5.nabble.com/Bar-Lines-and-Compound-Time-Signature-tp188471p188479.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lily

Re: Bar Lines and Compound Time Signature

Am 12.03.2016 um 19:32 schrieb Edward Ardzinski: I would like the bar number on the second line to be 9, not 5, counting each bar of 17 as 1 bar of 9 and another of 8...then have 18 on the beginning of the 3rd line in the pdf You could use an extra voice for the changing measure lengths (ins

Re: Bar Lines and Compound Time Signature

compound_time_signature_bar_line_issue.pdf compound_time_signature_bar_line_issue.ly I would like the

Re: Bar Lines and Compound Time Signature

2016-03-12 17:36 GMT+01:00 Edward Ardzinski : > I'm working on a piece that alternates between 9/8 and 4/4. The compound > time signature is great. Where in my original piece I had the time changes > in the fragmentary 2 bar music variables, with the compound time signature I > removed the time c

Re: Bar lines in polyphonic music and words under split voices

Quoting Do something Artistic (vegasart...@hotmail.com): > I have been working on a piece of music for some time now and cannot seem to > get the following to happen. > [...] > 2. attach words to a split vocal line of the form << {}\\ {}>> lilypond > seems to want to just skip over it and go to th

Re: Bar lines in polyphonic music and words under split voices

Am 29.09.2015 um 04:48 schrieb Do something Artistic: > I have been working on a piece of music for some time now and cannot > seem to get the following to happen. > > 1. vocal parts with different measure lengths. Lilypond always seems > to want to line bars up especially when one bar now has

Re: Bar lines in polyphonic music and words under split voices

Do something Artistic writes: > I have been working on a piece of music for some time now and cannot > seem to get the following to happen. > > 1. vocal parts with different measure lengths. Lilypond always seems > to want to line bars up especially when one bar now has six beats from > four or

Re: Bar lines in polyphonic music and words under split voices

Hi Spencer, Please always send a tiny example: http://www.lilypond.org/tiny-examples.html How about : \version "2.18.2" voiceA = \relative { \time 6/4 c''4 d e f g a \time 4/4 g f e d c1 } voiceB = \relative { \time 6/4 s1. \time 4/4 g'4 a b c s1 } lyricsA = \lyricmode {

Re: Bar lines in polyphonic music and words under split voices

Spencer, Not completely sure what you mean in #1, but in #2 the polyphonic shorthand << {} \\ {} >> should NEVER be used in a place where there are lyrics involved. This is because it creates completely new voices during that section, hence the skips you are seeing. I'd definitely use explicit voi

Re: Bar lines

Peter Meanwell writes: > Using 2.18.0 and Frescobaldi. Entering code for double bar line at end of > line > and repeat bar > on next shows no bar lines at all. http://www.lilypond.org/tiny-examples.html> -- David Kastrup ___ lilypond-user mailin

Re: Bar lines in 2.19.0

Sorry, I didn't mean to do that. I remember when I first joined this list several people got irritated that I didn't quote when I would reply and so it was hard for them to follow the conversation. I thought it was always best to quote but I see what you mean about the top post now. I'll try to be

Re: Bar lines in 2.19.0

Please don't top-post with full-quote below. It makes a lot of additional editing work for those who want to reply in a sensible manner that does not clog up the digests and other people's mail feeds. SoundsFromSound writes: > Mike Solomon wrote >> Hey all, >> >> On 2.19.0, when I do: > Wher

Re: Bar lines in 2.19.0

On Nov 13, 2013, at 3:45 PM, SoundsFromSound wrote: > Where is LilyPond version 2.19? I didn't think 2.18 was even released yet. > > That’s where current master is on the git branch. Cheers, MS___ lilypond-user mailing list lilypond-user@gnu.org ht

Re: Bar lines in 2.19.0

Where is LilyPond version 2.19? I didn't think 2.18 was even released yet. Mike Solomon wrote > Hey all, > > On 2.19.0, when I do: > > \relative c' { > f1 \bar "|" > f1 \bar "." > g1 \bar "||" > a1 \bar ".|" > b1 \bar ".|." > c1 \bar "|.|" > d1 \bar "|." > e1 \bar "|:" > f1 \bar ":|” > } > >

Re: Bar lines in 2.19.0

Am 13.11.2013 10:43, schrieb David Kastrup: Mike Solomon writes: Hey all, On 2.19.0, when I do: \relative c' { f1 \bar "|" f1 \bar "." g1 \bar "||" a1 \bar ".|" b1 \bar ".|." c1 \bar "|.|" d1 \bar "|." e1 \bar "|:" f1 \bar ":|” } I get the attached result, which leaves out several bar lines

Re: Bar lines in 2.19.0

Mike Solomon writes: > Hey all, > > On 2.19.0, when I do: > > \relative c' { > f1 \bar "|" > f1 \bar "." > g1 \bar "||" > a1 \bar ".|" > b1 \bar ".|." > c1 \bar "|.|" > d1 \bar "|." > e1 \bar "|:" > f1 \bar ":|” > } > > I get the attached result, which leaves out several bar lines that > should n

Re: Bar lines in 2.19.0

Am 13.11.2013 10:30, schrieb Mike Solomon: Hey all, On 2.19.0, when I do: \relative c' { f1 \bar "|" f1 \bar "." g1 \bar "||" a1 \bar ".|" b1 \bar ".|." c1 \bar "|.|" d1 \bar "|." e1 \bar "|:" f1 \bar ":|” } I get the attached result, which leaves out several bar lines that should normally be

Re: Bar lines

This thread is extremely interesting. However, I think we're mixing two things here: 1. Defining semantically disjoint and intuitive bar line types (e.g., final measure ending bar line, start of repeat, end and start of repeat...) 2. Describing how a bar line type should be displayed The former

Re: Bar lines

On Mar 8, 2013, at 1:21 AM, Janek Warchoł wrote: > To be absolutely clear: i want both an 'end-bar' property and the > thing mentioned above. > To put it differently: i suggest to have an 'end-bar' property and set > its default value to a function which returns "|." for longer music > and "|" fo

Re: Bar lines

> To be absolutely clear: i want both an 'end-bar' property and the > thing mentioned above. OK. > Is my explanation clear? Yes, thanks. However, I still don't see the usefulness. Werner ___ lilypond-user mailing list lilypond-user@gnu.org htt

Re: Bar lines

Hi, On Fri, Mar 8, 2013 at 6:24 AM, Werner LEMBERG wrote: > >>> I really would not like to have to tell LilyPond for every single >>> fragment to not use a final bar line. >> >> Could you explain what you didn't like in my suggestion that said "if >> the music is more than 3 bars long, use a "|."

Re: Bar lines

>> I really would not like to have to tell LilyPond for every single >> fragment to not use a final bar line. > > Could you explain what you didn't like in my suggestion that said "if > the music is more than 3 bars long, use a "|." barline; if it's 3 or > less use a "|" barline"? I think that i

Re: Bar lines

Hi, On Thu, Mar 7, 2013 at 6:45 PM, David Kastrup wrote: > Marc Hohl writes: >> No – I still would prefer if LilyPond draws the final bar line without >> having to explicitely tell her. > > Take a look at > http://lilypond.org/doc/v2.17/Documentation/notation/writing-pitches> > > I really would

Re: Bar lines

Marc Hohl writes: > Am 07.03.2013 18:56, schrieb David Kastrup: > >> A piece has one final bar line. A music theory text has thousands of >> fragments without final bar line. > Ok, but this depends on what you write more often – from my rather > selfish point of view, I *never* wrote a music the

Re: Bar lines

On Thu, Mar 07, 2013 at 05:56:58PM +0100, David Kastrup wrote: > Marc Hohl writes: > > > What exactly do you mean by :spanbar ("xxx" "yyy")? > > I have absolutely no idea. I was just throwing out possible Scheme > syntax elements that could be used in such an interface Shucks, I've started thi

Re: Bar lines

On 03/07/2013 10:54 AM, Marc Hohl wrote: Am 07.03.2013 18:52, schrieb Paul Scott: [...] All musical sections do not end with \bar "|." so you do need to explicitly tell her. You, of course can create your own template to do that. How can I write a template for telling lilypond to end my scores

Re: Bar lines

Am 07.03.2013 19:00, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:52, schrieb Paul Scott: [...] All musical sections do not end with \bar "|." so you do need to explicitly tell her. You, of course can create your own template to do that. How can I write a template for telling l

Re: Bar lines

Am 07.03.2013 18:56, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:45, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: We use "|." for the end bar not because of its _visual_ properties, If that is the case, I would say \b

Re: Bar lines

Marc Hohl writes: > Am 07.03.2013 18:52, schrieb Paul Scott: >> [...] >> All musical sections do not end with \bar "|." so you do need to >> explicitly tell her. >> >> You, of course can create your own template to do that. > How can I write a template for telling lilypond to end my > scores with

Re: Bar lines

Marc Hohl writes: > Am 07.03.2013 18:45, schrieb David Kastrup: >> Marc Hohl writes: >> >>> Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: >> We use "|." for the end bar not because of its _visual_ properties, > If that is the case, I would say \bar "." is more logi

Re: Bar lines

Am 07.03.2013 18:52, schrieb Marc Hohl: Am 07.03.2013 18:45, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: We use "|." for the end bar not because of its _visual_ properties, If that is the case, I would say \bar "." is more logical.

Re: Bar lines

Am 07.03.2013 18:52, schrieb Paul Scott: [...] All musical sections do not end with \bar "|." so you do need to explicitly tell her. You, of course can create your own template to do that. How can I write a template for telling lilypond to end my scores with a final bar line? ___

Re: Bar lines

On Thu, Mar 07, 2013 at 06:39:40PM +0100, Marc Hohl wrote: > Am 07.03.2013 18:36, schrieb David Kastrup: > >Noeck writes: > > > >>>We use "|." for the end bar not because of its _visual_ properties, > >>If that is the case, I would say \bar "." is more logical. > >Zounds. Tell you what: I'd consi

Re: Bar lines

Am 07.03.2013 18:45, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: We use "|." for the end bar not because of its _visual_ properties, If that is the case, I would say \bar "." is more logical. Zounds. Tell you what: I'd consider that

Re: Bar lines

Marc Hohl writes: > Am 07.03.2013 18:36, schrieb David Kastrup: >> Noeck writes: >> We use "|." for the end bar not because of its _visual_ properties, >>> If that is the case, I would say \bar "." is more logical. >> Zounds. Tell you what: I'd consider that an actual improvement. > No – I

Re: Bar lines

Am 07.03.2013 18:36, schrieb David Kastrup: Noeck writes: We use "|." for the end bar not because of its _visual_ properties, If that is the case, I would say \bar "." is more logical. Zounds. Tell you what: I'd consider that an actual improvement. No – I still would prefer if LilyPond draw

Re: Bar lines

Noeck writes: >> We use "|." for the end bar not because of its _visual_ properties, > If that is the case, I would say \bar "." is more logical. Zounds. Tell you what: I'd consider that an actual improvement. Never thought of it myself. -- David Kastrup

Re: Bar lines

>> a) >> In a text I'd write >> p.e >> " >>This is the "Barform": >>|: Stollen :| >> Abgesang >> " As these symbols (|: :|) need a \bar command around and as \repeat is the command to be used for repeats, there is no need for that, imho. >> b) The present barline-interface is "p

Re: Bar lines

Am 07.03.2013 17:56, schrieb David Kastrup: Marc Hohl writes: Am 07.03.2013 10:06, schrieb David Kastrup: [...] Ok, here is the deal: I promise to give real thought about a way to _define_ repeat structures in such a straightforward manner that a user would understand how to create repeat str

Re: Bar lines

Marc Hohl writes: > Am 07.03.2013 10:06, schrieb David Kastrup: >> [...] >> Ok, here is the deal: I promise to give real thought about a way to >> _define_ repeat structures in such a straightforward manner that a user >> would understand how to create repeat structures of his own including >> wo

Re: Bar lines

Am 07.03.2013 10:06, schrieb David Kastrup: [...] Ok, here is the deal: I promise to give real thought about a way to _define_ repeat structures in such a straightforward manner that a user would understand how to create repeat structures of his own including working Midi and \expandRepeats as lo

Re: Bar lines

Noeck writes: > Am 06.03.2013 20:16, schrieb Marc Hohl: >> Am 06.03.2013 17:47, schrieb Janek Warchoł: >>> Hi all, >>> >>> i was very surprised by Marc's suggestion to revert his barline >>> interface commit. I'm pretty sure that everyone regards Marc's (and >>> Harm's) work in this area as very

Re: Bar lines

Am 06.03.2013 20:16, schrieb Marc Hohl: > Am 06.03.2013 17:47, schrieb Janek Warchoł: >> Hi all, >> >> i was very surprised by Marc's suggestion to revert his barline >> interface commit. I'm pretty sure that everyone regards Marc's (and >> Harm's) work in this area as very valuable and noone thin

Re: Bar lines

Am 07.03.2013 10:16, schrieb Marc Hohl: >> ] similar to | but wider look and looks like closing, like end > We have already \bar "[|:" and ":|]" defined but with a different meaning > (just give it a try ;-) Nice. That's definitely the right choice for this one. >> (Btw, I would have chosen §

Re: Bar lines

Janek Warchoł writes: > On Thu, Mar 7, 2013 at 10:06 AM, David Kastrup wrote: >> [snip snip] >> Ok, here is the deal: I promise to give real thought about a way to >> _define_ repeat structures in such a straightforward manner that a user >> would understand how to create repeat structures of hi

Re: Bar lines

Hi all, On Wed, Mar 6, 2013 at 10:18 PM, Noeck wrote: > Before trying it out and writing my first mail, thought I could use > custom barlines now out of the box. Would it make sense to have that? > I will explain what I mean: > \bar "|!." > would print a bar equivalent to a definition: > \def

Re: Bar lines

Am 06.03.2013 21:55, schrieb Noeck: Hi, It is orthogonal to us making \bar "|:" and \bar ":|" well-defined by letting : automatically imply a thick bar since nothing else makes sense. I don't think that this is the problem Joram struggled with. So he is defining a bar type "|:" himself. Yes,

Re: Bar lines

Thomas Morley writes: > 2013/3/6 David Kastrup : >> Marc Hohl writes: > [...] >>> The basic idea behind the bar line interface based on Harm's >>> work, and I like the idea of having a 1:1 representation of the >>> bar line stringwise. >> >> For specifying the visual composition of a particular

Re: Bar lines

Marc Hohl writes: > Am 06.03.2013 21:24, schrieb David Kastrup: >> Marc Hohl writes: >> >>> I am a bit disappointed that the discussion about \bar ":|." >>> rises half a year after the patch went through the revision >>> process. >> If you think this is the first time, you have missed a few time

Re: Bar lines

Am 06.03.2013 21:24, schrieb David Kastrup: Marc Hohl writes: I am a bit disappointed that the discussion about \bar ":|." rises half a year after the patch went through the revision process. If you think this is the first time, you have missed a few times. The revision process does not inco

Re: Bar lines

Hi *, Am 06.03.2013 02:59, schrieb Thomas Morley: > I'll try to answer your first two questions while demonstrating a step > by step example. thanks a lot for your very detailed and well thought example! It addresses and answers even more questions than I thought of. >> 3) Having a ":" in a span

Re: Bar lines

Hi, >>> It is orthogonal to us making \bar "|:" and \bar ":|" well-defined by >>> letting : automatically imply a thick bar since nothing else makes >>> sense. >> >> I don't think that this is the problem Joram struggled with. > > So he is defining a bar type "|:" himself. Yes, it was not my prob

Re: Bar lines

On 03/06/2013 02:16 PM, Marc Hohl wrote: > I'd rather see lilyponds input structure being optimized. The > \repeat construct doesnt allow for d'al segno, da capo and stuff > like that. + about 70 brazilian This was a surprising omission to me as a new LilyPond user, given how logically almost eve

Re: Bar lines

On Wed, Mar 6, 2013 at 11:56 PM, David Kastrup wrote: > Janek Warchoł writes: >> Similarly to Marc i'd very much like to see LilyPond automatically end >> pieces with final barline. > > No question about that: of course I'd also always like LilyPond to do > the right thing by itself. But if it i

Re: Bar lines

2013/3/6 David Kastrup : > Marc Hohl writes: [...] >> The basic idea behind the bar line interface based on Harm's >> work, and I like the idea of having a 1:1 representation of the >> bar line stringwise. > > For specifying the visual composition of a particular bar type: full > agreement. That

Re: Bar lines

Janek Warchoł writes: > On Wed, Mar 6, 2013 at 9:24 PM, David Kastrup wrote: >> Marc Hohl writes: >>> As I mentioned elsewhere, I seldom use the repeat sign explicitely, I >>> try to get along with \repeat volta. Moreover, I find it very annoying >>> to end every piece with an explicit \bar "|.

Re: Bar lines

On Wed, 6 Mar 2013 23:24:15 +0100 Janek Warchoł wrote: > > Similarly to Marc i'd very much like to see LilyPond automatically end > pieces with final barline. > I understand David's concern, but i think that it can be quite easily > addressed. For example, we could have a "final-barline" proper

Re: Bar lines

2013/3/6 Marc Hohl : > Am 06.03.2013 17:47, schrieb Janek Warchoł: > >> Hi all, >> >> i was very surprised by Marc's suggestion to revert his barline >> interface commit. I'm pretty sure that everyone regards Marc's (and >> Harm's) work in this area as very valuable and noone thinks of >> deleting

Re: Bar lines

2013/3/6 David Kastrup : > If I understand correctly, the barline definition commands basically > have two arguments. The first part is the name for accessing a bar > line, the second is a breakdown of the look for it in-line, at start of > line, at end of line. No, not exactly. >From Nr: \defin

Re: Bar lines

2013/3/6 David Kastrup : > Thomas Morley writes: >> You mentioned your concerns before (can't find it right now), though, >> personally I see no _coding-problem_. > > Good. Probably a little misunderstanding here, because I explained myself badly. I wanted to say, that the current discussion is

Re: Bar lines

Marc, On Wed, Mar 6, 2013 at 8:16 PM, Marc Hohl wrote: > Am 06.03.2013 17:47, schrieb Janek Warchoł: >> i was very surprised by Marc's suggestion to revert his barline >> interface commit. I'm pretty sure that everyone regards Marc's (and >> Harm's) work in this area as very valuable and noone t

Re: Bar lines

Werner LEMBERG writes: >> What does not make sense is to require the user to specify the >> visual composition of a bar every time he wants to use it. That's >> WYSIWYG without style sheets. > > Hmm. > >>> But if anyone wants to implement aliases, go ahead. >> >> I was of the impression that th

Re: Bar lines

> What does not make sense is to require the user to specify the > visual composition of a bar every time he wants to use it. That's > WYSIWYG without style sheets. Hmm. >> But if anyone wants to implement aliases, go ahead. > > I was of the impression that this was undesired. I can't remembe

Re: Bar lines

Marc Hohl writes: > I am a bit disappointed that the discussion about \bar ":|." > rises half a year after the patch went through the revision > process. If you think this is the first time, you have missed a few times. The revision process does not incorporate user feedback that we have seen i

Re: Bar lines

Am 06.03.2013 17:47, schrieb Janek Warchoł: Hi all, i was very surprised by Marc's suggestion to revert his barline interface commit. I'm pretty sure that everyone regards Marc's (and Harm's) work in this area as very valuable and noone thinks of deleting it at all! I am a bit disappointed tha

Re: Bar lines

Janek Warchoł writes: > Hi all, > > i was very surprised by Marc's suggestion to revert his barline > interface commit. I'm pretty sure that everyone regards Marc's (and > Harm's) work in this area as very valuable and noone thinks of > deleting it at all! > > What I see are two issues: > > a) s

Re: Bar lines

Hi all, i was very surprised by Marc's suggestion to revert his barline interface commit. I'm pretty sure that everyone regards Marc's (and Harm's) work in this area as very valuable and noone thinks of deleting it at all! What I see are two issues: a) should we change the character that produc

Re: Bar lines

Thomas Morley writes: > 2013/3/6 David Kastrup : > >> It is orthogonal to us making \bar "|:" and \bar ":|" well-defined by >> letting : automatically imply a thick bar since nothing else makes >> sense. >> >> We don't want to point users having a simple understandable problem >> to an explanatio

Re: Bar lines

2013/3/6 David Kastrup : > Marc Hohl writes: > >> Am 06.03.2013 02:59, schrieb Thomas Morley: >>> 2013/3/5 Noeck : Hi, I tried the (relatively) new bar line interface: \version "2.17.12" \defineBarLine "|:" #'(":||" "" "|:") % a) \defineBarLine ":||" #'(":.." "" " |

Re: Bar lines

Marc Hohl writes: > Am 06.03.2013 09:38, schrieb David Kastrup: >> Marc Hohl writes: >> >>> kudos for this detailed explanation! I wonder if the documentation about >>> bar lines should be enhanced in this way, or is there a place where this >>> information can be stored and made available for a

Re: Bar lines

Am 06.03.2013 09:38, schrieb David Kastrup: Marc Hohl writes: Am 06.03.2013 02:59, schrieb Thomas Morley: 2013/3/5 Noeck : Hi, I tried the (relatively) new bar line interface: \version "2.17.12" \defineBarLine "|:" #'(":||" "" "|:") % a) \defineBarLine ":||" #'(":.." "" " ||") % b) \new

Re: Bar lines

Marc Hohl wrote Wednesday, March 06, 2013 8:10 AM > Am 06.03.2013 02:59, schrieb Thomas Morley: > >> I'll try to answer your first two questions while demonstrating a step >> by step example. >> [snip long explanation] >> > kudos for this detailed explanation! I wonder if the documentation about

Re: Bar lines

Marc Hohl writes: > Am 06.03.2013 02:59, schrieb Thomas Morley: >> 2013/3/5 Noeck : >>> Hi, >>> >>> I tried the (relatively) new bar line interface: >>> \version "2.17.12" >>> \defineBarLine "|:" #'(":||" "" "|:") % a) >>> \defineBarLine ":||" #'(":.." "" " ||") % b) >>> >>> \new StaffGroup <<

Re: Bar lines

Am 06.03.2013 02:59, schrieb Thomas Morley: 2013/3/5 Noeck : Hi, I tried the (relatively) new bar line interface: \version "2.17.12" \defineBarLine "|:" #'(":||" "" "|:") % a) \defineBarLine ":||" #'(":.." "" " ||") % b) \new StaffGroup << \new Staff { a1 \bar "|:" a \bar "|:" } \new S

Re: Bar lines

2013/3/5 Noeck : > Hi, > > I tried the (relatively) new bar line interface: > \version "2.17.12" > \defineBarLine "|:" #'(":||" "" "|:") % a) > \defineBarLine ":||" #'(":.." "" " ||") % b) > > \new StaffGroup << > \new Staff { a1 \bar "|:" a \bar "|:" } > \new Staff { f'1 f' } >>> > > I have

Re: Bar lines appearing even with \stopStaff and \RemoveEmptyStaves

Alexandre Ficagna wrote: > > Hy, > > does someone know why, even with \stopStaff and \RemoveEmptyStaves, > the barlines on the upper staff stand still? > Below the code: > > you didn't apply \RemoveEmptyStaves \override VerticalAxisGroup #'remove-first = ##t to the RhythmicStaff Eluze -

Re: Bar Lines Disappear with Staff Line Count Change

On Sat, Mar 10, 2012 at 12:32 PM, Mark Mathias wrote: > Why do Bar Lines disappear when reducing the Staff Line count? I've tried > several alterations to the layout context for score, but don't get the right > results. > > \version "2.15.33" > > \relative c'' { > > \override Staff . StaffSymbol #

  1   2   >