Re: Getting readline to work in scheme-sandbox

Hi Knute, I'm currently working on this problem. A library called libguilereadline, that comes with guile, does provide the interface to the libreadline library. The version we ship with our packages, however, seems to be broken somehow. There are some ways to get around this. Do you have

Re: Unusual cross-staff stem in Bartók

Thank you. This seems to do it nicely. I’d not submitted a MWE because I didn’t have anything I was confident was even the right sort of starting point and was looking for a pointer where to even start. Fortunately (for me), you filled the gap very nicely with this. I’ll need to adapt it for

Re: Unusual cross-staff stem in Bartók

p.s. Maybe this helps? \version "2.19.83" \layout { \context { \PianoStaff \consists #Span_stem_engraver } } { \new PianoStaff << \new Staff { bes'8[ ] } \new Staff { \clef bass \voiceOne \autoBeamOff \crossStaff { \tweak

Re: Unusual cross-staff stem in Bartók

Hi Arle, > How would I achieve this effect? All of the crossStaff examples I find have > the note heads on the same side of the stem and the stem extends above or > below one of the notes. I’ve tried to get them to work with moderate success, > but not with this arrangement. Please always

Distance of a grob from its reference point

Hello. Is there a way to obtain, for a given grob 1) its *calculated* distance from its reference point? (from what I see, the reference Y of an OttavaBracket is the middle line of the associated staff...) I tried ly:grob-staff-position (see the snippet below), but it doesn't seem to give this

Re: lilypond-user Digest, Vol 206, Issue 45

Sic scripsit Aaron Hill: > In your larger document, do you use \autoBeamOff? This was the problem. I did’t recall turning autoBeam off so I didn’t think to check for it. Sic scripsit Kieran MacMillan: > Well, that would follow "traditional" (meaning pre-1900) engraving rules for > vocal

Re: Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

Hi Arle, > Seems this is a bug unless there is a reason why lyrics should follow manual > beaming rather than slurs when autoBeam is off. Can anyone tell me whether I > should log this? Well, that would follow "traditional" (meaning pre-1900) engraving rules for vocal writing, when melismas

Lyric misalignment solved. Was Re: Lyric misalignment and beaming?

Thanks very much to Carl Sorenson for a response that got me to start paring things down even more and led me to find the problem in my score where I didn’t previously look. Took a while Basically, if autoBeam is off (somehow I’d turned it off outside a variable where I was defining things),

Re: How to increase shift dynamic and end of hairpin

Hi Guy, > You sir are a gentleman and a scholar! Well, ½ of each means I’m a total of 1. ;) > I didn't want to say anything, but each of the three previous suggestions > worked for the MWE, but when applied to my score either either did not work > at all, or only worked for some of the areas

Getting readline to work in scheme-sandbox

I recently discovered the scheme-sandbox in LilyPond and I want to get line editing to work. In scheme-sandbox.ly the comments say: % One typical thing you might want to put there is % (use-modules (ice-9 readline)) % (activate-readline) % in order to activate command line editing for

Re: Lyric misalignment and beaming?

On 2020-01-13 3:45 pm, Arle Lommel wrote: Does anyone have any idea what I should check to resolve this problem? I’ve tried everything I can think of with no luck. According to the docs, manual beaming will create melismata when automatic beaming is disabled. In your larger document, do you

Re: Lyric misalignment and beaming?

From: Arle Lommel Date: Monday, January 13, 2020 at 4:45 PM To: Subject: Lyric misalignment and beaming? Got a head scratcher here. Using 2.19.83, I’ve run into a problem where I *cannot* create a minimal example: The minimal example works exactly as it should and it is only in context

Lyric misalignment and beaming?

Got a head scratcher here. Using 2.19.83, I’ve run into a problem where I *cannot* create a minimal example: The minimal example works exactly as it should and it is only in context where things fail, but I have no idea what actually makes them fail, so I have no idea how to make a minimal

Syntax highlighting

