Re: slurs problem with voices

On Wed, May 1, 2024 at 10:55 PM Robert Garrigos wrote: > Oh this is a bit embarrassing, such a basic error….. sorry, I never > realized that the parenthesis needs to be right after the first note. > Nothing to be embarrassed about. It takes some getting used to. -- Knute Snortum

Re: slurs problem with voices

; Sent: Wednesday, May 1, 2024 2:15 PM > To: Robert Garrigos ; LilyPond Users > > Subject: Re: slurs problem with voices > > On 01/05/2024 21:57, Robert Garrigos wrote: >> >> Why is not the first example working? I tried with explicit voicing with the >> same

RE: slurs problem with voices

024 2:15 PM To: Robert Garrigos ; LilyPond Users Subject: Re: slurs problem with voices On 01/05/2024 21:57, Robert Garrigos wrote: Why is not the first example working? I tried with explicit voicing with the same results. Thanks. Robert The slur starts at the d2 so must be placed wi

Re: slurs problem with voices

On Wed, May 1, 2024 at 1:59 PM Robert Garrigos wrote: > I have this music to engrave, note the slur: > [...] > Why is not the first example working? I tried with explicit voicing with > the same results. > Slurs in LilyPond are "post events", meaning they always go *after* the note. So if you

Re: slurs problem with voices

On 01/05/2024 21:57, Robert Garrigos wrote: Why is not the first example working? I tried with explicit voicing with the same results. Thanks. Robert The slur starts at the d2 so must be placed with that note following the pitch and duration, { d4 d2( | \hideNotes ef8)} -- Timothy

Re: slurs problem with voices

Hi Robert, > I tried different approaches but cannot get that slur. \version "2.25.14" \language "english" global = { \key ef \minor \time 3/4 } \relative c' { \clef treble \global << { bf'4 cf2 \tweak staff-position #5.1 ~ | 8 8 r8 r8 } \\ { d4 d2( | \hideNotes ef8) }

Re: Slurs within chords, and dotted notes

On 1/7/2024 4:11 PM, Xavier Scheuer wrote: \once \override Dots.avoid-slur = #'ignore (Dots instead of Slur) Thank you!  That’s what I was misunderstanding. —Joel

Re: Slurs within chords, and dotted notes

