Re: Combining drum parts

Am Fr., 4. Okt. 2024 um 19:37 Uhr schrieb Cameron Hall : > > I'd like to have separate drum parts for readability purposes but > combine them into one staff on the conductor's score. To my surprise, > the partCombine function does not work at all for drum parts, so I've > resulted to just combining

Re: Changing the shape of a tie in a chord

Am Mo., 30. Sept. 2024 um 22:57 Uhr schrieb Knute Snortum : > > How do you change the shape of a tie that's in a chord? In the following > example, neither \shape command has any effect. > > %%% > \version "2.24.4" > > tieShapeA = \shape #'((0 . 0) (0 . -1) (0 . -1) (0 . 0)) \etc > tieShapeB = \s

Re: weird error writing a tablature which uses a custom tuning

Am Do., 26. Sept. 2024 um 01:46 Uhr schrieb Thomas Morley : > > Am Di., 24. Sept. 2024 um 09:11 Uhr schrieb Thomas Morley > : > > > > Am Di., 24. Sept. 2024 um 01:04 Uhr schrieb Federico Bruni > > : > > > > > > Hi folks > > > > > >

Re: weird error writing a tablature which uses a custom tuning

Am Di., 24. Sept. 2024 um 09:11 Uhr schrieb Thomas Morley : > > Am Di., 24. Sept. 2024 um 01:04 Uhr schrieb Federico Bruni > : > > > > Hi folks > > > > I've just come across a really weird error. > > I'll try to make a minimal example tomorrow,

Re: weird error writing a tablature which uses a custom tuning

urrent/scm/lily/tablature.scm: >205:36 3 (tab-note-head::handle-ties #) > In unknown file: >2 (ly:item-break-dir ()) > In ice-9/boot-9.scm: > 1676:22 1 (raise-exception _ #:continuable? _) > In unknown file: >0 (apply-smob/1 # #<&comp?>) > I

Re: 2.25.19: segmentation fault

Am Di., 17. Sept. 2024 um 15:42 Uhr schrieb Trevor Bača : > > Hi, > > Calling 2.25.19 (under macOS ARM) on the attached file causes a > segmentation fault. > > The file is large, and a bit of a mess. But the segmentation fault reliably > happens every time 2.25.19 attempts to interpret the file. >

Re: issue with duration-lines from tied notes

Am Mi., 11. Sept. 2024 um 06:17 Uhr schrieb Matthew Burns : > > Hi Everyone, > > Thanks to everyon for this mailing list, I've been reading for a while > and it's lovely to have a place to see things I haven't found! > > I'm currently having some issues with Duration lines, and I thought > I'd shar

Re: TabStaff String Bend + Tie/Ghost Notes

Am Do., 15. Aug. 2024 um 16:13 Uhr schrieb Thomas Morley < thomasmorle...@gmail.com>: > > Hi, >> >> attached you'll find my attempt to create a style-sheet. >> Please holler for all I misunderstood or forgot or for bugs. >> >> Cheers, >> Har

Re: TabStaff String Bend + Tie/Ghost Notes

Am Do., 15. Aug. 2024 um 16:11 Uhr schrieb Thomas Morley < thomasmorle...@gmail.com>: > > > Am Di., 13. Aug. 2024 um 18:04 Uhr schrieb Lucas Cavalcanti < > lucaspi...@gmail.com>: > >> Hello! I'm having a bit of trouble trying to replicate this behaviour >

Re: TabStaff String Bend + Tie/Ghost Notes

Am Di., 13. Aug. 2024 um 18:04 Uhr schrieb Lucas Cavalcanti < lucaspi...@gmail.com>: > Hello! I'm having a bit of trouble trying to replicate this behaviour with > string bending and ties: > [image: GuitarProStringBends] > A bit of context: I'm a long time GuitarPro user and now I am fully > migra

Re: Multi Measure Rests in Tab Staff

Am Mo., 12. Aug. 2024 um 13:32 Uhr schrieb Richard Shann : > > If I have Multi Measure Rests in a Tab score empty bars result. > I've tried including the Multi_measure_rest_engraver but to no avail: > > 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< > \version "2.24" > music = { > \compressEmp

Re: TupletBrackets edge thickness

Am Mo., 12. Aug. 2024 um 13:44 Uhr schrieb Karim Haddad : > Sorry to bother you again with this. Your solution works like a charm. > However, apparently in the case of a reduced magstep of a Staff it ceases to > work. Any idea? > I am joining the example here PTAL Cheers, Harm \version "2.24

Re: TupletBrackets edge thickness

Am Mo., 12. Aug. 2024 um 12:53 Uhr schrieb haddad : > Although this is not an imortant feature, ie just esthetic and not that > standard, it would be great to have implemented the controls of these > edges in the tupletbracket properties. You could open an issue as feature-request at GitLab ;) ht

