Am So., 2. Dez. 2018 um 14:01 Uhr schrieb Sandro Santilli :
>
> On Sun, Dec 02, 2018 at 11:01:36AM +, J Martin Rushton wrote:
>
> > "LilyPond source files appear to be written in a custom programming
> > language whose grammar is never discussed."
> > - I'm afraid this one is bang on target.
>
Am Fr., 30. Nov. 2018 um 12:02 Uhr schrieb Tyler Mitchell :
>
> On Fri, Nov 30, 2018 at 11:09:52AM +0100, Thomas Morley wrote:
> > Probably it's enough to use the music-function-default-arguments,
> > which can be omitted with newer versions, i.e.:
> >
> >
Am Fr., 30. Nov. 2018 um 09:19 Uhr schrieb Tyler Mitchell :
>
> On Thu, Nov 29, 2018 at 10:10:16PM +0100, Thomas Morley wrote:
> > Hi,
> >
> > I once made below (here a little lifted up):
> >
> [...snip...]
> >
> > HTH,
> > Harm
>
> Than
Am Do., 29. Nov. 2018 um 23:22 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Do., 29. Nov. 2018 um 11:04 Uhr schrieb Richard Shann
> > :
> >
> >>
> >> As a further point is the term "standard markup objects" well-
> >&g
Hi Richard,
please bear in mind I'm not a native speaker.
Thus work on the docs is pretty difficult for me.
That said:
Am Do., 29. Nov. 2018 um 11:04 Uhr schrieb Richard Shann
:
> On Thu, 2018-11-29 at 09:50 +0100, Thomas Morley wrote:
> > Well, in NR 1.8.1 Writing text one
Am Do., 29. Nov. 2018 um 11:57 Uhr schrieb Tyler Mitchell :
>
> I'm trying to figure out how to add a "parenthesized" second key
> signature to my music, something like this:
>
> https://www.ldx.ca/tmp/paren-key-1.png
>
> I experimented with adding two \key commands one after the other,
> b
Am Do., 29. Nov. 2018 um 09:34 Uhr schrieb Jeff Olson :
>
> I have a complex Mutopia submission that requires different formatting
> for A4 and Letter sized paper (it's too tight on the page to trust
> lilypond's spacing algorithms on the same source without paper specific
> tweaks).
>
> So I'd lik
Am Do., 29. Nov. 2018 um 09:33 Uhr schrieb Richard Shann
:
>
> On Wed, 2018-11-28 at 15:45 +0100, Lukas-Fabian Moser wrote:
> > > Sorry, I should have made it clearer that this index is being
> > > automatically generated. Now you point out that there is an
> > > \autoOageBreaksOff, which is what I
Am Di., 27. Nov. 2018 um 16:22 Uhr schrieb Richard Shann
:
>
> I'm creating an index to my scores, in the form of a sequence of
> LilyPond markups (for title, composer, first few bars etc).
What exactly are you doing? An example would be nice.
> It is working well apart from page breaking which c
Am Di., 27. Nov. 2018 um 00:16 Uhr schrieb Malte Meyn :
> „Notes, forked stems“ (l. 109)
> → should be „yes (fake: rotated stems or custom lines)“
>
Or like attached pdf.
Most recent code here (if someone's interested)
https://archiv.lilypondforum.de/index.php/topic,1176.msg6932.html#msg6932
Che
Am So., 25. Nov. 2018 um 16:09 Uhr schrieb Phil Holmes :
>
> - Original Message -
> From: "David Sumbler"
>
> > The parameters NonMusicalPaperColumn and suchlike have long been a
> > mystery to me. If it can be done reasonably succinctly, could you
> > perhaps explain what NonMusicalPaper
'
Am Sa., 24. Nov. 2018 um 22:28 Uhr schrieb Thomas Morley
:
>
> Am Fr., 23. Nov. 2018 um 15:28 Uhr schrieb David Sumbler :
> >
> > -Original Message-
> > From: David Sumbler
> > Reply
> > -To: da...@aeolia.co.uk
> > To: lilypond-user@gn
Am Fr., 23. Nov. 2018 um 15:28 Uhr schrieb David Sumbler :
>
> -Original Message-
> From: David Sumbler
> Reply
> -To: da...@aeolia.co.uk
> To: lilypond-user@gnu.org
> Subject: Spacing issue after Mark and TextScript
> Date: Wed, 21 Nov 2018 12:24:29 +
>
> %%%
> \versio
Am Do., 22. Nov. 2018 um 23:49 Uhr schrieb Patrick Karl :
>
> I have lately been trying to move from v2.19.81 to 2.19.82. The biggest
> problem I see at this early stage is that
> v2.19.82 documentation is apparently dependent upon a new font,
> Emmentaler-20. Or at least I
> get an error mess
Am So., 18. Nov. 2018 um 22:16 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > As a side-effect of this thread I learned that doing
> > whatever = \context Staff \applyContext #(lambda (ctx) ...)
> > will affect Staff _and_ all it's alias. Furtherm
Am So., 18. Nov. 2018 um 21:15 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am So., 18. Nov. 2018 um 20:40 Uhr schrieb David Kastrup :
> >
> >> Just do
> >>
> >> (eq? ctx (ly:context-find ctx 'Staff))
> >>
> >>
Am So., 18. Nov. 2018 um 20:40 Uhr schrieb David Kastrup :
> Just do
>
> (eq? ctx (ly:context-find ctx 'Staff))
>
> --
> David Kastrup
I did not even consider to use ly:context-find. The description says:
Find a _parent_ of context that has name or alias name. Return #f if not found.
So I expecte
Am So., 18. Nov. 2018 um 19:19 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Hi,
> >
> > consider the code below. I'd like to restrict usage to Staff-like
> > contexts, i.e. Staff, Tab- and DrumStaff, etc would be ok, but
> > container-
Am So., 18. Nov. 2018 um 18:23 Uhr schrieb Thomas Morley
:
>
> Hi,
>
> consider the code below. I'd like to restrict usage to Staff-like
> contexts, i.e. Staff, Tab- and DrumStaff, etc would be ok, but
> container-contexts like StaffGroup, etc should lead to return '(
Hi,
consider the code below. I'd like to restrict usage to Staff-like
contexts, i.e. Staff, Tab- and DrumStaff, etc would be ok, but
container-contexts like StaffGroup, etc should lead to return '().
Pseudo-code:
\new Staff(Group)
\with {
\applyContext
#(lambda (context)
(if
Am So., 18. Nov. 2018 um 08:36 Uhr schrieb Andrew Bernard
:
>
> What is the approved and recommend way to attach images for small examples to
> posts in this list?
>
> In the past I have just made an attachment to the post,
Please continue to do so.
Speaking only for myself, frequently I don't se
Am Sa., 17. Nov. 2018 um 12:03 Uhr schrieb Thomas Morley
:
> Default \center-column does not adjust baseline-skip according to the
> grobs font-size.
> Below I wrote 'center-column-fontsize-adjusted-baseline-skip' (you
> should probably rename it, lol), which does
Hi Kieren,
Am Sa., 17. Nov. 2018 um 02:36 Uhr schrieb Kieren MacMillan
:
>
> Hi all,
>
> In the snippet below, you’ll see that I’m attempting to override Fingering in
> a custom context to add a caret (^) on top of the [formatted] finger number
> to make it into a scale degree.
>
> The "padding"
Am Mi., 14. Nov. 2018 um 18:07 Uhr schrieb Pierre Perol-Schneider
:
>
> Here's where I am so far:
>
> \version "2.19.82"
> \fixed c' {
> <<
> { \voiceOne
> c16-\offset positions #-1 [ c c c c c c c c c c c c ] }
> \\
> { \voiceOne s4
>\once\override Beam.positions = #'
Am Mi., 14. Nov. 2018 um 11:04 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > I'm not convinced about below, but for the record:
> >
> > One could give the key-function a string-argument, or probably a symbol
> > And react on the input, like
Am Mi., 14. Nov. 2018 um 10:28 Uhr schrieb David Kastrup :
>
> David Kastrup writes:
>
> > Davide Liessi writes:
> >
> >> Il giorno mer 14 nov 2018 alle ore 08:25 Keizen Li Qian
> >> ha scritto:
> >>> Parsing.../usr/share/lilypond/2.18.2/ly/music-functions-init.ly:564:11:
> >>> In procedure ly:m
Am Mo., 12. Nov. 2018 um 19:02 Uhr schrieb Torsten Hämmerle
:
> It really starts getting funny if you change the c' into a d' (the c' just
> didn't show up somewhere because it did not change the C major chord):
>
> %%
> <<
> \chords { c }
> \relative { \clef bass d' }
> >>
> %
Am Mo., 12. Nov. 2018 um 20:30 Uhr schrieb David Kastrup :
>
> Torsten Hämmerle writes:
>
> > David Kastrup wrote
> >> If you want a Staff, create it rather than rely on somebody else doing
> >> that, maybe.
> >
> > That is basically what I thought (and wrote), too.
> > But, admittedly, these shor
Am Mo., 12. Nov. 2018 um 05:36 Uhr schrieb Rohan Srinivasan
:
>
> Friendly bump.
Hi,
this was asnwered already:
http://lilypond.1069038.n5.nabble.com/Combining-lyric-verses-onto-one-line-tt217186.html#none
Didn't you get the replies?
Cheers,
Harm
__
Am So., 11. Nov. 2018 um 11:57 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Use \voiceTwo instead of \stemDown, then LilyPond will place the rest
> > correctly and the warning disappears.
>
> Sometimes I think we should undocument \stemUp/\stemDown.
Am So., 11. Nov. 2018 um 01:39 Uhr schrieb Joseph Srednicki
:
>
> Hello:
>
> The following measure causes Lilypond to issue a warning about too many
> colliding rests.
>
> Is there a way that I can code this measure to avoid the warning?
>
> I checked the online mail archive. I found a message sta
Am Mi., 27. Juni 2018 um 22:31 Uhr schrieb David Kastrup :
>
>
> Hi folks,
>
> I've been afraid of looking at my bank account for the past months but
> finally had to do so. For the last three months, the payments from
> LilyPond users were stable: one paying €100 monthly, one paying €75
> monthly
Am Do., 8. Nov. 2018 um 21:00 Uhr schrieb Jérôme Plût :
>
>
> #(begin
> ; after http://lsr.di.unimi.it/LSR/Snippet?id=969
> (define-markup-command (with-background layout props color arg) (color?
> markup?)
>(let* ((stencil (interpret-markup layout props arg))
> (X-ext (ly:stencil-ex
Am Do., 8. Nov. 2018 um 10:10 Uhr schrieb David Kastrup :
>
> Jérôme Plût writes:
>
> > I would like to *read*, from within a Scheme function
> > (define-music-function), the values of variables such as
> > Score.currentBarNumber or Score.alternativeNumberingStyle.
> >
> > I can have a guess that
Am Mo., 5. Nov. 2018 um 13:24 Uhr schrieb David Sumbler :
>
> My subject line only partially describes the problem.
>
> I find that a tie is not shown after a line-break if the following
> conditions are all true:
> 1. There is a line-break (as stated)
> 2. There is a new time signature
> 3. There
Am Mo., 5. Nov. 2018 um 03:07 Uhr schrieb Aaron Hill :
>
> On 2018-11-04 2:12 pm, Rohan Srinivasan wrote:
> > Hi list,
> >
> > I have the following code for a short song I'm engraving:
> >
> > [ . . . ]
> >
> > Since all 3 verses have "That's" at the end of the line, I would like
> > to
> > combine
Am So., 4. Nov. 2018 um 16:38 Uhr schrieb pablocordal :
>
> Hi Urs and Torsten,
>
> This snippet is exactly what I need. I'm trying to test it, but when I copy
> your code in Frescobaldi (which uses Lilypond underneath) and try to compile
> it I receive this error:
>
> error: syntax error, unexpec
Am So., 4. Nov. 2018 um 01:30 Uhr schrieb David Nalesnik
:
>
> On Sat, Nov 3, 2018 at 7:24 PM David Nalesnik
> wrote:
> >
> > On Sat, Nov 3, 2018 at 7:23 PM Andrew Bernard
> > wrote:
> > >
> > > Hi David,
> > >
> > > Isn't Lilypond open source? Cant you make your code open source? I am not
> >
Am Sa., 3. Nov. 2018 um 16:16 Uhr schrieb Thomas Morley
:
>
> Am Do., 1. Nov. 2018 um 16:21 Uhr schrieb Thomas Morley
> :
>
> > Furthermore, compiling your code with my guilev2-setup fails right
> > from the beginning with:
> > error: GUILE signaled an error for
Am Sa., 3. Nov. 2018 um 21:36 Uhr schrieb Ben :
>
> On 11/3/2018 4:25 PM, David Nalesnik wrote:
>
> On Sat, Nov 3, 2018 at 3:21 PM Ben wrote:
>
> On 11/3/2018 4:16 PM, David Nalesnik wrote:
>
> On Sat, Nov 3, 2018 at 2:57 PM Ben wrote:
>
> On 11/3/2018 2:54 PM, m...@opus11.net wrote:
>
> Just won
Am Do., 1. Nov. 2018 um 16:21 Uhr schrieb Thomas Morley
:
> Furthermore, compiling your code with my guilev2-setup fails right
> from the beginning with:
> error: GUILE signaled an error for the expression beginning here
> #
> (load "motif.scm")
> Unable to find fil
Am Sa., 3. Nov. 2018 um 13:16 Uhr schrieb Sven Axelsson
:
>
> I want to auto generate a collection of short tunes by \include-ing the
> existing files. If there is room for it, I want to put several tunes on the
> same page, but I only want page breaks between tunes, never in the middle of
> a t
Am Sa., 3. Nov. 2018 um 13:12 Uhr schrieb Thomas Morley
:
>
> Am Sa., 3. Nov. 2018 um 12:27 Uhr schrieb Federico Bruni :
>
> > The second staff at the bottom will be cropped.
> > This seems to happen (at least with above file) only with TabStaff,
> > DrumStaff, Rhyt
Am Sa., 3. Nov. 2018 um 12:27 Uhr schrieb Federico Bruni :
> The second staff at the bottom will be cropped.
> This seems to happen (at least with above file) only with TabStaff,
> DrumStaff, RhythmicStaff and VaticanaStaff, while other kinds of Staff
> works fine. Is this a good clue to investiga
Am Do., 1. Nov. 2018 um 19:37 Uhr schrieb Jérôme Plût :
>
> Kalendis Novembribus MMXVIII scripsit Thomas Morley :
> > Part of the problem is you use 'structure as a music-property without
> > declaring it. As a consequence using the option -dcheck-internal-types
> &g
Am Mo., 29. Okt. 2018 um 15:30 Uhr schrieb Jérôme Plût :
>
> I have a few questions about using Scheme to build Lilypond data.
>
> 1. I have some Scheme code that builds custom articulations (more
> precisely, it attaches metadata to NoteEvents, and the only way I found
> to make this possible is v
Am Do., 1. Nov. 2018 um 16:24 Uhr schrieb Kieren MacMillan
:
>
> Hi Werner,
>
> > +1. I've *never* seen an ambitus except at the very beginning of a piece.
>
> I often use an ambitus in front- or end-matter, to give vocal ranges separate
> from the score itself. Of course, "front-matter" can be i
Am Do., 1. Nov. 2018 um 14:44 Uhr schrieb Jérôme Plût :
>
>
> I wrote some macros to help write analysis of musical pieces.
> Here is an example file (on Bach's Invention I).
>
> Structural analysis is (of course) performed by hand, and displayed on
> a Lyrics structure on top of the music. (This p
Am Mi., 31. Okt. 2018 um 19:09 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi there,
>
> Not sure if this is a bug or if I am using it wrong.
>
> I've started using :
> \consists "Mark_engraver"
> \consists "Bar_number_engraver"
> , etc
> inside StaffGroups since it is now working.
> (Fixed with I think
Am Mi., 31. Okt. 2018 um 18:11 Uhr schrieb joelhamme :
>
> My fellow singers in choir have been asking me to improve the visual chunking
> of choir staves. They wanted to have closed bar lines on the right edge of
> each choir staff.
>
> Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of
Am Mo., 29. Okt. 2018 um 12:10 Uhr schrieb David Sumbler :
>
>
> -Original Message-
> From: Thomas Morley
> To: David Sumbler
> CC: lilypond-user
> Subject: Re: Line-breaking with non-aligned barlines
> Date: Sun, 28 Oct 2018 02:01:04 +0200
>
> Am Fr., 26.
Am Mo., 29. Okt. 2018 um 07:58 Uhr schrieb Werner LEMBERG :
>
>
> >> If possible, this should be made the default. I even suggest to
> >> completely drop the current behaviour since I can't envision a
> >> situation where you really want this.
> >
> > I'll open an issue on the tracker.
>
> Thanks.
Am So., 28. Okt. 2018 um 08:07 Uhr schrieb Werner LEMBERG :
>
> > A minimal would be:
> >
> > \paper { indent = 0 ragged-right = ##t }
> >
> > {
> > \override Beam.breakable = ##t
> > s2. s8
> > c'8[
> > \break
> > c'16]
> > }
> >
> > Not sure I'd call it a bug.
>
> IMHO, it is
Am Fr., 26. Okt. 2018 um 13:58 Uhr schrieb Thomas Morley
:
> currently I've not the time to dive deeper in your code, maybe later
> today or during the upcoming weekend.
Hi Urs,
I haven't looked deeply into your code, but I think it will not work as desired.
First some gen
Am So., 28. Okt. 2018 um 17:56 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> >\override BarNumber.after-line-breaking = #'()
>
> Whoa… What exactly does that do? It seems like a nuclear option!
>
> I’ll be sure to give it a try the next time I run into the issue (which
> should be very soon,
Am So., 28. Okt. 2018 um 12:39 Uhr schrieb Simon Albrecht
:
>
> Hello list,
>
> I’m currently debugging a couple issues with a use case of the MarkLine
> context. One of them is demonstrated in the attached minimal scenario:
> with a MarkLine atop the topmost staff, the barnumbers fail to align
> w
Am Fr., 26. Okt. 2018 um 23:52 Uhr schrieb David Sumbler :
> But as things are the break here is still unsatisfactory
> because the semiquaver just after the break has 2 long beams stretching
> back to the start of the line, whereas one would ideally want 1 long
> beam and a short one. I haven't
Am So., 28. Okt. 2018 um 00:28 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> > your example works here out of the box and without any problem.
> > So I don't understand the problem.
>
> They’re nested, not interlocking/overlapping (as I want them to be).
> Even though I set the ids to be "interlo
Am So., 28. Okt. 2018 um 00:04 Uhr schrieb Kieren MacMillan
:
>
> Hi all,
>
> I’d like to use spanner-id (or similar) to interlock/overlap
> HorizontalBracket spanners.
> Is this possible?
>
> Thanks,
> Kieren.
>
> %%% MWE BEGINS
> \version "2.19.80"
> \layout { \context { \Voice \consists "Horiz
Am Fr., 26. Okt. 2018 um 18:56 Uhr schrieb Thomas Morley
:
> << e { s1*15/320 \bar "" \ctxMom s } >>
Well, could be shortened to s1*3/64 and the \ctxMom-command should be
deleted after the duration is found,
Am Fr., 26. Okt. 2018 um 18:26 Uhr schrieb David Sumbler :
>
> Below I have shown a compile-able 93 lines (sorry it can't be made much
> shorter) from the files for a much longer piece.
>
> In this particular passage the harpsichord plays 4 bars in strict tempo
> whilst the flute plays 4 bars rubat
Am Fr., 26. Okt. 2018 um 18:18 Uhr schrieb Hans Åberg :
>
>
> > On 26 Oct 2018, at 17:41, Thomas Morley wrote:
> >
> > But you could do (at least on Linux):
> >
> > lilydevel -e "(begin (define myhash (make-hash-table))(hashq-set!
> > myhash
Am Fr., 26. Okt. 2018 um 16:44 Uhr schrieb Peter Anglea :
>
> I’m trying to use the -e (--evaluate) option to define a hash, not just a
> single variable. For instance
>
> lilypond -e ‘((define myhash (make-hash-table))(hashq-set! myhash
> ‘foo “bar”))’ file.ly
>
> The above doesn’t work.
Am Fr., 26. Okt. 2018 um 15:41 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi,
> Please consider the following example:
>
> %%
> \version "2.19.82"
> music =
> \fixed c' {
> \time 3/8
> \voiceOne
> 4. q
> }
> { \music } { \music } { \music }
> %%
>
> After trying several compilation, sometimes t
Hi Urs,
currently I've not the time to dive deeper in your code, maybe later
today or during the upcoming weekend.
For now only about:
Am Fr., 26. Okt. 2018 um 11:54 Uhr schrieb Urs Liska :
> Additionally (but this is already present
> in your code) when using make-with-dimensions-markup (where i
Hi Urs,
Am Do., 25. Okt. 2018 um 17:49 Uhr schrieb Urs Liska :
>
> Hi Harm,
>
> thank you for this. From the *behaviour* this seems like what I need, but I
> have a few questions that may make it not really usable for my case.
>
>
> Am 24.10.2018 um 18:25 schrieb Thoma
Am Do., 25. Okt. 2018 um 14:30 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Di., 9. Okt. 2018 um 01:24 Uhr schrieb David Kastrup :
> >>
> >> David Kastrup writes:
> >>
> >> > namely a bunch of Translator_creator s creating C
Am Do., 25. Okt. 2018 um 19:03 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi Thomas,
>
> > Yep, set-global-staff-size _must_ be set at top-level, outside of \book.
>
> That's good to know.
> The documentation got me going on using-it inside \book{}s.
> http://lilypond.org/doc/v2.19/Documentation/notatio
Hi Pierre-Luc,
Am Mi., 24. Okt. 2018 um 16:01 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi there,
>
> Is this a bug?
>
> \version "2.21.0"
> %#(set-global-staff-size 4)
> \book {
> #(set-global-staff-size 4)
> \score {
> {\tempo 4=120 c4}
> \layout {}
> }
> }
>
> I'm trying to set the gl
Am Mi., 24. Okt. 2018 um 16:00 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Mi., 24. Okt. 2018 um 01:07 Uhr schrieb David Kastrup :
> >>
> >> Thomas Morley writes:
> >>
> >> > Am Di., 23. Okt. 2018 um 23:54 Uhr schrieb D
Am Di., 9. Okt. 2018 um 01:24 Uhr schrieb David Kastrup :
>
> David Kastrup writes:
>
> > namely a bunch of Translator_creator s creating C++ engravers (maybe the
> > print expression should at least mention _which_ C++ engraver in order
> > to make them look less similar)
>
> which is actually pr
Am Di., 23. Okt. 2018 um 08:28 Uhr schrieb Urs Liska :
>
> Hi,
>
> I want to use TextScript.staff-padding to produce markup elements that
> are aligned to their baseline. In order to prevent the texts from moving
> vertically to avoid collisions I used \textLengthOn (or its spelled-out
> variant):
Am Mi., 24. Okt. 2018 um 17:02 Uhr schrieb Ben :
> This should be what you need (see attached)
We do have 'number-format', so one could do:
#(define-public (format-roman-mark-numbers mark context)
(make-bold-markup (number-format 'roman-upper mark)))
#(define-public (format-boxed-roman-mark-n
Am Mi., 24. Okt. 2018 um 16:59 Uhr schrieb Ben :
>
> On 10/24/2018 10:39 AM, David Nalesnik wrote:
> Based on my reading of scm/translation.functions.scm, I have no idea
> why the following should not work:
>
> \version "2.19.82"
>
> \relative c'' {
> \set Score.markFormatter = #(format-mark-gen
Am Mi., 24. Okt. 2018 um 01:07 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Di., 23. Okt. 2018 um 23:54 Uhr schrieb David Kastrup :
> >
> >> So you should figure out what your comparison as equal is supposed to be
> >> doing in the first
Am Di., 23. Okt. 2018 um 23:54 Uhr schrieb David Kastrup :
> So you should figure out what your comparison as equal is supposed to be
> doing in the first place.
Yep, that's the culprit.
So the question is how to find the last rhythmic event of a
music-expression and place <>\stopTextSpan right
Am Mo., 22. Okt. 2018 um 21:59 Uhr schrieb Torsten Hämmerle
:
>
> Hi Harm,
>
> All these numbers are quite confusing at first glance. And at second and
> third glance, too.
> But they are nothing but conversion factors to switch units.
> And, unfortunately, LilyPond basically uses three concurrent
Hi,
for some reason I wanted a music-function which should end a
TextSpanner automagically at the next event which starts a new
TextSpanner or the last possible event at all.
Although it needs further testing I already found a glitch I really
can't explain or cope with: Sometimes, when the TextSp
Hi Torsten,
I've created
https://sourceforge.net/p/testlilyissues/issues/5430/
Am So., 21. Okt. 2018 um 21:33 Uhr schrieb Torsten Hämmerle
:
>
> Thomas Morley-2 wrote
> > I like to understand the numerical values.
> > The pair (-0.443862992125984 . 1.09258582677165) seems
Hi Torsten,
Am So., 21. Okt. 2018 um 17:17 Uhr schrieb Torsten Hämmerle
:
>
> Hi Harm,
>
> As it looks like, this function has not been working for some time, I've
> tested it back to 2.14.2
I even checked with 2.12.3 (without useful result)
> What does it do?
>
> In lily/stencil-interpret.cc, th
Hi,
in the IR one can find:
"
Function: ly:stencil-fonts s
Analyze s, and return a list of fonts used in s.
"
Though, how to get some output from it?
At least the code below returns nothing relevant.
(I used old syntax to check with all lily-version available, i.e.
since 2.12.3 up to 2.21.0)
#(
Am So., 21. Okt. 2018 um 09:27 Uhr schrieb Jean-Julien Fleck
:
>
> Thanks a lot Harm, it works perfectly !
A further thought:
Currently the code will return TextScript not Fingering. Thus we need
to mimic aligning/fontsize like Fingering and loose the possibility to
apply Fingering-overrides/tweak
Am Sa., 20. Okt. 2018 um 23:11 Uhr schrieb Jean-Julien Fleck
:
>
> Hi everyone,
>
> I have been searching how to indicate some optionnal finger indication in
> parenthesis but found no direct way. I ended up using some quite complicated
> hack:
>
> doigte = \markup { \halign #-0.5 \override #'(fo
Am Do., 18. Okt. 2018 um 11:32 Uhr schrieb Thomas Morley
:
> I made some mistakes while typing
> the "1{2{3 4 5)|#6 7)8) 9 1)"
>
> Ok, make that "several mistakes"
Ok, one could enter it using new indented lines (the code is able to
cope wi
Am Mi., 17. Okt. 2018 um 21:40 Uhr schrieb David Wright
:
>
> On Wed 17 Oct 2018 at 15:43:40 (+0200), Thomas Morley wrote:
>
> > I'd like to propose the code below. Attached as well.
> >
> > It stores the info in a string, which is converted t
Am Mi., 17. Okt. 2018 um 15:43 Uhr schrieb Thomas Morley
:
> I'd like to propose the code below.
>
> It stores the info in a string, which is converted to a nested list
> suitable for 'systemStartDelimiterHierarchy'. It can be nested in
> arbitrary depth.
Hi Lukas-Fabian,
I finally found the time to look deeper into it.
Am So., 14. Okt. 2018 um 15:07 Uhr schrieb Lukas-Fabian Moser :
> For me, there are the following issues with the systemStartDelimiterHierarchy
> design:
>
> 1) There's an overlap between systemStartDelimiter and
> systemStartDe
Hi Lukas-Fabian,
Am So., 14. Okt. 2018 um 15:07 Uhr schrieb Lukas-Fabian Moser :
> Though, the whole thread mixes up different topics.
>
> I'm not sure, tbh. Of course, setting delimiters and setting spacing should
> be thought of as mostly orthogonal aspects of setting up a score. The
> proble
.19.82"
foo = #(define-void-function ()() (write (*location*)))
{ R1 \foo R1 }
In my case it display in terminal:
#
i.e. a certain line and column
Cheers,
Harm
>> Thomas Morley schrieb am Fr., 12. Okt. 2018,
>> 10:29:
>>>
>>> Am Fr., 12. Okt. 2018 um 08:10
Am Sa., 13. Okt. 2018 um 11:56 Uhr schrieb foxfanfare :
>
> Lukas-Fabian Moser wrote
> > I disagree that LP does not follow the standard engraving rules. It just
> > seems to me that \new GrandStaff etc. imply a certain semantics which is
> > perfectly alright for, e.g., an orchestral Piano part, b
Hi Urs,
Am Sa., 13. Okt. 2018 um 00:00 Uhr schrieb Urs Liska :
> > %% Not sure if needed, though, better be paranoid and work on a copy of
> > %% default-script-alist to avoid possible bleed-over.
> > #(define my-script-alist default-script-alist)
>
> Except that this doesn't *create* a copy but
Am Fr., 12. Okt. 2018 um 20:57 Uhr schrieb Urs Liska :
>
> Hi Harm,
>
>
> Am 12.10.2018 um 18:58 schrieb Thomas Morley:
> > Hi Urs,
> >
> > not sure I understand correctly, probably something like below?
> >
> > one = \markup \score { d'1 }
&g
Am Fr., 12. Okt. 2018 um 17:52 Uhr schrieb Urs Liska :
>
> Hi,
>
> basically this is a follow-up question to the one where I needed to
> align a text over a slur. I wanted to apply the techniques I learned
> from your valuable help but ran against the next wall (or: I didn't see
> that there is no
Hi Urs,
sorry for the late reply.
Right now I've a cold (not working in my regular job), so I've more
time to look into lilypond-tasks.
While waiting for a guile-complie to finish...
Am So., 30. Sep. 2018 um 12:01 Uhr schrieb Urs Liska :
> Creating a new articulation (or overwriting the definiti
Am Fr., 12. Okt. 2018 um 09:59 Uhr schrieb Urs Liska :
> What is 'interval-center'? Grepping the source doesn't show a
> definition, so I'd assume it's in the C++ domain? I haven't found
> anything about that in the documentation (or through Google).
Hi Urs,
~/lilypond-git (master)$ git grep "in
Am Fr., 12. Okt. 2018 um 08:10 Uhr schrieb Jan-Peter Voigt :
>
> Hello Sebastian,
>
> what do you mean with "return"? Do want to add the score immediatly or
> do you want to return an object containing both?
> You used the parser-location arguments in your scheme-function, so I
> guess you are usin
Am Di., 9. Okt. 2018 um 16:54 Uhr schrieb Urs Liska :
>
> Hi,
>
> I have a custom \path markup, implemented as an event function.
>
> This works well, but when I add a slur I don't manage to get it to
> behave it properly. What I want is to print the vertical lines and then
> outside the slur, just
Am Di., 9. Okt. 2018 um 00:47 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Well, I'm a little confused about translators and translator-creators
> > (I use the hyphen to make the wording more obvious).
> > Not the least reason is:
> > #(
Am Mo., 8. Okt. 2018 um 23:50 Uhr schrieb David Kastrup :
> ly:get-all-translators gets the _globally_ registered translators, those
> you can access with a _string_ as reference (should be a symbol,
> really).
>
> > So _registering_ them makes testI/II translators,
>
> No, translator creators (wh
Am Mo., 8. Okt. 2018 um 12:28 Uhr schrieb Jogchum Reitsma :
>
> Op 06-09-18 om 09:43 schreef Thomas Morley:
> > 2018-09-05 11:15 GMT+02:00 Jogchum Reitsma :
> >> Hi,
> >>
> >> The first bar of part 5: Ecce gratum, from Orff's Camina Burana states
901 - 1000 of 3935 matches
Mail list logo
