Change barline-glyph question

Hi all v 2.25.26 I want barlines all dotted for one file, so from looking at define-grobs.scm I expected to be able to write \override Score.BarLine.glyph = "!" - which doesn't work but \override Score.BarLine.glyph-name = "!" does. any clues as to what I'm not understanding? thanks D

Re: Barline alignment on consecutive systems

e d e d c g a g a g a g f d e d e d e d c } > } > > In this example, at the very least the barline of the third system should > be moved either left or right. > Is there an easy way to tell Lilypond to offset barlines? I take it that you trying to reproduce the appearance of the B

Barline alignment on consecutive systems

lative { \time 3/4 R2.*2 d'''32 e d e d e d c g a g a g a g f d e d e d e d c \repeat unfold 3 { g a g a g a g f d e d c f g a c f a c f a16 r d,32 e d e d e d c g a g a g a g f d e d e d e d c } } In this example, at the very least the barline of the third system shoul

Re: Barline confusion/question

> "Joerg" == Joerg Zahn writes: Joerg> It is not my intent to derange this Joerg> discussion but why in the nether hells does the first line in Joerg> those scores always have an indentation. It is for the stuff you usually pu at the start of a score (but is omitted in these minimal examples

Re: Barline confusion/question

On Tue 11 Mar 2025 at 20:53:05 (-0500), Lilypond-User wrote: > Sorry for the late response. Using \bar ".|:-||” accomplished what I > needed, albeit confusingly. Since the II precedes the .|: on the output PDF, > why isn’t the correct syntax for this command \bar “||-.|:” ? I had > actuall

Re: Barline confusion/question

On Wed, 12 Mar 2025 at 09:46, Joerg Zahn wrote: > > It is not my intent to derange this discussion Hello, Please open a new thread then. > but why in the nether hells does the first line in those scores always have an indentation. Because this is standard music engraving practice. > I see no

Re: Barline confusion/question

On Wed, 12 Mar 2025, Joerg Zahn wrote: > It is not my intent to derange this discussion but why in the nether hells > does the first line in those scores always have an indentation. > I see no way of preventing this indentation. That is how music is traditionally formatted, and other engraving sy

Re: Barline confusion/question

y" == Timothy Lanfear writes: >> >> >> Timothy> The \section command is the simplest solution to this >> Timothy> problem. >> >> Timothy> \version "2.24.0" >> >> Timothy> { c''1 1 1 1 \break c''1 1 1

Re: Barline confusion/question

Timothy Lanfear > >>>>> <mailto:timo...@lanfear.me>> writes: >> >> >> Timothy> The \section command is the simplest solution to this >> Timothy> problem. >> >> Timothy> \version "2.24.0" >> >> Timothy> { c'&#x

Re: Barline confusion/question

Timothy> { c''1 1 1 1 \break c''1 1 1 1 \break \section > Timothy> \repeat volta 2 { d''1 1 1 1 } }-- > > This doesn't seem to work: there's no repeat barline at the start of > the line for the volta. > > \version "2.24.4

Re: Barline confusion/question

On 08/03/2025 08:44, Peter Chubb wrote: Timothy> \version "2.24.0" Timothy> {   c''1 1 1 1 \break   c''1 1 1 1 \break   \section Timothy> \repeat volta 2 {     d''1 1 1 1   } }-- This doesn't seem to work: there's no repeat barline

Re: Barline confusion/question

t; \repeat volta 2 {     d''1 1 1 1   } }-- This doesn't seem to work: there's no repeat barline at the start of the line for the volta. \version "2.24.4" \score { \new Staff \relative c' { f1 \bar "||" | \break \section \repeat v

Re: Barline confusion/question

> This sort of thing is common engraving practice > so I must be missing something obvious. Search for the following text in the docs: In addition, you can specify ".|:-||", which is equivalent to ".|:" except at line breaks, where it gives a double bar line at the end of the line and a start

Re: Barline confusion/question

On 07/03/2025 15:21, tim...@bitstream.net via LilyPond user discussion wrote: Of all the things in Lilypnd I find barline syntax perhaps the most baffling.  What I want is a double barline to end an 8 bar intro section at the end of a line (I am using \break to force 4 bars to a line) and then

Barline confusion/question

Of all the things in Lilypnd I find barline syntax perhaps the most baffling. What I want is a double barline to end an 8 bar intro section at the end of a line (I am using \break to force 4 bars to a line) and then a repeat barline at the start of the next line where the head begins. I’ve

Re: Barline through all staves

Dear Thomas, Let me know if the attached file achieves what you were hoping for. Thanks, -William % \version "2.25.21" scoreAViolinIPart = {c'4 c' c' c' c' c' c' c' c' c' c' c' c'1 } scoreAViolinIIPart = { % for every staff which is the BOTTOM of a group (example: piano left hand)

Barline through all staves

Hi, I have this Score: << \new StaffGroup << \scoreAViolinIPart \scoreAViolinIIPart >> \new ChoirStaff << \scoreASopranoVoicePart \scoreAAltoVoicePart \scoreATenorVoicePart \scoreABassVoicePart >> \scoreABassoContinuoPart >> I w

Re: Automatically set Hairpin.to-barline

GHT) will return '(). To fix this use > \override Hairpin.to-barline = > #(lambda (grob) >(let* ((right-bound (ly:spanner-bound grob RIGHT)) > (nhds (and (ly:grob? right-bound) (ly:grob-object right-bound > 'note-heads #f > (not nhds

Re: Automatically set Hairpin.to-barline

the engraver for dynamics only listenes to note columns, which includes notes and rests. It does not include MM rests. This then causes the code to fail, as (ly:spanner-bound grob RIGHT) will return '(). To fix this use \override Hairpin.to-barline = #(lambda (grob) (let* ((rig

Re: Automatically set Hairpin.to-barline

Many thanks David and Harm At 14:41 on 19 Nov 2024, Thomas Morley wrote: > Or even: > \override Hairpin.to-barline = > #(lambda (grob) >(let* ((right-bound (ly:spanner-bound grob RIGHT)) > (nhds (ly:grob-object right-bound 'note-heads #f)))

Re: Automatically set Hairpin.to-barline

Am Dienstag, 19. November 2024, 14:41:03 MEZ schrieb Thomas Morley: > > Though possibly this would need > > > > \override Hairpin.to-barline = > > > > #(ly:make-unpure-pure-container > > > >(lambda (grob) > > > &

Re: Automatically set Hairpin.to-barline

Am Di., 19. Nov. 2024 um 13:54 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Hi Mark, > > > > probably: > > > > \override Hairpin.to-barline = > > #(grob-transformer 'to-barline > > (lambda (grob orig) >

Re: Automatically set Hairpin.to-barline

Thomas Morley writes: > Hi Mark, > > probably: > > \override Hairpin.to-barline = > #(grob-transformer 'to-barline > (lambda (grob orig) > (let* ((right-bound (ly:spanner-bound grob RIGHT)) >(nhds (ly:grob-object right-boun

Re: Automatically set Hairpin.to-barline

Am Di., 19. Nov. 2024 um 11:58 Uhr schrieb Mark Knoop : > > I'm looking for a way to set a hairpin's to-barline property depending on > whether the terminating grob it is attached to is a note or a rest. I'd like > hairpins which end on a rest to stop at the barl

Automatically set Hairpin.to-barline

I'm looking for a way to set a hairpin's to-barline property depending on whether the terminating grob it is attached to is a note or a rest. I'd like hairpins which end on a rest to stop at the barline (to-barline = ##t), and hairpins which end on a note to continue to the note

Re: Barline scaling issues

} > ``` > > which produces this: > > [image: image.png] > > You can see the staff size transition -- the top one "wins" in the sense > that its larger barlines are longer. If you flip the magnification from the > bottom to the top, then the smaller lines "

Re: Barline scaling issues

p one "wins" in the sense that its larger barlines are longer. If you flip the magnification from the bottom to the top, then the smaller lines "win" and they are longer instead, meaning that the staff on top seems to always be the one ch

Re: Barline scaling issues

On Thu, 11 Jul 2024 at 22:10, Tom Brennan wrote: > > Hi all > > When using `\magnifyStaff #2/3`, I'm seeing weird transitions between the staves of a `StaffGroup`. For example, > > (snip) > > The question is, is this a bug or expected behavior? Is there a workaround t

Barline scaling issues

to the top, then the smaller lines "win" and they are longer instead, meaning that the staff on top seems to always be the one chosen to dictate the barline vertical span. It looks like you can get the barlines to be consistent by using the following workaround in a staff `\with` block: ``

Re: PianoPedalBracket.to-barline doesn't always work as expected

Hi Werner, >> Might I suggest that “to-barline” is potentially >> misleading/confusing…? > I suggest you file an issue. https://gitlab.com/lilypond/lilypond/-/issues/6709 Cheers, Kieren. __ My work day may look different than your work

Re: PianoPedalBracket.to-barline doesn't always work as expected

Hi Mats, > Exactly the same feature might also be useful for hairpins and other spanner > types Indeed! I’ll be sure to make the issue I submit a general spanner issue… Best, Kieren. __ My work day may look different than your work day. Please do not

Re: PianoPedalBracket.to-barline doesn't always work as expected

On 2024-04-12 12:05, Werner LEMBERG wrote: Might I suggest that “to-barline” is potentially misleading/confusing…? On the other hand: end-at-barline, for a pedal coded for release on a note **just after** a barline, might be more clearly descriptive of the current behaviour; and

Re: PianoPedalBracket.to-barline doesn't always work as expected

> Might I suggest that “to-barline” is potentially > misleading/confusing…? > > On the other hand: > > end-at-barline, for a pedal coded for release on a note **just > after** a barline, might be more clearly descriptive of the > current behaviour; and > &

Re: PianoPedalBracket.to-barline doesn't always work as expected

Hi all, Might I suggest that “to-barline” is potentially misleading/confusing…? On the other hand: end-at-barline, for a pedal coded for release on a note **just after** a barline, might be more clearly descriptive of the current behaviour; and extend-to-barline, for a pedal coded for

Re: PianoPedalBracket.to-barline doesn't always work as expected

Hi Jean, Of course you are right. Let me explain how I got to this to explain my confusion. My first attempt was to add it to the next note without using \override Staff.PianoPedalBracket.to-barline = ##t (as I wasn't aware of it existence at that point). What I discovered however is

Re: PianoPedalBracket.to-barline doesn't always work as expected

Le mardi 09 avril 2024 à 23:55 +0200, Maurits Lamers via LilyPond user discussion a écrit : > Hey all, > > I encountered a situation where the PianoPedalBracket setting to-barline > doesn't always do what you'd expect. Given the following code, the pedal > bracket is n

Re: PianoPedalBracket.to-barline doesn't always work as expected

Hi Aaron, Yes it does. It is just unexpected that this would be necessary. cheers Maurits Op 10-04-2024 om 00:12 schreef Aaron Hill: Does the empty chord construct help?   <>\sustainOff (I'm away from my normal environment, so I cannot test this locally to confirm.) -- Aaron Hill

Re: PianoPedalBracket.to-barline doesn't always work as expected

On 2024-04-09 2:55 pm, Maurits Lamers via LilyPond user discussion wrote: Only when the \sustainOff is placed outside of the tremolo, the bracket extends to the barline: %%% \version "2.24.0" \score {   \new Staff {     \clef bass     \time 6/8     \relative c' {    

PianoPedalBracket.to-barline doesn't always work as expected

Hey all, I encountered a situation where the PianoPedalBracket setting to-barline doesn't always do what you'd expect. Given the following code, the pedal bracket is not extended to the end of the bar: %%% \version "2.24.0" \score {   \new Staff {     \clef bass     \ti

Re: "\override BarLine" for a PianoStaff

Yes it does! Thank you. On Fri, Jan 26, 2024 at 11:23 PM Vaughan McAlley wrote: > > Hi Ivan, > > \new PianoStaff \with { \remove "Span_bar_engraver" } > > should work! > >

Re: "\override BarLine" for a PianoStaff

On Sat, 27 Jan 2024 at 11:08, Ivan Kuznetsov wrote: > "\override BarLine" for a PianoStaff > > I frequently use lilypond for short theory > examples for teaching, and for such examples > I often use the code: > >\override BarLine.transparent = ##t > > t

"\override BarLine" for a PianoStaff

"\override BarLine" for a PianoStaff I frequently use lilypond for short theory examples for teaching, and for such examples I often use the code: \override BarLine.transparent = ##t to make bar lines disappear. This has always worked for me for a single staff, but when I just t

Re: Anything similar to to-barline for extender lines of cresc/dim?

current file by adding \layout{   \context{     \Score     \override DynamicTextSpanner.to-barline = ##t   } } (or even putting these lines in an include file together with all other favorite settings of yours). My question was on

Re: Anything similar to to-barline for extender lines of cresc/dim?

1 1 1\f 1 1\cresc 1 1 1\f 1 1\cresc 1 1 1\f } { \theNotes \break \override DynamicTextSpanner.to-barline = ##t \theNotes } -- Knute Snortum

Re: Anything similar to to-barline for extender lines of cresc/dim?

On 2023-10-10 23:01, Mats Bengtsson wrote: On 2023-10-10 18:07, David Kastrup wrote: Have you tried not "anything like to-barline" but rather _exactly_ to-barline ? Like c -\tweak to-barline ##t \cresc and its ilk? Silly me! Too obvious to try. Well, in fact I was looking arou

Re: Anything similar to to-barline for extender lines of cresc/dim?

On 2023-10-10 18:07, David Kastrup wrote: Mats Bengtsson writes: Hi, Is there anything analogous to Hairpin.to-barline = #t that applies to the extender line of textual dynamics like \cresc or \dim? Unfortunately, I don't have a copy of Gould, but

Re: Anything similar to to-barline for extender lines of cresc/dim?

Mats Bengtsson writes: > Hi, > > Is there anything analogous to Hairpin.to-barline = #t that applies to > the extender line of textual dynamics like \cresc or \dim? > > Unfortunately, I don't have a copy of Gould, but to me all the options > I tried below look worse th

Anything similar to to-barline for extender lines of cresc/dim?

Hi, Is there anything analogous to Hairpin.to-barline = #t that applies to the extender line of textual dynamics like \cresc or \dim? Unfortunately, I don't have a copy of Gould, but to me all the options I tried below look worse than having an extender line that ends exactly below th

Re: barline in proportional notation disappear

> Thank you sooo much for your answer! > That’s amazing, it’s really clear and I’ll take a deep look at it! > What is MusicSE? I cannot find anything on google. Can u point me out to the > reference u said? > Cheers! As Jean said it is the music stackexchange thing. You’ve accidently replied t

Re: barline in proportional notation disappear

Hello, this was also posted on MusicSE, for reference here my reply: You are not getting some barlines as s1^"text" \bar "!" will insert the bar line after the skip, which is in your case in a random position later. Rather do \bar "!" s1^"text" to have the bar line at the exact posit

barline in proportional notation disappear

Hello, A while back, I reached out to this mailing list seeking assistance in building a Csound to LilyPond converter. What I had in mind was a tool to enhance the readability and presentation of Csound scores using LilyPond. For context, the Csound score format I'm working with is relatively

Re: Distance from barline to first note of bar

Hi Jean, >> I know >> describes the different spacing-style options, but can you comment on >> why/whether one would/should set both this spacing-style *and* another >> (e.g., minimum-space)? > I don't understand the question. Ho

Re: Distance from barline to first note of bar

Le dimanche 16 juillet 2023 à 08:51 -0400, Kieren MacMillan a écrit : > I know > describes the different spacing-style options, but can you comment on > why/whether one would/should set both this spacing-style *and* another (e.g., >

Re: Distance from barline to first note of bar

Hi all, > I won't comment on the default value I‘ve always found it too small… > \layout { > \context { > \Score > \override BarLine.space-alist.next-note = #'(semi-fixed-space . 10) > } > } I know descri

Re: Distance from barline to first note of bar

I won't comment on the default value, but: > Can the gap be extended by some ratio of global staff size? (I'm assuming a > fixed increase would make problems with scores with a larger basic staff > size, like my own.) Sure: ``` \layout { \context { \Score \override BarLine.

Distance from barline to first note of bar

Dear everybody, So I've been wondering about the distance between the barline and the first note of a measure. I'm not an expert typesetter by any means, but it does seem to me that the gap is narrower in lilypond scores than in examples by Gould, for instance. I've co

Re: Missing barline

Hi Rip_Mus, Try: \relative c' { c1 \bar ".|:-|" \break c1 } Cheers, Pierre Le dim. 14 mai 2023 à 11:17, Rip _Mus a écrit : > Hello, > in the following minimal example, at the end of the first line, the > barline is missing: > > ``` > \version &quo

Missing barline

Hello, in the following minimal example, at the end of the first line, the barline is missing: ``` \version "2.24.0" \relative c' { c1 \bar ".|:" \break c1 } ``` Is it possible to find a simple solution to implement? Thank you! Rip_mus

Re: Note head on barline

f any context specific stuff). Cheers, Valentin Am Mittwoch, 22. Februar 2023, 17:06:50 CET schrieb Immanuel Asmus: > Thank you, this works like a charm, even with tuplets, multiple voices > or staves (as far as I tested). > There is one case that doesn’t work as expected, but I do not (yet)

Re: Note head on barline

Thank you, this works like a charm, even with tuplets, multiple voices or staves (as far as I tested). There is one case that doesn’t work as expected, but I do not (yet) need it: Namely, when the note on the barline is dotted, the dot will not be moved. Try, e.g., \fixed c' { \time 3/4

Re: Fwd: Note head on barline

Le mercredi 22 février 2023 à 15:05 +0100, Immanuel Asmus a écrit : > Dear all,I want to typeset the sincopa as it was customary > between 1500 and 1700 AD: A note whose duration would exceed the bar > should be placed directly on the barline. (Attached

Re: Visible Barline in ChoirStaff

Leo Correia de Verdier writes: > Your example doesn’t work because the bars between the staves are in fact not > BarLine grobs, but SpanBar grobs, and they would live in the ChoirStaff > context. > The difference between a ChoirStaff and a StaffGroup is that the Choirstaff >

Re: Visible Barline in ChoirStaff

excellent! Worked perfect. Your example doesn’t work because the bars between the staves are in fact not BarLine grobs, but SpanBar grobs, and they would live in the ChoirStaff context. The difference between a ChoirStaff and a StaffGroup is that the Choirstaff doesn’t contain the

Re: Visible Barline in ChoirStaff

Your example doesn’t work because the bars between the staves are in fact not BarLine grobs, but SpanBar grobs, and they would live in the ChoirStaff context. The difference between a ChoirStaff and a StaffGroup is that the Choirstaff doesn’t contain the Span_Bar_Engraver, that creates them. You

Re: Visible Barline in ChoirStaff

thx Jean, yes I want a ChoirStaff - but only at a specific bar one line through ALL voices.. Le 8 févr. 2023 à 16:13, Johannes Roeßler a écrit :  Hi Group, how can I add a visible (in the sense of connecting all staffs) barline in a choirstaff? I tried  \once \override

Re: Visible Barline in ChoirStaff

> Le 8 févr. 2023 à 16:13, Johannes Roeßler a écrit : > >  > Hi Group, > > how can I add a visible (in the sense of connecting all staffs) barline in a > choirstaff? > > I tried \once \override Staff.BarLine.transparent = ##f \bar "|" > > but

Visible Barline in ChoirStaff

Hi Group, how can I add a visible (in the sense of connecting all staffs) barline in a choirstaff? I tried  \once \override Staff.BarLine.transparent = ##f \bar "|" but o course it doesn't work, for its just in a staff... Best regards Johannes

Re: Barline glyph in markup

Hi, thank you for the suggestions! Attached the piece of notation that I would like to engraver, in a piece for piano solo. I was thinking about using two Staff contexts and a Dynamics context between the staves to put those repeat barline, better if vertically centered. Any other suggestions

Re: Barline glyph in markup

On 03/02/2023 10:50, Rip _Mus wrote: > Hi, > is it possible to use a repeat barline glyph(opened or closed) in a markup? > I'm trying to print it centered between two staves within a Dynamics context. > Thank you in advance! The two other answers work, but I wonder if th

Re: Barline glyph in markup

On Fri, 3 Feb 2023 at 15:03, Valentin Petzel wrote: > > Hi Rip_mus, > > Bar Lines are not in fact glyphs, but drawn directly. We could recreate a > drawing procedure for markups, but the easiest thing to do would probably be > to use the \score markup command for this as seen in the appended file.

Re: Barline glyph in markup

schrieb Rip _Mus: > Hi, > is it possible to use a repeat barline glyph(opened or closed) in a markup? > I'm trying to print it centered between two staves within a Dynamics > context. > Thank you in advance! > > Rip_mus #(define-markup-command (bar layout props type)

Barline glyph in markup

Hi, is it possible to use a repeat barline glyph(opened or closed) in a markup? I'm trying to print it centered between two staves within a Dynamics context. Thank you in advance! Rip_mus

Re: sustain to-barline? LP 2.24.0

nneth Wolcott > > > wrote: > > > > > > > > Hi; > > > > > > > > I decided to place my sustain pedal commands in the Dynamics > > > > Context; I hope that solves the problem. > > > > > > > > Thanks, >

Re: sustain to-barline? LP 2.24.0

> my sustain pedal commands in the Dynamics > > > Context; I hope that > solves the problem. > > > > > > Thanks, > > > Ken > > > > > > > On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcot

Re: sustain to-barline? LP 2.24.0

:50 PM Kenneth Wolcott > > wrote: > > > > > > Hi; > > > > > > I decided to place my sustain pedal commands in the Dynamics > > > Context; I hope that solves the problem. > > > > > > Thanks, > > > Ken > > > >

Re: sustain to-barline? LP 2.24.0

roblem. > > > > Thanks, > > Ken > > > > On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcott > > wrote: > > > > > > Hi; > > > > > > sustain to-barline? LP 2.24.0 > > > > > > I'd like to have the sustain pe

Re: sustain to-barline? LP 2.24.0

mands in the Dynamics > Context; I hope that solves the problem. > > Thanks, > Ken > > On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcott > wrote: > > > > Hi; > > > > sustain to-barline? LP 2.24.0 > > > > I'd like to have the sustain pedal term

Re: sustain to-barline? LP 2.24.0

Hi; I decided to place my sustain pedal commands in the Dynamics Context; I hope that solves the problem. Thanks, Ken On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcott wrote: > > Hi; > > sustain to-barline? LP 2.24.0 > > I'd like to have the sustain pedal terminate

sustain to-barline? LP 2.24.0

Hi; sustain to-barline? LP 2.24.0 I'd like to have the sustain pedal terminate at the bar line, not at the last note in the staff. Is there a "to-barline" setting for the sustain pedal? I searched for "to-barline" and found nothing regarding the sustain pedal.

Re: Missing end-of-stave barline?

will not print anything at the end of a bar, so you > should usually default to \bar "[|:-|" (single Bar line at end of line). > (The same holds true for ".|:" by the way!). > > Using \repeat, \section, \fine and such will automatically take care of > conste

Re: Missing end-of-stave barline?

e same holds true for ".|:" by the way!). Using \repeat, \section, \fine and such will automatically take care of constellations such as barline-repeat or double repeats. Cheers, Valentin Am Montag, 9. Jänner 2023, 12:07:07 CET schrieb Mark Probert: > Thanks! > > -mark.

Re: Missing end-of-stave barline?

Thanks! -mark. On 9 Jan 2023 at 17:58:10, Jean Abou Samra wrote: > > > Le 9 janv. 2023 à 07:56, Mark Probert a écrit : > > Hi. > > When I run this snippet the barline at the end of first stave, which > I think should be a “||”, goes “missing” (there is no barline

Re: Missing end-of-stave barline?

> Le 9 janv. 2023 à 07:56, Mark Probert a écrit : > > Hi. > > When I run this snippet the barline at the end of first stave, which I think > should be a “||”, goes “missing” (there is no barline at all). > > Is there a correct way of setting the end of stave

Missing end-of-stave barline?

Hi. When I run this snippet the barline at the end of first stave, which I think should be a “||”, goes “missing” (there is no barline at all). Is there a correct way of setting the end of stave barline in this kind of situation? %% —— \version "2.24" parta = { aes4 bes c d |

Re: Align markdown to barline?

lak wrote: >> Hi list, >> >> Is there a way to (easily) attach a text to a barline? Currently I am doing >> this kind of a stunt in order to line it up correctly: >> >> >> left = { >> \relative c { >> \clef bass >> c1_

Re: Align markdown to barline?

On 11/19/22 11:34 PM, Kenneth Flak wrote: Hi list, Is there a way to (easily) attach a text to a barline? Currently I am doing this kind of a stunt in order to line it up correctly: left = { \relative c { \clef bass c1_"C" d_"P" f_

Align markdown to barline?

Hi list, Is there a way to (easily) attach a text to a barline? Currently I am doing this kind of a stunt in order to line it up correctly: left = { \relative c { \clef bass c1_"C" d_"P" f_" C" e_" C" f_&

Re: Custom scheme engraver (Barline) problem

   ; The bar-text is for regular bar numbers and the bar-span is for > > spanning > >       ; bar number - i.e., "centered" bar numbers. Default values we can > > just > >       ; mark as empty lists to make error checking easier. (with null?) > >       (bar-text

Re: Custom scheme engraver (Barline) problem

rror checking easier. (with null?) > (bar-text '()) > (bar-span '()) > ; The next set of variables are just used for internal state. > (considered-numbering #f) ; flag to mark if we have already processed > this barline > (saw-bar-line #t)

Custom scheme engraver (Barline) problem

if we have already processed this barline       (saw-bar-line #t)         ; flag to set when we see a barline. This makes it                                 ; so the same barline isn't processed multiple times.                                 ; although the

Re: Code pointer from end-BarLine to previous NoteHead.?

Le 19/07/2022 à 15:00, David Kastrup a écrit : Jean Abou Samra writes: Meanwhile, like Lukas, I have been unashamedly switching back to 2.22 when I wished a better diagnostic. This is what we advise most users to use, so I'm not bothered. The issue is marked as a regression, so it will have to

Re: Code pointer from end-BarLine to previous NoteHead.?

Jean Abou Samra writes: > Meanwhile, like Lukas, I have been unashamedly switching > back to 2.22 when I wished a better diagnostic. This is > what we advise most users to use, so I'm not bothered. > The issue is marked as a regression, so it will have to > be fixed before we release the next sta

Re: Code pointer from end-BarLine to previous NoteHead.?

Le 18/07/2022 à 19:28, Thomas Morley a écrit : Am Mo., 18. Juli 2022 um 18:43 Uhr schrieb Lukas-Fabian Moser : I regularly switch back to old Guile v1.8 LilyPond versions (that's very easy in Frescobaldi) if my Scheme code gets to complicated for me - this happens quite often :-) - and I want t

Re: Code pointer from end-BarLine to previous NoteHead.?

Le 18/07/2022 à 18:43, Lukas-Fabian Moser a écrit : Forgive me for piping up: I'm not able to say what happened, I'm not able to debug because of that unhelpful (oh, I'm very polite this evening) guile messages, see the other thread. I'm overtired like hell, close to trashing the whole proje

Re: Code pointer from end-BarLine to previous NoteHead.?

Thomas Morley writes: > I will not vanish from the list/project in the foreseeable future, > unless hit by bus... > > Though in my humble opinion meaningful error messages are the most > pressing issue and I don't see I could do anything to improve the > situation. > That is frustrating, furtherm

Re: Code pointer from end-BarLine to previous NoteHead.?

Am Mo., 18. Juli 2022 um 18:43 Uhr schrieb Lukas-Fabian Moser : > > Forgive me for piping up: > > I'm not able to say what happened, I'm not able to debug because of > > that unhelpful (oh, I'm very polite this evening) guile messages, see > > the other thread. > > > > I'm overtired like hell, clos

Re: Code pointer from end-BarLine to previous NoteHead.?

Forgive me for piping up: I'm not able to say what happened, I'm not able to debug because of that unhelpful (oh, I'm very polite this evening) guile messages, see the other thread. I'm overtired like hell, close to trashing the whole project, and close to advertising everyone to not use LilyPon

Re: Code pointer from end-BarLine to previous NoteHead.?

Jean Abou Samra writes: > Le 18/07/2022 à 00:59, David Kastrup a écrit : >> Harm is not a C programmer either. Scheme is his only language and he >> learnt it because of LilyPond. So he has no exposure to the low-level >> nature of C++, nor to the basics of imperative programming languages >> t

Re: Code pointer from end-BarLine to previous NoteHead.?

Le 18/07/2022 à 00:59, David Kastrup a écrit : Harm is not a C programmer either. Scheme is his only language and he learnt it because of LilyPond. So he has no exposure to the low-level nature of C++, nor to the basics of imperative programming languages that are sort of a required firm footin

Re: Code pointer from end-BarLine to previous NoteHead.?

Jean Abou Samra writes: > Le 18/07/2022 à 00:44, David Kastrup a écrit : >> Jean Abou Samra writes: >> >> [Harm:] >> >> You are aware that you are not talking to a C++ programmer? Not exactly >> a motivating message under the circumstances... > > > > I learnt C++ (like many things) by pretendin

  1   2   3   4   5   6   7   8   9   10   >