Hi all, I'd like to add LilyPond syntax highlighting to highlight.js ( https://highlightjs.readthedocs.io/en/latest/ ) so that I can experiment with documentation tools such as mkDocs/readthedocs. Does anyone have any experience with this? Would it just be a matter of getting one of the current

Re: Shift up OttavaBracket

Sorry for the typo WRONG: 1) At this point, given that Y-offset can't be used for properly offsetting (\offset) the OttavaBracket (unless you use a ruler and place its reference point of the bracket, which is very tedious), is there any any other property that can be used? CORRECT 1) At this

Re: Shift up OttavaBracket

Thank you for the clarification. 1) At this point, given that Y-offset can't be used for properly offsetting (\offset) the OttavaBracket (unless you use a ruler and place its reference point of the bracket, which is very tedious), is there any any other property that can be used? 2) Is there a

Re: Mailing list duplicates

Aaron Hill writes: > On 2020-01-13 12:58 pm, David Kastrup wrote: >> Uh, you are aware that you can easily configure your mailing list >> options to _not_ include you in mail you are already receiving via >> other >> headers? >> And lo and behold: no need to lecture anybody anymore. > > If I

Re: How to increase shift dynamic and end of hairpin

Kieren, You sir are a gentleman and a scholar! I didn't want to say anything, but each of the three previous suggestions worked for the MWE, but when applied to my score either either did not work at all, or only worked for some of the areas that needed the extended hairpin decrescendo.

Mailing list duplicates (was: Re: Shift up OttavaBracket)

On 2020-01-13 12:58 pm, David Kastrup wrote: Uh, you are aware that you can easily configure your mailing list options to _not_ include you in mail you are already receiving via other headers? And lo and behold: no need to lecture anybody anymore. If I were aware of this feature, I would

Re: Shift up OttavaBracket

Aaron Hill writes: > On 2020-01-13 11:38 am, Carl Sorensen wrote: >> I would like to request that we not use lilybin links for problematic >> code snippets. It places necessary information out of the context of >> the email. > > And I politely ask that folks only reply to the mailing list and

Re: Shift up OttavaBracket

From: Paolo Prete Date: Monday, January 13, 2020 at 1:33 PM To: Carl Sorensen Cc: Lilypond-User Mailing List Subject: Re: Shift up OttavaBracket Does it mean that similar issues can happen with the same property applied to other grobs, like DynamicLineSpanner ? Since the Y-offset property

Re: Shift up OttavaBracket

Does it mean that similar issues can happen with the same property applied to other grobs, like DynamicLineSpanner ? Thanks, Best P On Mon, Jan 13, 2020 at 9:20 PM Carl Sorensen wrote: > > > On 1/13/20, 12:25 PM, "Kieren MacMillan" > wrote: > > Hi Paolo (et al.), > > > Well, I

Re: Shift up OttavaBracket

On 1/13/20, 12:25 PM, "Kieren MacMillan" wrote: Hi Paolo (et al.), > Well, I investigated as well. I think that the only way to solve this is to use the combination > Y-offset + \offset + 2.19 > As you can see, this seems to work in 2.19 >

Re: Shift up OttavaBracket

You are right, but a bad behavior happens with 2.19 too. See: { c'\f \once \offset Y-offset -0.3 DynamicLineSpanner c'\f r2 \ottava #1 c8 8\ottava #0 r4 \once \offset Y-offset 1 Staff.OttavaBracket \ottava #1 c8 8 \ottava #0 r4 \ottava #1 c8\(

Re: Shift up OttavaBracket

From: Paolo Prete Date: Monday, January 13, 2020 at 12:21 PM To: David Nalesnik Cc: Kieren MacMillan , Aaron Hill , Lilypond-User Mailing List , Carl Sorensen Subject: Re: Shift up OttavaBracket Well, I investigated as well. I think that the only way to solve this is to use the

Re: Shift up OttavaBracket

On 2020-01-13 11:38 am, Carl Sorensen wrote: I would like to request that we not use lilybin links for problematic code snippets. It places necessary information out of the context of the email. And I politely ask that folks only reply to the mailing list and not include individual user

Re: Shift up OttavaBracket

David Nalesnik wrote: I'm going to investigate this. \offset requires a grob property which is assigned a default value in define-grobs.scm (from which file the IR grob reference pages are generated). This value is 0.46, inaccessible at the top of axis-group-interface.cc. Cheers, Robin

Re: Shift up OttavaBracket

From: Paolo Prete Date: Monday, January 13, 2020 at 12:29 PM To: Kieren MacMillan Cc: David Nalesnik , Aaron Hill , Lilypond-User Mailing List , Carl Sorensen Subject: Re: Shift up OttavaBracket You are right. I made the same test one minute ago :-) Well, definitely a bug. Is there a