On Sun, 7 Jan 2024 at 21:35, Joel C. Salomon wrote: > > Reposting for clarity as to what I’m asking. > > In the second case below, instead of the slur attaching to the specific note, it moves vertically—I assume, to avoid collision with the duration dot. (Though it’s interesting that a tie does

Re: Slurs within chords, and dotted notes

Hello Joel You can shape the Slur manually, like so: \version "2.25.11" \fixed c' {   % undotted note: slur attaches correctly   2   |   % dotted note: slur is moved vertically   \shape #'((1 . 0.5) (0.5 . 0.3) (0.5 . 0.3) (0 . 0)) Slur %adjusting the numbers control the four control points

Re: Slurs within chords, and dotted notes

Reposting for clarity as to what I’m asking. In the second case below, instead of the slur attaching to the specific note, it moves vertically—I assume, to avoid collision with the duration dot.  (Though it’s interesting that a tie does not mind overlapping the dot, as in the fourth case.)

Re: Slurs within chords, and dotted notes

I should have been clearer.  The score I’m trying to emulate has slurs— |4.  | —and it’s the vertical movement of the slurs I’m trying to avoid. The fact that ties will overlap the note dots was a curiosity I found in trying to boil that down to a minimal working example. —Joel On 1/4/2024

RE: Slurs within chords, and dotted notes

Joel: Is this better? \fixed c' { 2 | 2. 4 | 2 q | 2. q4 | } Mark From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org On Behalf Of Joel C. Salomon Sent: Thursday, January 4, 2024 6:11 PM To: LilyPond Users Subject: Slurs within chords, and

Re: Slurs running into each other

Hi Peter, What can I do to avoid the outer slur colliding with the inner slurs? Code the inner slurs as Slurs and the *outer* slur as a PhrasingSlur, rather than the other way around (as you did): f4\p\( aes8( des16. c32) | c8.( bes32 aes) g8\) r8 | As a secondary question, I always

RE: slurs

David, Wow, so simple. Thank you for the remedy. Mark -Original Message- From: David Kastrup Sent: Saturday, September 16, 2023 2:44 PM To: Mark Stephen Mrotek Cc: lilypond-user@gnu.org Subject: Re: slurs "Mark Stephen Mrotek" writes: > Hello All: > > &

Re: slurs

"Mark Stephen Mrotek" writes: > Hello All: > > > > \version "2.22.2" > > \relative c'' { > > \slurDown 4 > > (bes16) (a c bes d c ees d) > > } Good example why it is a bad idea to use non-standard input formatting for aesthetic reasons: you lose a proper idea about what you are actually

Re: Slurs inside or outside beamed notes

Yes, Gould does say to always place a slur outside a beam. And I’m fine with that being Lilypond’s default behavior. But I’d love the ability to tell Lilypond to place slurs inside of beams (when possible). I do have one hymnal that prints slurs inside beams. I suspect that this choice was

Re: Slurs inside or outside beamed notes

At 11:47 13/02/2023 -0800, Aaron Hill wrote: I am quite used to LilyPond's default handling of slurs with them positioned next to the beam, but should I be following the source engraving with the slurs sit inside so they are closer to the note heads? Does Gould offer advice on this? To your

Re: Slurs not being followed in one vocal part

Hi Jon, Am 22.01.23 um 03:31 schrieb Jon Arnold: Thanks all! Separating the voices did fix the problem. I used this score a long time ago and then updated the layout, so I feel like an update several years ago must have changed the behavior, which is interesting. Compare: \version "2.24"

Re: Slurs not being followed in one vocal part

Thanks all! Separating the voices did fix the problem. I used this score a long time ago and then updated the layout, so I feel like an update several years ago must have changed the behavior, which is interesting. On Sat, Jan 21, 2023 at 8:27 PM David Wright wrote: > On Sun 22 Jan 2023 at

Re: Slurs not being followed in one vocal part

On Sun 22 Jan 2023 at 11:59:06 (+1100), Vaughan McAlley wrote: > On Sun, 22 Jan 2023, 10:32 Jon Arnold, wrote: > > > Hey folks- > > > > Can anyone tell me why the slurs are not being followed in the soprano > > part of the attached file? It first occurs in the 2nd half of bar 7, bottom > > of

Re: Slurs not being followed in one vocal part

On Sun, 22 Jan 2023, 10:32 Jon Arnold, wrote: > Hey folks- > > Can anyone tell me why the slurs are not being followed in the soprano > part of the attached file? It first occurs in the 2nd half of bar 7, bottom > of page 3. It seems to be related to the barLiner function I have (it goes > away

Re: Slurs not being followed in one vocal part

Dear Jon, I'm having trouble finding exactly what is the problem here. There is a slur between the dotted quarter and eighth note in bar 7, looking at that section in the soprano block it is being rendered as I thought it would be. Can you please create a minimal example that demonstrates the

Re: slurs across voices

Hi William and Knute, Thanks for your suggestions. It's nice to have two options. I like Knute's since I'm not very knowledgable about the engraver functions, which are a black box to me, while the method Knute proposes is easily understandable and only requires tweaking the measure in

Re: slurs across voices

Hey Jim, A little while ago I found this email which describes enabling the slur engraver on the staff level instead of voice level. Did you see this before, or give it a try? https://lists.gnu.org/archive/html/bug-lilypond/2012-03/msg00663.html \version "2.15.33" \score {   \new Staff {  

Re: slurs across voices

On Wed, Jul 27, 2022 at 8:29 AM Jim Cline wrote: > > I would like to create slurs between alternating notes across two voices > in this example: > > \version "2.20.0" > lower = >\relative c { > \time 3/4 >\clef bass ><<{\stemUp e''16\rest cis4 bis ais8~ais16}\\{\clef

Re: Slurs with "afterGrace"

\afterGrace g4(-+ {a16 g16)} } Richard On Sun, 2022-02-06 at 09:13 +, Alasdair McAndrew wrote: > Thank you very much!  (But in Australia, where I am, it is early > evening).   I did try that, but the difficulty is that I already have > a symbol attached to the note (which I should have

Re: Slurs with "afterGrace"

Sorry for the hour! It's a matter of parenthesis order and spaces: \relative c' { \afterGrace g4-+( { a16 g16) } } This works for me Il dom 6 feb 2022, 10:13 Alasdair McAndrew ha scritto: > Thank you very much! (But in Australia, where I am, it is early > evening). I did try that, but the

Re: Slurs with "afterGrace"

On Sun, 2022-02-06 at 10:00 +, Alasdair McAndrew wrote: > Thank you!  I would never have thought of putting the ending slur > inside > the grace note braces - but it works perfectly.  well I got there because it said the error was in column 30, i.e. the closing ) and I suspected that those

Re: Slurs with "afterGrace"

Thank you! I would never have thought of putting the ending slur inside the grace note braces - but it works perfectly. Again, thanks. Alasdair On Sunday 06 February 2022 20:53:12 (+11:00), Richard Shann wrote: > > > \afterGrace g4(-+ {a16 g16)} } > > Richard > > On Sun, 2022-02-06 at

Re: Slurs with "afterGrace"

Thank you very much! (But in Australia, where I am, it is early evening). I did try that, but the difficulty is that I already have a symbol attached to the note (which I should have included in my example): \afterGrace g4-+( {a16 g16} ) I've tried moving the beginning of the slur to

Re: Slurs with "afterGrace"

Good morning, try: \afterGrace g4( { a16 g16) } The slur event must be attached directly after the note. Rip_mus Il dom 6 feb 2022, 08:59 Alasdair McAndrew ha scritto: > This works: > g4( \grace {a16 g16}) > > making a slur which includes the grace notes. But in order to get the > right

Re: Slurs and multiple voice writing in piano music

Hello Gabriel, You need to be mindful of this: In Lilypond a tie or a slur has to remain in the Voice it started in. Now, the problem ist that << A \\ B >> does in fact create two new Voices. Thus you cannot really tie to it from the outside. The thing you want to do is to continue the voice

RE: Slurs and multiple voice writing in piano music

Gabriel, Perhaps: \version "2.22.0" \relative c' { <<{d4. \acciaccatura f8 e d4. a8_~ \stemDown | a2}\\ {s1 \stemUp b4 b8. b16}>> s2 | } Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Gabriel Borin Sent: Wednesday,

Re: Slurs into chords

Jonathan Danner writes: > Hello, > > Im trying to make a slur, or even possibly a gliss into a chord and > can’t quite get it right without getting a warning message. Can anyone > provide a way I can do either of these? > > melody = \relative c'' { > \global > r8 a\f c a c4 e8 e~|e d16 (c)

Re: Slurs into chords

Hi Jonathan, Im trying to make a slur, or even possibly a gliss into a chord and can’t quite get it right without getting a warning message. Can anyone provide a way I can do either of these? Please try to remove from your examples everything that plays no role for your problem; otherwise,

Re: slurs, shape en linebreaks

On Thu, 5 Mar 2020, David Nalesnik wrote: If a slur is crossing a linebreak, using the \shape function doesn't work properly anymore. You can address the parts individually in one \shape invocation. See code below. (...) Does the following help any? Yes, it does. Thanks. Didn't know

Re: slurs, shape en linebreaks

Hi Martin, On Thu, Mar 5, 2020 at 6:21 AM Martin Tarenskeen wrote: > > > Fixed typo in attachment, question unchanged. > > > On Thu, 5 Mar 2020, Martin Tarenskeen wrote: > > > > > Hi, > > > > If a slur is crossing a linebreak, using the \shape function doesn't work > > properly anymore. Are you

Re: slurs, shape en linebreaks

Fixed typo in attachment, question unchanged. On Thu, 5 Mar 2020, Martin Tarenskeen wrote: Hi, If a slur is crossing a linebreak, using the \shape function doesn't work properly anymore. I work around this by splitting the slur in two, and then use \shape twice to tweak the end of the

Re: Slurs in alternate endings

On 2020-01-15 11:19 am, Pastor Jim Neubauer wrote: I have an alternative ending that includes a slur. I know there is a \repeatTie command for ties across alternate endings, but is there anything as simple for slurs? Do you have a MWE you can provide along with possibly a picture or

Re: Slurs in FluidSynth

Dan Eble writes: > On Sep 14, 2019, at 17:15, David Kastrup wrote: >> >> Here is an example showing _slurs_. Are you telling me that the >> many instances of two slurred A4 notes are to be sounded only once? >> That would sound pretty awful, and this is a Bach urtext. > > Let’s not worry

Re: Slurs in FluidSynth

On Sep 14, 2019, at 17:15, David Kastrup wrote: > > Here is an example showing _slurs_. Are you telling me that the > many instances of two slurred A4 notes are to be sounded only once? > That would sound pretty awful, and this is a Bach urtext. Let’s not worry about bariolage. Instead, let’s

Re: Slurs in FluidSynth

On Sat, 14 Sep 2019, Karlin High wrote: Wait, sorry, I probably misunderstood. In this example... \version "2.19.83" \score { { c'4( c'4) c'2 } \layout { } \midi { } } ...the MIDI sounds as { c'4 c'4 c'2 } But as performed, it would sound like { c'2 c'2 } No. A slur is not a tie. {

Re: Slurs in FluidSynth

Karlin High writes: > On 9/14/2019 2:45 PM, Karlin High wrote: >> On 9/14/2019 2:40 PM, Dan Eble wrote: >>> getting FluidSynth to avoid attacking each note in a slur when >>> reading from a LilyPond-produced MIDI >> >> Would choice of sound font affect this? > > Wait, sorry, I probably

Re: Slurs in FluidSynth

On 9/14/2019 4:10 PM, Martin Tarenskeen wrote: No. A slur is not a tie. I stand corrected. Thanks! -- Karlin High Missouri, USA ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Slurs in FluidSynth

On 9/14/2019 2:45 PM, Karlin High wrote: On 9/14/2019 2:40 PM, Dan Eble wrote: getting FluidSynth to avoid attacking each note in a slur when reading from a LilyPond-produced MIDI Would choice of sound font affect this? Wait, sorry, I probably misunderstood. In this example... \version

Re: Slurs in FluidSynth

Dan Eble writes: > If anyone has had success getting FluidSynth to avoid attacking each > note in a slur when reading from a LilyPond-produced MIDI, I would be > grateful to learn how to do it. Why shouldn't it do that? Slurs affect where the previous note ends, not where the next note starts.

Re: Slurs in FluidSynth

On 9/14/2019 2:40 PM, Dan Eble wrote: getting FluidSynth to avoid attacking each note in a slur when reading from a LilyPond-produced MIDI Would choice of sound font affect this? -- Karlin High Missouri, USA ___ lilypond-user mailing list

Re: slurs and ties to end of bar

Hi Werner! Attached is a lilypond source that shows how to  use postscript to crop parts from a lilypond page. Obviously you still need to find a way to pass the right corner coordinates to the postscript code ... Knut \version "2.21.0" \pointAndClickOff #(set-global-staff-size 18)

Re: slurs and ties to end of bar

>> I have to typeset a bunch of snippets that contain ties and slurs >> either from a (not typeset) bar at the left or to a bar to the >> right (see attached example). What is the recommended way to do >> that gracefully? > > I'm still not sure what you're after and/or the wished workflow. See

Re: slurs and ties to end of bar

Am Do., 18. Juli 2019 um 07:38 Uhr schrieb Werner LEMBERG : > > > Folks, > > > I have to typeset a bunch of snippets that contain ties and slurs > either from a (not typeset) bar at the left or to a bar to the right > (see attached example). What is the recommended way to do that > gracefully? >

Re: slurs and ties to end of bar

>> What I imagine is a possibility to specify `front matter' and >> `back matter' that gets processed but not displayed, for example >> >>\relative c' { >> \frontmatter { f4( } >> g a b c >> \backmatter { d) } >>} >> >> which should be handled as >> >>\relative c' { >>

Re: slurs and ties to end of bar

Hi Werner, What I imagine is a possibility to specify `front matter' and `back matter' that gets processed but not displayed, for example \relative c' { \frontmatter { f4( } g a b c \backmatter { d) } } which should be handled as \relative c' { \partial 4 f4(

Re: slurs and ties to end of bar

> You mean you just want the slurs to extend before and after the > notes? Yes, but ... > Any reason you can't use \shapeII from openlilylib? ... I don't want to have a manual solution – but thanks for the suggestion. What I imagine is a possibility to specify `front matter' and `back matter'

Re: slurs and ties to end of bar

You mean you just want the slurs to extend before and after the notes? Any reason you can't use \shapeII from openlilylib? Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Slurs inside a beam

On Aug 12, 2018, at 8:24 AM, Thomas Morley wrote: > 2018-08-12 3:31 GMT+02:00 Andrew Bernard : >> Hi David, >> >> One way to do it: >> >> \version "2.19" >> >> { >> 8. 16 >> } >> >> >> From the Changes page: >> >> A new command \=X has been added – where ‘X’ can be any non-negative

Re: Slurs inside a beam

2018-08-12 3:31 GMT+02:00 Andrew Bernard : > Hi David, > > One way to do it: > > \version "2.19" > > { > 8. 16 > } > > > From the Changes page: > > A new command \=X has been added – where ‘X’ can be any non-negative integer > or symbol – so that a specific ‘id’ can be assigned to the start and

Re: Slurs inside a beam

Hi Aaron, All good. But I use \shapeII from the openlilylib library. There are some insoluble issues with it that crop up sometimes, but in general I hammer it heavily in use and it holds up well. There are a variety of ways to specify the shape, including using polar coordinates which is

Re: Slurs inside a beam

On 2018-08-11 13:30, David F. wrote: While we’re on the topic of bending slurs to our will, I’d like for slurred, beamed eighth notes to have the slur printed below or inside the beam. This works with a simple ^~ for ties. How might I accomplish this? The behavior I am after can also be

Re: Slurs inside a beam

Hi David, One way to do it: \version "2.19" { 8. 16 } >From the Changes page: A new command \=X has been added – where ‘X’ can be any non-negative integer or symbol – so that a specific ‘id’ can be assigned to the start and end of slurs and phrasing slurs. This is useful when simultaneous

Re: Slurs do not work with Larsen articulations

Noeck writes: > Hi Harm, > > IMHO that's a good explanation and according to the recurring questions > on this list, sth. that would be helpful. > > I like the "attached to the note" much better than "not enclosed in" > because the negative wording "not enclosed in" only

Re: Slurs do not work with Larsen articulations

Thomas Morley writes: > 2018-04-25 23:23 GMT+02:00 Carl Sorensen : >> >> >> On 4/25/18, 2:34 PM, "David Kastrup" wrote: >> >> So I see it more as a documentation challenge than a design failure. >> >> >> I agree, and I think we

Re: Slurs do not work with Larsen articulations

On 25.04.2018 23:29, Noeck wrote: c'8-1--(~\markup "what-ever-remark" c') The markup needs a hyphen. I'd suggest to drop the \markup here to make it simpler. In my personal rule set, the ~ goes last – but there is probably no reason for that … One thing does have to go last, and that is

Re: Slurs do not work with Larsen articulations

On 25.04.2018 12:48, foxfanfare wrote: But for instance in the Available Music Functions section, sometimes there is a small code exemple, sometime there isn't (almost evry time). I found personnaly clearer

Re: Slurs do not work with Larsen articulations

On 4/25/2018 5:03 PM, Robert Hickman wrote: Just including a note at the top of all of the pages "this is the learning manual and is intended to be read start to finish" would help clarify that. -- Karlin

Re: Slurs do not work with Larsen articulations

"As we try to make clear, the Learning Manual is intentionally not built for random access. The Notation Reference *is* built for random access." However it frequently shows up in google search results out of order and the way it is written mean that these pages often don't make sense. Just

Re: Slurs do not work with Larsen articulations

2018-04-25 23:23 GMT+02:00 Carl Sorensen : > > > On 4/25/18, 2:34 PM, "David Kastrup" wrote: > > So I see it more as a documentation challenge than a design failure. > > > I agree, and I think we can improve the documentation. > > Carl > > startSlur,

Re: Slurs do not work with Larsen articulations

Hi Harm, IMHO that's a good explanation and according to the recurring questions on this list, sth. that would be helpful. I like the "attached to the note" much better than "not enclosed in" because the negative wording "not enclosed in" only tells what you _should not_ do and not what you

Re: Slurs do not work with Larsen articulations

On 4/25/18, 2:34 PM, "David Kastrup" wrote: So I see it more as a documentation challenge than a design failure. I agree, and I think we can improve the documentation. Carl ___ lilypond-user mailing list

Re: Slurs do not work with Larsen articulations

Carl Sorensen writes: > On 4/25/18, 1:46 PM, "Thomas Morley" wrote: > > > There is a point that I was trying to make with these changes, > > without jumping right out and saying it (because I couldn’t find > > a good place to jump

Re: Slurs do not work with Larsen articulations

On 4/25/18, 1:46 PM, "Thomas Morley" wrote: > There is a point that I was trying to make with these changes, without jumping right out and saying it (because I couldn’t find a good place to jump out and say it). In LilyPond, *ALL* extra things that apply

Re: Slurs do not work with Larsen articulations

Thomas Morley writes: > Hi Carl, > > 2018-04-25 13:26 GMT+02:00 Carl Sorensen : >> Evan, >> >> Thanks for your feedback. Feedback from new users is important for >> improving the Learning Manual. > > Indeed. > >> There is a point that I was trying

Re: Slurs do not work with Larsen articulations

Thomas Morley writes: > Sometimes I think using "(" and ")" to indicate slurs leads to > misunderstandings, they are read as a sort of brackets (they are not) > Ofcourse it's conveniant, but I wonder, if doing like below would lead > to the same misinterpretation: > >

Re: Slurs do not work with Larsen articulations

ieren MacMillan > <kieren_macmil...@sympatico.ca>, David Kastrup <d...@gnu.org>, Lilypond-User > Mailing List <lilypond-user@gnu.org> > Subject: Re: Slurs do not work with Larsen articulations > > > > > > That sounds good to me. > > Thanks fo

Re: Slurs do not work with Larsen articulations

Hi Carl, 2018-04-25 13:26 GMT+02:00 Carl Sorensen : > Evan, > > Thanks for your feedback. Feedback from new users is important for improving > the Learning Manual. Indeed. > There is a point that I was trying to make with these changes, without > jumping right out and

Re: Slurs do not work with Larsen articulations

r Mailing List <lilypond-user@gnu.org> Subject: Re: Slurs do not work with Larsen articulations That sounds good to me. Thanks for the feedback. In case it's not clear, my pseudo-objection to the wording +Note that @code{[} and @code{]} do not enclose the notes to be +slurred. is that the ( an

Re: Slurs do not work with Larsen articulations

\On 4/25/18, 12:16 PM, "Robert Hickman" wrote: I assume that the project still has contributors who work on the documentation? It dosn't really matter if they are the original authors of it. I'm not saying that it is terible, but making some points

Re: Slurs do not work with Larsen articulations

On Wed, Apr 25, 2018 at 6:26 AM, Carl Sorensen wrote: > Thanks for your feedback. Feedback from new users is important for > improving the Learning Manual. > Just so we're on the same page, I've been an occasional LilyPond user for many many years now; I was just saying

Re: Slurs do not work with Larsen articulations

On 4/25/18, 12:16 PM, "Robert Hickman" wrote: It is quite apparent that this wasn't written for random access and I feel that websites are much more effective and user friendly if they are. As we try to make clear, the Learning Manual is intentionally not

Re: Slurs do not work with Larsen articulations

It is quite apparent that this wasn't written for random access and I feel that websites are much more effective and user friendly if they are. "It's easy to wave your hands and say "not good, I want you all to redo it better" but that will not result in changes getting done," I assume that the

Re: Slurs do not work with Larsen articulations

Robert Hickman writes: > On 25 April 2018 at 18:44, Karlin High wrote: >> On 4/25/2018 12:38 PM, Kieren MacMillan wrote: >>> >>> Hi Robert, >>> Many pages duplicate content or say 'please read page xyz first' because I recognise that people

Re: Slurs do not work with Larsen articulations

On 25 April 2018 at 18:44, Karlin High wrote: > On 4/25/2018 12:38 PM, Kieren MacMillan wrote: >> >> Hi Robert, >> >>> Many pages duplicate content or say 'please read page xyz first' >>> because I recognise that people will enter the site from any page >>> and I cannot make

Re: Slurs do not work with Larsen articulations

On 4/25/2018 12:38 PM, Kieren MacMillan wrote: Hi Robert, Many pages duplicate content or say 'please read page xyz first' because I recognise that people will enter the site from any page and I cannot make any assumptions about what they already know. This is a great suggestion. Perhaps you

Re: Slurs do not work with Larsen articulations

Hi Robert, > Many pages duplicate content or say 'please read page xyz first' > because I recognise that people will enter the site from any page > and I cannot make any assumptions about what they already know. This is a great suggestion. Perhaps you can contribute such links as you continue

Re: Slurs do not work with Larsen articulations

" In the context of the Learning Manual, pitches and durations are introduced in section 1.2.1. It seems like it would be unfriendly to clutter that section with a discussion about modifications coming after the note. " The problem with this attitude is that it is a website and people will enter

Re: Slurs do not work with Larsen articulations

Sorry to jump in here as someone who just (re-)signed up for the list, but I actually find +Note that @code{[} and @code{]} do not enclose the notes to be +slurred. potentially confusing. I would say something like either "Note that the first note of the slur appears before the opening @code{(}"

Re: Slurs do not work with Larsen articulations

, Kieren MacMillan <kieren_macmil...@sympatico.ca>, David Kastrup <d...@gnu.org>, Lilypond-User Mailing List <lilypond-user@gnu.org> Subject: Re: Slurs do not work with Larsen articulations Sorry to jump in here as someone who just (re-)signed up for the list, but I actually find

Re: Slurs do not work with Larsen articulations

David Kastrup wrote > That's actually the killer reason. There are a few places where > documentation strings get drawn into the manual, and those documentation > strings can be used more and less tersely. They should be verbose > enough to be useful which may include examples (examples take up

Re: Slurs do not work with Larsen articulations

Simon Albrecht writes: > On 24.04.2018 22:02, foxfanfare wrote: >> I missed >> more exemples in the huge "Internal Manual"! > > I don’t think any will be added, for two reasons: > The technical reason is that the Internals Reference is auto-generated > from the program

Re: Slurs do not work with Larsen articulations

Here's a proposed patch for the documentation. I haven't posted it on Rietveld because I'm having some problems with make doc (that are unrelated to this change). -- a/Documentation/learning/common-notation.itely +++ b/Documentation/learning/common-notation.itely @@ -275,6 +275,9 @@ Notation

Re: Slurs do not work with Larsen articulations

On 24.04.2018 22:02, foxfanfare wrote: I missed more exemples in the huge "Internal Manual"! I don’t think any will be added, for two reasons: The technical reason is that the Internals Reference is auto-generated from the program code, so possibilities to manually add stuff are very

Re: Slurs do not work with Larsen articulations

If I may intervene here: about the documentation quality, I'd must say I disagree. As I said in another post, I find it (globaly) very high ended. I started LP about 3 weeks from now, I'm just finishing the full notation PDF book of almost 900 pages! Of course, I still have a lot more to learn

Re: Slurs do not work with Larsen articulations

On Tue, Apr 24, 2018 at 1:58 PM, David Kastrup wrote: > Except when it's a clever way of getting rid of an unwanted semicolon. > Or in this case, create a semicolon hole, a negative semicolon count. > Add one semicolon, and none remains. :) Clean forgot about macros in C. I stand

Re: Slurs do not work with Larsen articulations

Karlin High writes: > On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote: >> The only way to create good documentation is to listen to your users >> problems and progressively make improvements. > > Yes, exactly! The LilyPond community has a

Re: Slurs do not work with Larsen articulations

Robert Hickman writes: > The only way to create good documentation is to listen to your users > problems and progressively make improvements. "your users" paints a false dichotomy. There is no fundamental difference between you and anybody else writing documentation. --

Re: Slurs do not work with Larsen articulations

Hi Robert (and Karlin), >> Whatever help I would get from the C-people, getting rid >> of the semicolons would not be part of it. > > This is **NOT** the point I am making No, of course not — I would imagine Karlin was simply responding to your comment > Personally I prefer the syntax

Re: Slurs do not work with Larsen articulations

On 24 April 2018 at 16:18, Karlin High wrote: > On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote: >> The only way to create good documentation is to listen to your users >> problems and progressively make improvements. > > Yes, exactly! The

Re: Slurs do not work with Larsen articulations

On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote: > The only way to create good documentation is to listen to your users > problems and progressively make improvements. Yes, exactly! The LilyPond community has a process for this.

Re: Slurs do not work with Larsen articulations

The only way to create good documentation is to listen to your users problems and progressively make improvements. On 24 April 2018 at 14:49, Kieren MacMillan wrote: > Hi Robert, > >> If I misinterpreted it you can guarantee >> that other people are also doing so.

Re: Slurs do not work with Larsen articulations

Hi Robert, > If I misinterpreted it you can guarantee > that other people are also doing so. Well, that’s a faulty generalization… ;) … but IMO more clarity is always better. As they say: "Patches [to the docs] are always gratefully accepted." Cheers, Kieren.

Re: Slurs do not work with Larsen articulations

> The example looks pretty clear to me. "marked with" is not really > synonymous with "surrounded with" in my book even though it could be > more explicit about just how the marks are supposed to be made. > If I misinterpreted it you can guarantee that other people are also doing so. The

  1   2   3   4   >