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 gener

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 surprised. >

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 _and

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.

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"

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:

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

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

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

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

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

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,

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

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

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 worke

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

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

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 >

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

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

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

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

Re: LSR update?

Am Di., 27. Dez. 2022 um 16:55 Uhr schrieb Thomas Morley : > > Am Di., 27. Dez. 2022 um 15:24 Uhr schrieb Jean Abou Samra > : > > > > Le 27/12/2022 à 15:06, Thomas Morley a écrit : > > > (3) > > > It's not possible to do > > > lilypond *.ly > &

Re: Strange behaviour with unknown alternativeNumberingStyle

Meanwhile I created https://gitlab.com/lilypond/lilypond/-/issues/6507 Am Sa., 31. Dez. 2022 um 19:01 Uhr schrieb Dan Eble : > > On Dec 30, 2022, at 12:10, Thomas Morley wrote: > > > > Hi all, > > > > please have a look at: > > > > \version "2.25.0&

Strange behaviour with unknown alternativeNumberingStyle

Hi all, please have a look at: \version "2.25.0" { \override Score.BarNumber.break-visibility = ##(#f #t #t) % \set Score.alternativeNumberingStyle = #'whatever b1 \repeat volta 2 { c' c' } \alternative { d' e' } f' } As soon as the style-setting is uncommented it behaves like

Re: LSR update?

Am Di., 27. Dez. 2022 um 17:54 Uhr schrieb Jean Abou Samra : > > Le 27/12/2022 à 17:44, Thomas Morley a écrit : > > Here string-delete has one argument, a procedure. > > > No; check the parentheses again. > I did, several times - before I got it: My edit

Re: LSR update?

Am Di., 27. Dez. 2022 um 17:08 Uhr schrieb Jean Abou Samra : > > Le 27/12/2022 à 16:55, Thomas Morley a écrit : > > > > 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

Re: LSR update?

Am Di., 27. Dez. 2022 um 17:11 Uhr schrieb Jean Abou Samra : > > Le 27/12/2022 à 17:06, Thomas Morley a écrit : > >>>TODO guile message about `string-delete' > >>> > >>> adding-fingerings-or-string-numbers-or-stroke-fingerings-outside-of-the-mu

Re: LSR update?

Am Di., 27. Dez. 2022 um 15:24 Uhr schrieb Jean Abou Samra : > > Le 27/12/2022 à 15:06, Thomas Morley a écrit : > > Well, I started to update the snippets to 2.24.0 locally. > > Thank you for doing this. > > Do you intend to do them all, or do you need help? > > >

Re: LSR update?

Am Di., 27. Dez. 2022 um 15:24 Uhr schrieb Jean Abou Samra : > > Le 27/12/2022 à 15:06, Thomas Morley a écrit : > > Well, I started to update the snippets to 2.24.0 locally. > > Thank you for doing this. > > Do you intend to do them all, or do you need help? I'd vol

Re: Issue with deep-copy/map-some-music a tuplet

Am So., 25. Dez. 2022 um 18:18 Uhr schrieb Jean Abou Samra : > > > > > Le 25 déc. 2022 à 18:08, Paolo Prete a écrit : > > > >  > > Hello Jean, > > > > I just verified that 2.25 doesn't accept a tuplet of skips ( i.e: \tuplet > > 3/2 { s s s }, while all the previous versions do. > > Is this

Re: Issue with deep-copy/map-some-music a tuplet

Hi Paolo, the culprit is a non-breakable space character. Delete it. Am Sa., 24. Dez. 2022 um 20:20 Uhr schrieb Paolo Prete : > > Hello, > > I just noticed an inconsistent behavior with 2.25.0. The snippet below > doesn't compile; I don't know if there is a hidden problem inside it, but > it

Re: markup->string

Am So., 13. Nov. 2022 um 16:30 Uhr schrieb Jean Abou Samra : > > > > > Le 13 nov. 2022 à 16:22, Thomas Morley a écrit : > > > > Nevertheless, _if_ the old code is just (markup->string > > ), would it be possible to leave it untouched while > > running

Re: markup->string

Am So., 13. Nov. 2022 um 15:43 Uhr schrieb Jean Abou Samra : > > Le 13/11/2022 à 14:41, Thomas Morley a écrit : > > Hi, > > > > please consider below (originally for 2.20. _not_ converted): > > > > \version "2.23.80" > > > > \header

markup->string

Hi, please consider below (originally for 2.20. _not_ converted): \version "2.23.80" \header { myTitle = "myTitle" myOtherTitle = \markup { \italic \fromproperty #'header:myTitle } title = $(markup->string myOtherTitle) } \markup { "TEST" } A title is not printed. Though, I'm at loss,

Re: procedure to check equality of list-elements

Am So., 6. Nov. 2022 um 13:39 Uhr schrieb Jean Abou Samra : > > > > Le 06/11/2022 à 13:27, Thomas Morley a écrit : > > Ofcourse not, though you need to know that the chosen proc is suitable > > for the task. > > For me eqv? was always meant to work with

Re: procedure to check equality of list-elements

Am So., 6. Nov. 2022 um 13:39 Uhr schrieb Jean Abou Samra : > > > > Le 06/11/2022 à 13:27, Thomas Morley a écrit : > > Ofcourse not, though you need to know that the chosen proc is suitable > > for the task. > > For me eqv? was always meant to work with

Re: procedure to check equality of list-elements

Am So., 6. Nov. 2022 um 13:07 Uhr schrieb Jean Abou Samra : > > Le 06/11/2022 à 13:03, Thomas Morley a écrit : > > Hi, > > > > in !1701 `ly:beam::calc-knee' checks whether all list-elements are equal. > > Basically doing (apply eqv? ). > > Tbh, I don't under

procedure to check equality of list-elements

Hi, in !1701 `ly:beam::calc-knee' checks whether all list-elements are equal. Basically doing (apply eqv? ). Tbh, I don't understand why it works... Though, the need to check a list for all list-elements are equal happened to me not only once. Thus, would it be acceptable to add something like:

Re: Potential LSR licensing violations

Am Do., 20. Okt. 2022 um 21:30 Uhr schrieb Han-Wen Nienhuys : > > On Thu, Oct 20, 2022 at 2:34 AM Jean Abou Samra wrote: > > So far, so good. However, take this snippet: > > > > https://lsr.di.unimi.it/LSR/Item?id=102 > > > > It begins with 300 lines of code that used to be in the LilyPond > >

Re: Potential LSR licensing violations

Am Do., 20. Okt. 2022 um 02:34 Uhr schrieb Jean Abou Samra : > I figured that now I am an LSR editor, I had to learn about what > legal responsibility I have when accepting contributions. Well, I think the work of an LSR editor is roughly described in CG 7. LSR work. Afaict, license issues are

Re: Potential LSR licensing violations

Am Do., 20. Okt. 2022 um 07:23 Uhr schrieb Werner LEMBERG : > > So far, so good. However, take this snippet: > > > > https://lsr.di.unimi.it/LSR/Item?id=102 > > > > It begins with 300 lines of code that used to be in the LilyPond > > repository, released under the GPL, before they were considered

Re: weird error engraving two files with 2.23.14

Am Do., 13. Okt. 2022 um 14:08 Uhr schrieb Thomas Morley : > > Am Do., 13. Okt. 2022 um 01:09 Uhr schrieb Federico Bruni > : > > These two files are copyrighted and I can't share them here, but I will > > send privately to anyone interested in debugging this issue. >

Re: weird error engraving two files with 2.23.14

Am Do., 13. Okt. 2022 um 01:09 Uhr schrieb Federico Bruni : > > Hi folks > > I've recently used convert-ly to update my private music sheet library > and test version 2.23.14 (official binaries). > Two files are failing with the same error message: > > Drawing systems... > Converting to

Re: Duration lines and dots

Am Mo., 10. Okt. 2022 um 00:27 Uhr schrieb Jean Abou Samra : > > Harm, > > On the lilypond-user-fr list, there is a user wondering about this: > > \version "2.23.14" > > \new Voice \with { >\consists Duration_line_engraver >% \override DurationLine.bound-details.left.start-at-dot = ##t > }

Re: Tablature full notation rests and tablature aethstetic improvements

Hi, Am Fr., 7. Okt. 2022 um 07:44 Uhr schrieb tk5wbps2--- via Discussions on LilyPond development : > > I'm considering contributing to lilypond. > welcome to the pond > > The two features I propose are as follows. > > 1) An option to include rests in tablature (with \tabFullNotation). > Afaict,

Re: Markup command \simple

Am So., 2. Okt. 2022 um 16:58 Uhr schrieb Jean Abou Samra : > > > > Le 02/10/2022 à 15:05, David Kastrup a écrit : > > If the function itself isn't used as a placeholder. > > I haven't found any such use. > > I've opened https://gitlab.com/lilypond/lilypond/-/merge_requests/1650 > Meanwhile I

Re: LSR changes for \textMark/\textEndMark

Am Mi., 28. Sept. 2022 um 14:32 Uhr schrieb Jean Abou Samra : > > Le 27/09/2022 à 22:07, Jean Abou Samra a écrit : > > Le 27/09/2022 à 21:05, Thomas Morley a écrit : > >> Hi Jean, > >> > >> will do. > >> Is it urgent? I'll have not much time

Re: LSR changes for \textMark/\textEndMark

Am Di., 27. Sept. 2022 um 13:30 Uhr schrieb Jean Abou Samra : > > Harm, > > As you can see from open MRs, I'm working on moving from \mark > to text marks in tests and documentation. Could you please apply the > following changes in LSR? > > These snippets should have their doc tag removed

Re: Moving most initialization to .scm files

Am Mo., 5. Sept. 2022 um 21:34 Uhr schrieb Jonas Hahnfeld : > > On Mon, 2022-09-05 at 21:22 +0200, Thomas Morley wrote: > > Am Mo., 5. Sept. 2022 um 19:50 Uhr schrieb Jonas Hahnfeld via > > Discussions on LilyPond development : > > > > > > On Sun, 2022-09-04 a

Re: Moving most initialization to .scm files

Am Mo., 5. Sept. 2022 um 19:50 Uhr schrieb Jonas Hahnfeld via Discussions on LilyPond development : > > On Sun, 2022-09-04 at 22:38 +0200, Jean Abou Samra wrote: > > This needs to be done for lots of code in lots of files, so it will be > > quite a major change to the source even though it is just

Re: Removing a snippet

Am So., 4. Sept. 2022 um 21:26 Uhr schrieb Dan Eble : > > Harm, > > The Contributor's Guide has sections on adding, editing, and renaming > snippets. What should I do when I want to stop using a snippet in the > Notation Reference? Well, short answer, adjust NR in

Re: no links in PDFs with gs 9.56.1

Am So., 7. Aug. 2022 um 13:05 Uhr schrieb Werner LEMBERG : > > > > If I build the docs I use 'extractpdfmark' as well. In the light of > > this thread I tried ghostscript self-compiled from their most recent > > master, giving me 9.57.0. [...] > > > > [compilation time] is insane. > > I also

Re: no links in PDFs with gs 9.56.1

Am Sa., 30. Juli 2022 um 12:39 Uhr schrieb Werner LEMBERG : > > > >> In case you are forced to use 9.56.1, add `-dNEWPDF=false` to the > >> gs command line options (in file `Documentation/GNUmakefile`) to > >> make gs use the old PDF engine, which produces good results. > > > > So this is about

Re: LSR snippet doesn’t appear

Am Di., 2. Aug. 2022 um 13:32 Uhr schrieb Jean Abou Samra : > > > > > Le 2 août 2022 à 13:28, Thomas Morley a écrit : > > > > Am Di., 2. Aug. 2022 um 13:21 Uhr schrieb Jean Abou Samra > > : > >> > >> Some time ago, I entered a snippet entit

Re: LSR snippet doesn’t appear

Am Di., 2. Aug. 2022 um 13:21 Uhr schrieb Jean Abou Samra : > > Some time ago, I entered a snippet entitled "Adding a QR code" in LSR, and it > appears in the snippet database (even without logging in), but a search for > "QR code" in the search bar yields no result. Am I doing something wrong?

Re: Fixing regressions and serious issues

Am Mi., 20. Juli 2022 um 11:40 Uhr schrieb Jonas Hahnfeld via Discussions on LilyPond development : > > On Thu, 2022-07-14 at 17:38 +0200, Jean Abou Samra wrote: > I agree, even though I'd like to note that only those marked ~Critical > actually block the release. There are a number of

Re: Nested segno and volta repeats

peat segno, neat thing, I've always had to do it by hand > with cadenza trickeries... > > L > > On Sun, 29 May 2022, 10:45 Thomas Morley, wrote: >> >> Am So., 29. Mai 2022 um 09:56 Uhr schrieb Jean Abou Samra >> : >> > >> > Hi Dan, >> >

Re: Nested segno and volta repeats

Am So., 29. Mai 2022 um 09:56 Uhr schrieb Jean Abou Samra : > > Hi Dan, > > Is there any way to get this repeat structure with the recent > repeat additions? This is from a question on the user list. > > ||: A:|| B|| > Fine D.C. Al Fine > > -> A A B A >From a musicians

Re: checkout releases?

Thanks all! Am Do., 26. Mai 2022 um 13:53 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Alas I can't checkout v2.23.7: > > $ git checkout v23.7 > > error: pathspec 'v23.7' did not match any file(s) known to git > > I really hate that damn mach

checkout releases?

Hi, some time ago we decided to use v2.23.7 instead of the old release/2.23.6-1 in the repository. Alas I can't checkout v2.23.7: $ git checkout v23.7 error: pathspec 'v23.7' did not match any file(s) known to git Though I've success with $ git checkout release/2.23.6-1 Updating files: [...]

Re: snippet fails with 2.23.

Am Di., 17. Mai 2022 um 20:39 Uhr schrieb Jean Abou Samra : > > Le 16/05/2022 à 23:07, Thomas Morley a écrit :Well, I _am_ a LSR-editor. > > Though, sometimes it feels I am the only one (not really true, Werner > > does a lot but his focus is more on lsr-software and > &g

Re: snippet fails with 2.23.

Am Mo., 16. Mai 2022 um 09:52 Uhr schrieb Mats Bengtsson : > >Thanks for your work with this. I happened to stumble upon >[1]https://lsr.di.unimi.it/LSR/Item?id=1113, "Watermark" that most >likely does not do exactly what was intended. It belongs _not_ to the duties of the

Re: snippet fails with 2.23.

Am So., 15. Mai 2022 um 21:44 Uhr schrieb Thomas Morley : > > Am So., 15. Mai 2022 um 14:11 Uhr schrieb Jean Abou Samra > : > > > > > > > > Le 15/05/2022 à 14:01, Thomas Morley a écrit : > > > Hi, > > > > > > the new doc-tagged LSR-snipp

Re: LSR and Documentation/snippets/new

Am Mi., 11. Mai 2022 um 23:24 Uhr schrieb Thomas Morley : > > Am Di., 10. Mai 2022 um 00:27 Uhr schrieb Werner LEMBERG : > > > > > > >> All snippets are updated. > > > > > > Thanks a lot, Harm! > > > > +1. Good job! > > > > &

Re: snippet fails with 2.23.

Am So., 15. Mai 2022 um 14:11 Uhr schrieb Jean Abou Samra : > > > > Le 15/05/2022 à 14:01, Thomas Morley a écrit : > > Hi, > > > > the new doc-tagged LSR-snippet 'tambourine-example.ly' > > https://lsr.di.unimi.it/LSR/Item?id=1070 > > > >

Re: LSR and Documentation/snippets/new

Am Sa., 7. Mai 2022 um 00:36 Uhr schrieb Thomas Morley : > > Folks, > > currently I'm updating all LSR-files to work with 2.22. > One step is > CG 7.7 Updating the LSR to a new version > [...] > 5. Copy relevant snippets (i.e. snippets whose version is equal to or >

Re: snippet fails with 2.23.

Am So., 15. Mai 2022 um 14:08 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Hi, > > > > the new doc-tagged LSR-snippet 'tambourine-example.ly' > > https://lsr.di.unimi.it/LSR/Item?id=1070 > > > > %% > > \paper { tagline = ##f }

snippet fails with 2.23.

Hi, the new doc-tagged LSR-snippet 'tambourine-example.ly' https://lsr.di.unimi.it/LSR/Item?id=1070 %% \paper { tagline = ##f } #(define mydrums '((tambourine default #t 0))) \new DrumStaff \with { instrumentName = #"Tambourine" } \drummode { \set DrumStaff.drumStyleTable =

Re: LSR and Documentation/snippets/new

Am Sa., 14. Mai 2022 um 09:31 Uhr schrieb Sebastiano Vigna : > > > > > On 13 May 2022, at 22:43, Thomas Morley wrote: > > > > > > I spoke too early... > > In the tarball the snippets still print \version "2.18.0", although > > they are com

Re: LSR and Documentation/snippets/new

Am Mo., 9. Mai 2022 um 23:45 Uhr schrieb Thomas Morley : > LSR-software is running 2.22. > Last LSR-problem I'm aware of (see above) is fixed. Hi Seba, I spoke too early... In the tarball the snippets still print \version "2.18.0", although they are compiled with 2.22. Pl

Re: LSR and Documentation/snippets/new

Am Di., 10. Mai 2022 um 00:27 Uhr schrieb Werner LEMBERG : > > > >> All snippets are updated. > > > > Thanks a lot, Harm! > > +1. Good job! > > > Werner The following snippets from Documentation/snippets/new (compiling with 2.22. and not previously in LSR) are now in LSR:

Re: LSR and Documentation/snippets/new

Am Sa., 7. Mai 2022 um 16:46 Uhr schrieb Thomas Morley : > > Am Sa., 7. Mai 2022 um 16:03 Uhr schrieb Thomas Morley > : > > > > Am Sa., 7. Mai 2022 um 14:13 Uhr schrieb Werner LEMBERG : > > > > > > > > > >> I think it's not really used at the m

Re: LSR and Documentation/snippets/new

Am Sa., 7. Mai 2022 um 14:13 Uhr schrieb Werner LEMBERG : > > > >> I think it's not really used at the moment because the LilyPond > >> version is 8 years old. I at least will definitely use it more when > >> it gets updated to 2.22. > > > > It has been already updated. > > This is excellent news!

Re: LSR and Documentation/snippets/new

Am Sa., 7. Mai 2022 um 00:36 Uhr schrieb Thomas Morley : > currently I'm updating all LSR-files to work with 2.22. Btw, current state: I converted all lsr-snippets to 2.22., inserted those from Documentation/snippets/new, fixed all crashes and most warnings: No ERRORs Some 'programming erro

Re: LSR and Documentation/snippets/new

Am Sa., 7. Mai 2022 um 00:46 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Please stop doing so, please first test, whether it compiles with > > current LSR-version, and please update the snippet _inside_ LSR. If > > you don't have an account please c

LSR and Documentation/snippets/new

Folks, currently I'm updating all LSR-files to work with 2.22. One step is CG 7.7 Updating the LSR to a new version [...] 5. Copy relevant snippets (i.e. snippets whose version is equal to or less than the new version of LilyPond running on the LSR) from ‘Documentation/snippets/new/’ into the set

Re: Setting up classical guitar fingerings

Am So., 20. Feb. 2022 um 22:41 Uhr schrieb Luca Fascione : > a) I'm looking for a way to get the fingerings where I want them without > using one-note-chord tricks Well, for Fingerings not in chord, like b-1 or -2-1 X-parent is NoteColumn _not_ NoteHead, Y-parent is VerticalAxisGroup. There is

Re: LilyPond 2.23.6 released

Am Di., 8. Feb. 2022 um 16:54 Uhr schrieb Jonas Hahnfeld via Discussions on LilyPond development : > > We are happy to announce the release of LilyPond 2.23.6. This is termed > a development release, but these are usually reliable. If you want to > use the current stable version of LilyPond, we

Re: Stepping down from Patch Meister role

Am Sa., 8. Jan. 2022 um 11:06 Uhr schrieb James : > > Hello, > > I am going to stop doing the Patch countdown at the end of this month. > > I'll continue for the next few weeks, but my last countdown will be > whatever the last date in January ends up being. > > Thanks for your understanding. > >

Re: LilyPond | Various doc issues (!1095)

Am Mi., 5. Jan. 2022 um 16:45 Uhr schrieb Jean Abou Samra : > > > > Le 05/01/2022 14:04, Thomas Morley a écrit : > > > > > > Am Mi., 5. Jan. 2022 um 13:28 Uhr schrieb Jean Abou Samra > > : > > > > > > [Replying via the mailing list because it

Re: LilyPond | Various doc issues (!1095)

Am Mi., 5. Jan. 2022 um 13:28 Uhr schrieb Jean Abou Samra : > >[Replying via the mailing list because it's unrelated to Werner's MR] > >Le 05/01/2022 12:59, Thomas Morley (@Thomas_Morley) > a écrit : > >[1]Thomas Morley commented on a discussion on >[2]D

Re: RFC: Adding syntax highlighting to the official documentation

Am Di., 28. Dez. 2021 um 22:22 Uhr schrieb Jean Abou Samra : > > On the merge request, Dan proposed the attached style. What do you think? > > Thanks, > Jean Well, I use jEdit for my own work. There I use a highly customized syntax highlighting: Many different colors and apart from comments all

Re: cross-staff, broken Glissando

Am Do., 11. Nov. 2021 um 19:24 Uhr schrieb Jean Abou Samra : > > Le 07/11/2021 à 12:39, Thomas Morley a écrit : > > Anyone up for it? > > Phooey. > > https://gitlab.com/lilypond/lilypond/-/merge_requests/998 > > Cheers, > Jean Looks like it was much more wor

Re: TimeSignature with note in denominator

Am Mo., 8. Nov. 2021 um 21:04 Uhr schrieb Kieren MacMillan : > > Hi Werner, > > >> For my first official patch as a Lily-dev, I’m proposing to make the > >> result of an official > >> #'style in TimeSignature. > > > > It would be nice to see some

Re: Manipulating instrument names and staff group names

latant counter-example is in the person > of Harm. Indeed :) I don't know C++, I don't know python. At the time I discovered LilyPond I didn't know scheme. While using LilyPond I felt the wish to get some things from LilyPond, which were not there - and learned scheme. Today there are several o

Re: cross-staff, broken Glissando

Am So., 7. Nov. 2021 um 14:00 Uhr schrieb Jean Abou Samra : > >>> That said,... > >>> If I always compensate the right ending-point with (pseudo-code) > >>> (ly:grob-relative-coordinate Y) > >>> Then the crosses are at those positions Mike's patch promises. > >> Really System? Isn't this going

Re: cross-staff, broken Glissando

Am So., 7. Nov. 2021 um 13:47 Uhr schrieb Aaron Hill : > > On 2021-11-07 4:26 am, Jean Abou Samra wrote: > > (Adding Aaron in CC.) > > Thanks, Jean. I am subscribed to lily-devel, so I did see the thread. > > > >> Alas, because my lack of C++-knowledge, I can't do it myself. > > > > You should

Re: cross-staff, broken Glissando

Am So., 7. Nov. 2021 um 13:26 Uhr schrieb Jean Abou Samra : > > (Adding Aaron in CC.) > > Le 07/11/2021 à 12:39, Thomas Morley a écrit : > > Hi, > > > > commit 94860164493ab3a209986b0e3662ff7bd8958cb5 > > Author: Mike Solomon > > Date: Mon Mar 28 10:58

cross-staff, broken Glissando

Hi, commit 94860164493ab3a209986b0e3662ff7bd8958cb5 Author: Mike Solomon Date: Mon Mar 28 10:58:29 2011 -0400 Assures smooth transitions at glissando line breaks. When a glissando breaks over lines, the left point of the beginning-of-line glissando picks up on the y-axis where

Re: markup-command rounded-box is broken

Am So., 10. Okt. 2021 um 11:06 Uhr schrieb Lukas-Fabian Moser : > > > > this would have the advantage to be inline with the doc-string and > > solve the issue at hand. > Should I prepare a MR? Please, do so. Additionally, I'll think a bit deeper about below. Thanks, Harm > > Though, speaking

Re: markup-command rounded-box is broken

Am So., 10. Okt. 2021 um 10:21 Uhr schrieb Lukas-Fabian Moser : > > > > So in my impression, rounded-box-stencil might deserve a refactoring > > anyway? > > I would propose: > > lukas@Aquarium:~/git/lilypond/scm(dev/lfm/rounded-box)$ git diff master > diff --git a/scm/define-markup-commands.scm

  1   2   3   4   5   6   7   8   9   10   >