Re: TupletBrackets edge thickness

Am Sa., 10. Aug. 2024 um 19:11 Uhr schrieb Lukas-Fabian Moser : > Hi Kieren, > > Left to do: We probably also should modify the extents of the resulting > stencil to avoid collisions... > > If the thickness of the edge lines are expanded *inwards*, wouldn’t the > original extent still be accurat

Re: guitar slides snippets in the LSR

Am Mo., 5. Aug. 2024 um 22:20 Uhr schrieb Federico Bruni : > > Il giorno lun 5 ago 2024 alle 09:39:54 +02:00:00, Thomas Morley > ha scritto: > > Is this about the doc-tagged https://lsr.di.unimi.it/LSR/Item?id=803 ? > > Isn't it more that StringNumber _may_ be needed

Re: Multiple fingering and glides

Am Di., 6. Aug. 2024 um 05:14 Uhr schrieb Fennel : > > Multiple fingerings are being used because I'm working on a heavily annotated > edition of a work that suggests multiple sets of fingerings for a single > passage. To summarize, alternative fingerings, right? > I'm currently choosing to eng

Re: multiple pluck fingering on single note?

Am Di., 6. Aug. 2024 um 14:38 Uhr schrieb Werner LEMBERG : > > > >> this is a question addressed mainly to guitar players: Is it > >> possible to have more than a single pluck fingering attached to a > >> note (for tremolo or similar things)? I've looked around a bit but > >> couldn't find an answ

Re: multiple pluck fingering on single note?

Am Di., 6. Aug. 2024 um 13:49 Uhr schrieb Werner LEMBERG : > > > Folks, > > > this is a question addressed mainly to guitar players: Is it possible > to have more than a single pluck fingering attached to a note (for > tremolo or similar things)? I've looked around a bit but couldn't > find an ans

Re: guitar slides snippets in the LSR

Am Mo., 5. Aug. 2024 um 05:49 Uhr schrieb Federico Bruni via bug-lilypond : > > Hi folks > > This was reported 10 years ago: > https://lists.nongnu.org/archive/html/bug-lilypond/2014-02/msg00326.html > > Now the string numbers have been removed, but there's still a sentence > to be removed: > > "St

Re: Multiple fingering and glides

Am Fr., 2. Aug. 2024 um 05:42 Uhr schrieb Werner LEMBERG : > > > > I'm working on a project that involves multiple fingerings for each > > note, and shift lines or glides between some notes. [...] > > Hopefully Harm has some time to help here since he is the original > author of the fingering glid

Re: search for better regtest comparison algorithm

Am Sa., 27. Juli 2024 um 18:56 Uhr schrieb Werner LEMBERG : > > > I've posted a question on StackExchange, searching for a better > regtest comparison algorithm > > > https://computergraphics.stackexchange.com/questions/14143/search-for-special-image-difference-metric > > > Werner > We also

Re: Improbable offset for stencil

‪Am Fr., 26. Juli 2024 um 13:17 Uhr schrieb ‫Yotam Medini יותם מדיני‬‎ :‬ > > Hello Thomas, > Thank you for the merge request. > In https://gitlab.com/lilypond/lilypond/-/merge_requests/2386 it says it > "must be rebased," > -- yotam Sure. Once the count-down-circle is set to patch-push, I'll reb

Re: Tempo changes and spanners

Am Di., 23. Juli 2024 um 23:52 Uhr schrieb Tom Brennan : > > Hi all > > I'm notating a sonata for a cello and piano, and I would like to produce > three "artifacts" (products?) from this: > > 1. A solo cello part (a typical single staff representation) > 2. A "study score" where all staves are equ

Re: Improbable offset for stencil

‪Am Sa., 20. Juli 2024 um 11:34 Uhr schrieb ‫Yotam Medini יותם מדיני‬‎ :‬ > > Werner & Jean - thanks to both of you for your explanations. > > Since debugging and understanding Scheme/Guile code > is beyond my current capabilities, I will not be able to provide > a correct fix for footer placement.

Re: 'cloning' Voice properties