Re: Shift up OttavaBracket

You are right. I made the same test one minute ago :-) Well, definitely a bug. Is there a workaround for this at least in 2.19 ? Otherwise the OttavaBracket interface is almost unusable (except for the extra-offset property) On Mon, Jan 13, 2020 at 8:25 PM Kieren MacMillan <

Re: Shift up OttavaBracket

Hi David, > I don't see the solution in creating a larger set of commands > that work in some circumstances. Agreed, so as long as we don’t in fact need/want two functions (e.g., \offset and \reposition) that are *expected* to work differently (e.g., one takes intermediate grobs into account

Re: Shift up OttavaBracket

Hi Paolo (et al.), > Well, I investigated as well. I think that the only way to solve this is to > use the combination > Y-offset + \offset + 2.19 > As you can see, this seems to work in 2.19 > http://lilybin.com/yb5u35/12 Not always: Cheers, Kieren.

Re: Shift up OttavaBracket

Well, I investigated as well. I think that the only way to solve this is to use the combination Y-offset + \offset + 2.19 As you can see, this seems to work in 2.19 http://lilybin.com/yb5u35/12 And it doesn't work in 2.18. Correct me if I'm wrong: this is currently the *only* proper way to

Re: Shift up OttavaBracket

Kieren MacMillan writes: > Hi David, > >> What's wrong with \offset itself? > > Nothing, I suppose, as long as it worked consistently with all grobs > (which it clearly doesn’t currently). Well, I don't see the solution in creating a larger set of commands that work in some circumstances. If

Re: Shift up OttavaBracket

On Mon, Jan 13, 2020 at 12:29 PM Kieren MacMillan wrote: > > Hi David, > > >> You’d like a command like \offset (say, \reposition) which tweaks the > >> position of a grob > >> from its final [calculated] position, pushing other grobs (in X or Y > >> directions) as necessary? > > > \offset

Re: Shift up OttavaBracket

Hi David, >> You’d like a command like \offset (say, \reposition) which tweaks the >> position of a grob >> from its final [calculated] position, pushing other grobs (in X or Y >> directions) as necessary? > \offset would do exactly that if there were a single property of > OttavaBracket which

Re: Shift up OttavaBracket

Hi David, > What's wrong with \offset itself? Nothing, I suppose, as long as it worked consistently with all grobs (which it clearly doesn’t currently). Best, Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www.kierenmacmillan.info ‣ email:

Re: Shift up OttavaBracket

Hi, On Mon, Jan 13, 2020 at 12:07 PM Kieren MacMillan wrote: > > Hi Paolo, > > > The OttavaBracket is already pretty well positioned by Lilypond itself, and > > it should be tuned, if necessary, only with that small values. And if you > > do this, and you don't want to use the extra-offset

Re: Shift up OttavaBracket

Kieren MacMillan writes: > Hi Paolo, > >> The OttavaBracket is already pretty well positioned by Lilypond > itself, and it should be tuned, if necessary, only with that small > values. And if you do this, and you don't want to use the extra-offset > property, you are forced to use the ruler in

Re: Shift up OttavaBracket

Hi Paolo, > The OttavaBracket is already pretty well positioned by Lilypond itself, and > it should be tuned, if necessary, only with that small values. And if you do > this, and you don't want to use the extra-offset property, you are forced to > use the ruler in the way I explained... So to