Am Mi., 17. Juli 2024 um 11:02 Uhr schrieb Werner LEMBERG : > > > >> ``` > >> \version "2.25.18" > >> > >> foo = > >> #(define-music-function () () > >> #{ > >> << > >> c'4 > >> \new Voice { g''4 } > >> >> > >> #}) > >> > >> { > >> \override Staff.NoteColumn.ignore-collisio

Re: 'cloning' Voice properties

Am So., 14. Juli 2024 um 18:38 Uhr schrieb Werner LEMBERG : > > > Folks, > > > consider the following snippet. > > > ``` > \version "2.25.18" > > foo = > #(define-music-function () () > #{ > << > c'4 > \new Voice { g''4 } > >> > #}) > > { > \override Staff.NoteColumn.ignore

Re: Thoughts on next stable release(s)

Am So., 16. Juni 2024 um 22:24 Uhr schrieb Jonas Hahnfeld via Discussions on LilyPond development : > > Hi all, > > it's been 7 months since the last stable (bugfix) release, LilyPond > 2.24.3. Today I went through the list of all (smaller) merge requests > and marked those that we might want to ap

Re: Workaround for \grace + \tuplet bug

Am Mo., 8. Juli 2024 um 18:09 Uhr schrieb Tom Brennan : > > I just realized that guile 3 is available for 2.24.x, so that's the > workaround. I'll still file the bug, though, for v2.25 in the proper channel. > > Thanks > Tom > > On Mon, Jul 8, 2024 at 11:40 AM Tom Brennan wrote: >> >> Hi all >> >

Re: TrillPitch* whiteout bug

Am Do., 27. Juni 2024 um 17:05 Uhr schrieb Trevor Bača : > > Hi, > > Here is a two-staff example with a bug relating to the way that whiteout > works with TrillPitchAccidental, TrillPitchHead, TrilPitchParentheses; the > parenthesized pitched-trill fails to print, leaving behind some type of > visu

Re: Graphical markup between objects?

Am So., 23. Juni 2024 um 19:48 Uhr schrieb Fennel : > > > Wondering if it's possible to override the behavior of the glide line such > that the glide will draw to the next fingering regardless of what the second > number is. > > - Fennel It's not possible. Think of chords with multiple fingering

Re: Conditional code in the midi block

Am So., 19. Mai 2024 um 21:28 Uhr schrieb Carolyn Beeton : > > I would like to include some Staff and Voice context settings in the \midi > block only if a flag is set to ##t and I have not been able to figure out how > to do this. When I try to wrap the \context blocks in a code block with > #

New LSR snippet 1187 "New pitch language"

To the author of the new LSR snippet 1187 "New pitch language" https://lsr.di.unimi.it/LSR/Item?u=1&id=1187 You add your new language to "nederlands", thus \language "alpha" returns a warning: warning: Could not find language `alpha'. Ignoring. Please fix or delete that line. Furthermore, I thin

Re: Empty chord construct and \break.

tremendously. Thank you so much!!! >> >> Hwaen Ch'uqi >> >> >> On Sun, Apr 28, 2024 at 7:24 AM Thomas Morley >> wrote: >>> >>> Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi >>> : >>> > >>> > Gr

Re: Empty chord construct and \break.

Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi : > > Greetings, > > I am trying to typeset a stack of spoken lines above a multimeasure rest. > This works fine when preceded by notes in the same system. However, when it > follows a forced break, the output is not so desirable. Can anyone

Re: Special notation question

Am So., 21. Apr. 2024 um 17:43 Uhr schrieb Xavier Mayeur : > Hello, > > In a \time 3/2 score, how can I write the following snippet in Lilypond? > > > > I wonder how to create the 'g' note with that special appearance and with > the right duration... > > -- > Cordialement, > > Xavier MAYEUR > Brux

Re: Multiple parts on the same stems

Am Di., 16. Apr. 2024 um 22:01 Uhr schrieb Gerardo Ballabio : > > Hello all, > I'm trying to typeset a percussion score with several instruments on > the same staff. When they play simultaneous notes I want to line them > up all on the same stem, like this (output attached, percussion1.pdf): > > %%

Re: Delayed turns etc

Am Mi., 17. Apr. 2024 um 11:13 Uhr schrieb Jean Abou Samra : > > That works for the last line of the whole score. The line I want to be > "ragged" is the last line of a page. with more music on the next page. > > > There is no way to make just one system ragged except the last one in the > score.

Re: make-music?