RE: metronome-mark-alignment

> -Original Message- > From: David Kastrup [mailto:d...@gnu.org] > Sent: Monday, January 13, 2020 7:35 AM > To: Daniel Rosen > Cc: Thomas Morley ; lilypond-user Mailing List > (lilypond-user@gnu.org) ; David Nalesnik > > Subject: Re: metronome-mark-alignment > > That is entirely my

Re: Shift up OttavaBracket

On Mon, Jan 13, 2020 at 4:36 PM Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Paolo, > > > But it doesn't work in many cases. For example, in my snippet I'm forced > to use a ruler If I want to shift the bracket exactly +2 staff-spaces more. > Then I have to put the starting point

Re: How to increase shift dynamic and end of hairpin

Hi Guy, > Sorry, Knute -- Harm's suggestion is less work LOL Even less work is to have David K’s \after function in your toolbox: \version "2.19.83" \language "english" after = #(define-music-function (parser location t e m) (ly:duration? ly:music? ly:music?) #{ \context

Re: hide Stuff

Am 13.01.20 um 16:02 schrieb bb: I need the Stuff only for midi output and want to hide it from the pdf. Is it possible? regards Yes, you can use several \score blocks or the \tag command.

Re: Shift up OttavaBracket

Hi Paolo, > But it doesn't work in many cases. For example, in my snippet I'm forced to > use a ruler If I want to shift the bracket exactly +2 staff-spaces more. Then > I have to put the starting point of the ruler at the reference point of the > staff, find the distance between that starting

Re: Shift up OttavaBracket

Hi Robin, as said in the previous post, I tried outside-staff-padding too. And explained the issues in this case too. It does the job only *if reset* http://lilybin.com/yb5u35/5 And this "0" reset forces the user to set that property before any calculation, which is not good. best, Paolo On

Re: Shift up OttavaBracket

Paolo Prete wrote: (A) + (B) make me suspect that the whole OttavaBracket interface is buggy. It may not be exactly what you want, but I have the feeling that you haven't tried outside-staff-padding. http://lilypond.org/doc/v2.19/Documentation/internals/outside_002dstaff_002dinterface

Re: Shift up OttavaBracket

On Mon, Jan 13, 2020 at 3:35 PM Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Paolo, > > > > > Not in my example: I know its reference point is exactly 10 spaces from > the reference point of the staff. ;) > > This happens because you have chosen a value that you know at a glance

hide Stuff

I need the Stuff only for midi output and want to hide it from the pdf. Is it possible? regards

Re: Shift up OttavaBracket

Hi Paolo, > Look at this: > http://lilybin.com/yb5u35/9 > As you can see, the result is the same if I set "2" or "0" for the Y-offset > property. That’s because neither 2 nor 0 is large enough to be outside the items in your example (e.g., the noteheads are at +4, and the slur is at an even

Re: Shift up OttavaBracket

On Mon, Jan 13, 2020 at 2:37 PM Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Paolo, > > > from what I read in the documentation > > http://lilypond.org/doc/v2.19/Documentation/learning/moving-objects > > ... there are two ways to place items like the OctaveBracket. > > > > 1) The

Re: Shift up OttavaBracket

Hi Paolo, > from what I read in the documentation > http://lilypond.org/doc/v2.19/Documentation/learning/moving-objects > ... there are two ways to place items like the OctaveBracket. > > 1) The first method is to use properties like "padding" (therefore: > staff-padding, outstide-staff-padding

Re: metronome-mark-alignment

Daniel Rosen writes: > As far as the Extending manual goes, though... I could be wrong, but > it seems to assume a basic working knowledge of how computer programs > and programming languages work that I simply don't have. Going through > it, I think to myself that I would need to have

Re: Shift up OttavaBracket

Hi Carl, from what I read in the documentation http://lilypond.org/doc/v2.19/Documentation/learning/moving-objects ... there are two ways to place items like the OctaveBracket. 1) The first method is to use properties like "padding" (therefore: staff-padding, outstide-staff-padding etc.). The