Am Sa., 13. Apr. 2024 um 22:09 Uhr schrieb Pierre-Luc Gauthier : > But what about the parenthesised alist -> (alist) ‽ > > I have not found documentation here : > https://extending-lilypond.gitlab.io/en/scheme/alists.html > nor here : > https://lilypond.org/doc/v2.25/Documentation/extending/associ

Re: make-music?

Am Sa., 13. Apr. 2024 um 20:59 Uhr schrieb Pierre-Luc Gauthier : > > Hello there, > > Quite an easy one I'm sure but I tried many combinations to no avail. > > I have this symbol that I wish to evaluate later. I thought that was > what ly:make-music was for. > > \version "2.25.15" > > #(define anAL

Re: Snippet 960 fails with Ly 2.25

Am Di., 2. Apr. 2024 um 00:21 Uhr schrieb K. Blum via bug-lilypond : > > Hello, > > LSR snippet 960 works alright with LilyPond 2.24.3 and earlier. > Ly 2.25.1 (and later) aborts with an error message, see below. > In the docs I haven't found any changes to the functions in use. > Also tried conver

Re: How to detect SpanBar from inside a make-bar-line definition?

Am Sa., 16. März 2024 um 14:59 Uhr schrieb Thomas Morley : > > Am Do., 14. März 2024 um 02:31 Uhr schrieb Dan Eble > : > > > > On 2024-03-13 20:09, Thomas Morley wrote: > > > I don't understand what you propose. > > > > My advice was

Re: How to detect SpanBar from inside a make-bar-line definition?

Am Do., 14. März 2024 um 02:31 Uhr schrieb Dan Eble : > > On 2024-03-13 20:09, Thomas Morley wrote: > > I don't understand what you propose. > > My advice was general software-design advice based on a hasty > consideration of your post, so I'm not really surpr

Re: How to detect SpanBar from inside a make-bar-line definition?

Am Mi., 13. März 2024 um 23:56 Uhr schrieb Dan Eble : > > On 2024-03-13 17:35, Thomas Morley wrote: > > > currently I'm attempting to improve dashed/dotted bar lines wrt to > > changed staff-space and span bars. > > We use both definitions for BarLine _a

How to detect SpanBar from inside a make-bar-line definition?

Hi, currently I'm attempting to improve dashed/dotted bar lines wrt to changed staff-space and span bars. We use both definitions for BarLine _and_ SpanBar, but then SpanBar is frequently a little off. It would be nice to have a possibility to detect whether a definition is used for span bars. But

Re: Volta spanner missing edge when using "|" as endRepeatType

Am Do., 29. Feb. 2024 um 07:53 Uhr schrieb Andy Bradford : > > Hello, > > I want to place an interlude that happens only the first time through a > a section that has a repeat and a second interlude for the second time > through. I don't want the repeat measure bar showing up in the middle of >

Re: Dashed bar lines fail requirements at some sizes

Hi, thanks for your report. Apart from the last point (see below), it's mostly caused by: commit cff90246a32186f450bab1f8cd415d320b8c0cf2 Author: Thomas Morley Date: Wed Oct 4 16:18:30 2023 +0200 Dashed bar lines do not stick out Give BarLine a little less, SpanBar a little

Re: \partial and \compressMMRests don't seem to work together

Am Sa., 17. Feb. 2024 um 01:18 Uhr schrieb Gerardo Ballabio : > > Sorry, forgot the attachment. > > Il giorno sab 17 feb 2024 alle ore 01:15 Gerardo Ballabio > ha scritto: > > > > Hello, > > I need to change the time in the middle of a bar. > > I managed to do that using \partial, but it seems tha

Re: Table of Contents and mixed numbers.

Am Do., 15. Feb. 2024 um 19:16 Uhr schrieb Hwaen Ch'uqi : > > Greetings, > > Until upgrading to 2.24, I had been using certain Scheme code and > \paper block layouts in order to output books consisting of prefatory > material with Roman numeral page numbers and the music itself with > Arabic page n

Re: toc, \with-link and `bookpart-level-page-numbering'

Am Sa., 17. Feb. 2024 um 18:47 Uhr schrieb Thomas Morley : > > Hi, > > please consider the following code: > > \version "2.25.13" > > \paper { > print-first-page-number = ##t > bookpart-level-page-numbering = ##t > } > > \book { > \bookp

toc, \with-link and `bookpart-level-page-numbering'

Hi, please consider the following code: \version "2.25.13" \paper { print-first-page-number = ##t bookpart-level-page-numbering = ##t } \book { \bookpart { \markuplist \table-of-contents } \bookpart { \paper { page-number-type = #'roman-upper } \tocItem \markup "Text" \marku

Re: RFC and help at MR 2256

Am Mo., 12. Feb. 2024 um 12:37 Uhr schrieb Jean Abou Samra : > > > It prints > > backtrace: > 0: AgogicLineSpanner.Y-offset (# ly:side-position-interface::y-aligned-side (_ #:optional _)>) > 1: AgogicLineSpanner.vertical-skylines (# ly:grob::vertical-skylines-from-element-stencils (_)>) > 2: Ver

Re: RFC and help at MR 2256

Am So., 11. Feb. 2024 um 13:51 Uhr schrieb Jean Abou Samra : > > > Alas, as soon as the relevant engravers are moved to another context, > > which is a common use case, I get an error: > > > > programming error: cyclic dependency: calculation-in-progress > > encountered for AgogicLineSpanner.vertic

RFC and help at MR 2256

Hi, https://gitlab.com/lilypond/lilypond/-/merge_requests/2256 attempts to solve https://gitlab.com/lilypond/lilypond/-/issues/3176 by introducing AgogicMark, AgogicSpanner and AgogicLineSpanner at score-level. It all mimics how DynamicLineSpanner collects and aligns dynamic stuff. So far all work

Re: Melody bars are out of sync after tie into first alternative and added lyrics

Am Sa., 27. Jan. 2024 um 12:14 Uhr schrieb Arne Ploese via bug-lilypond : > > Here you can find a > preview: > https://www.schott-music.com/de/preview/viewer/index/?idx=NTI0Mjcx&idy=524271&dl=0 > > Voice tenor bar 9 to 10 into first alternative it is bound, were as > from bar 9 to 13 (page 2) it i

Re: Is there a property that would set all of the "above staff" text to "above chordnames"

Am Mo., 1. Jan. 2024 um 21:59 Uhr schrieb : > > On Mon, 1 Jan 2024, Kevin Cole wrote: > > > What I mean is, I often have a situation where there's only a wee bit > > o' text occasionally, above the staff. But I frequently have > > ChordNames. It seems to me that the ChordNames would be better place

Problems while defining an aligning mark-spanner

Hi, please have a look at the code below. It is an attempt to implement an aligning spanner between certain marks at score-level. Here I use TextMark and a newly defined TextMarkSpanner-grob. Currently the TextNarks are moved, which is nice. Though, it relies on the highest element in the Staff,

Re: FingerGlideSpanner disappears if listened

Am Mo., 25. Dez. 2023 um 20:55 Uhr schrieb David Kastrup : > > Jean Abou Samra writes: > > > Probably related to the code and comment in lily/rhythmic-music-iterator.cc. > > Probably. Articulation events with a listener are removed (and > separately broadcast) from the articulations on a non-chor

FingerGlideSpanner disappears if listened

Hi, please consider: mus = { b-\glide -1 b-1 } << \new Voice \mus \new Voice \with { \consists #(lambda (ctx) (make-engraver (listeners ((finger-glide-event this-engraver event) '() } \mus >> With most recent master out of c3f2dddaa2b

Re: Doc-problem with new markup-command

Am Do., 23. Nov. 2023 um 11:53 Uhr schrieb Jean Abou Samra : > > > > Now m̀ake' fails. > > Offending line in the doc-string is > > The input-string @var{strg} may be composed by any string of \";|.:![]{}\". > > Obviously the braces, { and }, need to be escaped. > > How to? > > > Like this I think:

Re: Doc-problem with new markup-command

Am Do., 23. Nov. 2023 um 10:49 Uhr schrieb Thomas Morley : > > Am Do., 23. Nov. 2023 um 10:40 Uhr schrieb Jean Abou Samra > : > > > > > Ok. > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2179 > > > > Oh, I see. You forgot to give it a #

Re: Doc-problem with new markup-command

Am Do., 23. Nov. 2023 um 10:40 Uhr schrieb Jean Abou Samra : > > > Ok. > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2179 > > Oh, I see. You forgot to give it a #:category . Thanks for the hint. Would it make sense to warn if #:category is omitted? Corrected patch is up. Thanks, Har

Re: Doc-problem with new markup-command

Am Do., 23. Nov. 2023 um 10:23 Uhr schrieb Jean Abou Samra : > > Is this a doc build from scratch or an incremental rebuild? >From scratch. > I'd suggest opening the MR anyway. Ok. https://gitlab.com/lilypond/lilypond/-/merge_requests/2179

Doc-problem with new markup-command

Hi, I'm working on #3164 "add a `\bar-line` markup function" and thought the patch is ready to upload for review, i.e. the new bar-line-markup-command works as I think it should, `make check' (with a new regtest) returns as expected. `make doc' succeds without errors. Alas, the new markup-command

Re: programming error: Improbable offset for stencil: -inf staff space,Setting to zero.

Am So., 19. Nov. 2023 um 15:30 Uhr schrieb Michael Gerdau : > > Hi lilyponders! > > the attached fairly short script creates 4x the aforementioned error. It > seems to be created by the combined >\tweak Parentheses.font-size #2 \parenthesize > > The resulting score looks basically fine (AFAICT)

Re: LilyPond 2.25.10

Am Fr., 17. Nov. 2023 um 21:33 Uhr schrieb Michael Gerdau : > > >>> I will try to create a MWE if that is required to track down the > >>> problem. > >> > >> > >> A *minimal* example is not strictly required (though helpful), but > >> *some* example is — otherwise, there is nothing we can do, sorry

Re: Multiple clefs in one Staff

Am Fr., 27. Okt. 2023 um 11:29 Uhr schrieb Werner LEMBERG : > > > > Inspired by > > > > > > Should we be offering something like that? > > What exactly do you mean with 'offering'? > > Having thi

Re: programming error: note-column has no direction

ere is any reason for not engraving the stems, but if there > isn’t I’d say the latter one is the more stable path. > > Cheers, > Valentin > > Am Samstag, 7. Oktober 2023, 10:35:20 CEST schrieb Thomas Morley: > > Hi, > > > > this came up in the german

programming error: note-column has no direction

Hi, this came up in the german forum: https://lilypondforum.de/index.php/topic,1280.msg6613.html A more minimel example: \version "2.24.2" %% \include "gregorian.ly" %% %% \layout { %% \context { %% \GregorianTranscriptionVoice %% \consists Stem_engraver %% \omit Stem %% } %% }

Re: Question about condensed score

Am Fr., 18. Aug. 2023 um 21:51 Uhr schrieb David Kastrup : > > Rip _Mus writes: > > > Hello, > > does anyone happen to have an answer? > > I just can't understand this behavior... > > > > Thank you > > > > Il mer 16 ago 2023, 08:18 Rip _Mus ha > > scritto: > > > >> Good morning everyone, > >> goi

Re: A query about tablature

Am Di., 8. Aug. 2023 um 11:14 Uhr schrieb Lukas-Fabian Moser : > > Hi Alasdair, > > > Thank you very much - that is quite amazing! > You're very welcome. > > But it does show what I have long suspected: that without some extra > > programming, Lilypond does not have a current facility to extract th

Re: Retrieve context properties

Am So., 23. Juli 2023 um 10:03 Uhr schrieb Rip _Mus : > > Thank you Valentin, > this is very helpful! > The situation is that I always create a custom context, named "Tactus", that > creates bars for proportional notation (it's a Dynamics alias, that accepts > Voice and some overrides, transparen

Re: In-staff fermata with 2.25.

Hi Jean, Am Mi., 7. Juni 2023 um 23:31 Uhr schrieb Jean Abou Samra : > > Le mercredi 07 juin 2023 à 23:07 +0200, Thomas Morley a écrit : > > Hi, > > this came up in the german forum: > https://lilypondforum.de/index.php/topic,1247.msg6512.html > > How to print f

In-staff fermata with 2.25.

Hi, this came up in the german forum: https://lilypondforum.de/index.php/topic,1247.msg6512.html How to print fermata _in_ staff with 2.25.? Below works with 2.24. \version "2.24.1" %#(ly:set-option 'debug-skylines #t) \layout { \override Score.VerticalAxisGroup.default-staff-staff-spacing.b

Re: LSR #983 produces strange result

Am So., 23. Apr. 2023 um 09:33 Uhr schrieb Thomas Morley : > > Am So., 23. Apr. 2023 um 07:45 Uhr schrieb Werner LEMBERG : > > > > > > Please have a look at > > > > https://lsr.di.unimi.it/LSR/Item?id=983 > > > > This code has obviously worked som

Re: Circular staves

Am So., 23. Apr. 2023 um 04:38 Uhr schrieb Andrew Bernard : > > Just checking - you can't make circular staves with notes in lilypond, > can you? I know you can do nice circle of fifths diagrams as per an LSR > example, but circular staves are way out of scope, aren't they? > > This came up in the

Re: LSR #983 produces strange result

Am So., 23. Apr. 2023 um 07:45 Uhr schrieb Werner LEMBERG : > > > Please have a look at > > https://lsr.di.unimi.it/LSR/Item?id=983 > > This code has obviously worked some time before, but it no longer > doesn't. Is this a problem with the code or a bug? > > > Werner > Fixed inside LSR by r

Re: Bounding box for rotated markup

Am So., 9. Apr. 2023 um 12:16 Uhr schrieb Jean Abou Samra : > > > > > Le 9 avr. 2023 à 10:50, Thomas Morley a écrit : > > > > Hi, > > > > please consider following code: > > > > pol = \markup \polygon #'((0 . 2) (10 . 0) (10 . 20) (0 . 22

Bounding box for rotated markup

Hi, please consider following code: pol = \markup \polygon #'((0 . 2) (10 . 0) (10 . 20) (0 . 22)) \markup \override #'(box-padding . 0) \box { \pol \rotate #45 \pol } See attached image. How to get \box tight to the rotated polygon? Thanks, Harm

Re: Programming error with change staff

Am Do., 16. Feb. 2023 um 19:09 Uhr schrieb Knute Snortum : > > I have run into a situation where LilyPond produces a programming error. It > involves changing staff, voice one, accent fingering and avoid-slur. It's > best to just look at the MWE: > > \version "2.25.1" > > staffUp = \change Staf

Re: 2.25.1 bug

Am Di., 14. Feb. 2023 um 22:06 Uhr schrieb Jean Abou Samra : > > Le mardi 14 février 2023 à 19:55 +0100, Craig Fearing a écrit : > > The attached file is a minimized version of an official snippet. > > > > If run as version 2.25.*0* it compiles perfectly. > > > > If run as version 2.25.*1* it fails

Re: Error in Extending Lilypond example

Am Mi., 1. Feb. 2023 um 04:16 Uhr schrieb Saul Tobin : > > The fourth example engraver here: > https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example > > Running this code in 2.24 crashes on initializing the engraver with In > procedure ly:spanner-set

Re: Error in Extending Lilypond example

Am Mi., 1. Feb. 2023 um 04:16 Uhr schrieb Saul Tobin : > > The fourth example engraver here: > https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example > > Running this code in 2.24 crashes on initializing the engraver with In > procedure ly:spanner-set

Re: Custom percussion style is ignored for the first note when it is a grace note

Am Mi., 25. Jan. 2023 um 17:54 Uhr schrieb David Kastrup : > > Stu McKenzie writes: > > > There seems to have been various reports of bugs when the first note > > is a grace note, but this bug has been in many LilyPond versions to > > date. > > > > When the first note of a drum score has a grace n

Re: Completion_heads_engraver for line-ends only?

Am Di., 17. Jan. 2023 um 18:32 Uhr schrieb Graham King : > > I'm preparing an edition of de Wert's motet "Ascendente Jesu in naviculam" > which has an extended stretto section with dotted rhythms across barlines. > For this, Harm's Mensurstriche example in the Learning Manual produces a > mostl

Re: Resize \rhythm in mixed markup

Am Di., 10. Jan. 2023 um 02:44 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am So., 8. Jan. 2023 um 10:21 Uhr schrieb Thomas Morley > > : > >> > >> Hi, > >> > >> consider below > >> > >> \version

Re: Resize \rhythm in mixed markup

Am So., 8. Jan. 2023 um 11:13 Uhr schrieb Thomas Morley : > > Am So., 8. Jan. 2023 um 10:21 Uhr schrieb Thomas Morley > : > > > > Hi, > > > > consider below > > > > \version "2.24.0" > > > > \score { > > { g

Re: Resize \rhythm in mixed markup

Am So., 8. Jan. 2023 um 10:21 Uhr schrieb Thomas Morley : > > Hi, > > consider below > > \version "2.24.0" > > \score { > { g'1^\markup { My Rhythm \rhythm { 8[ 8] } } } > \layout { > \context { > \StandaloneRhythmStaff >

Resize \rhythm in mixed markup

Hi, consider below \version "2.24.0" \score { { g'1^\markup { My Rhythm \rhythm { 8[ 8] } } } \layout { \context { \StandaloneRhythmStaff fontSize = #6 } } } I'll have numerous such markups combining straight text and \rhythm. Thus I'd like to have a method to adjust t

Re: LSR update?

Am Mi., 28. Dez. 2022 um 07:17 Uhr schrieb Werner LEMBERG : > > > > Lateron, when LSR runs 2.24.0, we need to insert all snippets from > > /Documentation/snippets/new. Done. > > As final step we need to delete the ones from > > /Documentation/snippets/new and commit the new state, I would be > >

Re: Missing items to make Cairo ready

Am Fr., 6. Jan. 2023 um 14:26 Uhr schrieb Jonas Hahnfeld via Discussions on LilyPond development : > > On Fri, 2023-01-06 at 14:21 +0100, Jean Abou Samra wrote: > > Le 06/01/2023 à 10:19, Jonas Hahnfeld a écrit : > > I don't see any markup commands other than \postscript > > and \epsfile that we c

programming error in doc-snippet

Hi, with 2.25.0 /Documentation/snippets/new/ancient-notation-templatemodern-transcription-of-gregorian-music.ly emits: programming error: no stem for note column Cheers, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.or

Re: Unbreakable space in texinfo and html

Am Mo., 2. Jan. 2023 um 13:30 Uhr schrieb Werner LEMBERG : > > > > Here the next one: What's html for @@code@{TupletBracket@} > > ? > > Are you talking about > `it/texidocs/controlling-tuplet-bracket-visibility.texidoc`? There, > `@@code@{TupletBracket@}` is wrong; it should be > `@code{TupletBrac

Re: Unbreakable space in texinfo and html

Am Mo., 2. Jan. 2023 um 13:23 Uhr schrieb Werner LEMBERG : > > > > > I could do (in the description) > > > > (1) fa > > (2) ‘fa’ > > (3) 'fa' > > > > What do you recommend? > > Assuming that people are going to translate this I would do (1). > > > Werner Thanks, done. Harm

Re: LSR update?

Am Mo., 2. Jan. 2023 um 13:33 Uhr schrieb Werner LEMBERG : > > > >> Ideally, there would be a git repository to which we can actually > >> push the new files (to retain the editing history), and a script > >> that regenerates the database automatically – and vice versa. > > > > Werner, actually it'

Re: LSR update?

Am Mi., 28. Dez. 2022 um 07:17 Uhr schrieb Werner LEMBERG : > > > > Lateron, when LSR runs 2.24.0, we need to insert all snippets from > > /Documentation/snippets/new. This is tedious, any help would be > > great. > > Sebastiano, if we send you an archive with all updated snippets: Do > you have a

Re: Unbreakable space in texinfo and html

Am So., 1. Jan. 2023 um 22:24 Uhr schrieb Aaron Hill : > > On 2023-01-01 11:21 am, Thomas Morley wrote: > > May I ask further: > > What are the html equivalents of @qq{…} and @q{…}? > > If you are looking for HTML entities, there are several online resources > (such as

Re: Unbreakable space in texinfo and html

Am So., 1. Jan. 2023 um 23:58 Uhr schrieb Werner LEMBERG : > > > > What are the html equivalents of @qq{…} and @q{…}? > > There is no stand-alone equivalent to `@q`. If you write > > ``` > foo > ``` > > it gets converted by `pandoc` to > > ``` > ``foo'' > ``` > > which `makelsr.pl` in turn convert

Re: Unbreakable space in texinfo and html

Happy new year as well!! Am So., 1. Jan. 2023 um 19:12 Uhr schrieb Werner LEMBERG : > > > Hallo Harm, > > > a Happy New Year to you and all other LilyPonders! > > > > In our doc-strings we sometimes have @tie{} to get an unbreakable > > space. As lsr-editor I need similar for html. Is   the > >

Unbreakable space in texinfo and html

In our doc-strings we sometimes have @tie{} to get an unbreakable space. As lsr-editor I need similar for html. Is   the correct equivalent? Will   correctly be transformed to @tie{} if lsr-snippets are imported? Thanks, Harm

Re: LSR update?

Am So., 1. Jan. 2023 um 11:52 Uhr schrieb Jean Abou Samra : > > Le 31/12/2022 à 21:15, Thomas Morley a écrit : > > Today I found some time :) > > > > lilypond *.ly on all lsr-snippets fails because of the following snippets: > >custom-tuning-and-midi-rendering.l

  1   2   3   4   5   6   7   8   9   10   >