Re: Slashed grace with long slur
It worked for me to move the \slurUp command inside the \shlashedGrace, as in:
\slashGrace { \slurUp e8( } d b)
Kristin
On Sun, Jan 24, 2016, at 08:51 AM, Ralph Palmer wrote:
> Hi, All -
>
> I'm running Ly 2.19.33 under Win7.
>
> I'm trying to transcribe a slashed grace note with a long slur, as in
> the attachment slur.png. I've been unable to get the slur to stay up.
> I've tried \slurUp in conjunction with both \slashedGrace and
> \acciaccatura with no success. The attached .ly and .pdf files show
> the results. \slurUp does not work on a normal acciaccatura, either.
>
> Is my only option to use \shape ? Using \shape should work, I
> believe, but will probably mean a *lot* of adjustment - I need to
> produce almost forty of these.
>
> I'm grateful for any assistance,
>
> Ralph
>
> --
> Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com
> _
> lilypond-user mailing list lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user Email had 3
> attachments:
> * slashed grace with slur test.ly 1k (text/lilypond-source)
> * slashed grace with slur test.pdf 55k (application/pdf)
> * Slur.png 4k (image/png)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Slashed grace with long slur
I'm sorry, I typoed the command both places:
\slashedGrace { \slurUp e8( } d b)
K.
--
Kristin Rollins
kris...@verumsolum.com
Portsmouth, VA
On Sun, Jan 24, 2016, at 09:08 AM, Kristin Rollins wrote:
> It worked for me to move the \slurUp command inside the \shlashedGrace, as in:
>
> \slashGrace { \slurUp e8( } d b)
>
> Kristin
>
>
>
> On Sun, Jan 24, 2016, at 08:51 AM, Ralph Palmer wrote:
>> Hi, All -
>>
>> I'm running Ly 2.19.33 under Win7.
>>
>> I'm trying to transcribe a slashed grace note with a long slur, as in the
>> attachment
>> slur.png.
>> I've been unable to get the slur to stay up. I've tried
>> \slurUp
>> in conjunction with both
>> \slashedGrace
>> and
>> \acciaccatura
>> with no success.
>> The attached .ly and .pdf files show the results. \slurUp does not work on a
>> normal acciaccatura, either.
>>
>> Is my only option to use
>> \shape ?
>> Using \shape should work, I believe, but will probably mean a *lot* of
>> adjustment - I need to produce almost forty of these.
>>
>> I'm grateful for any assistance,
>>
>> Ralph
>>
>> --
>> Ralph Palmer
>> Brattleboro, VT
>> USA
>> palmer.r.vio...@gmail.com
>> _
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>> Email had 3 attachments:
>> * slashed grace with slur test.ly
>> 1k (text/lilypond-source)
>> * slashed grace with slur test.pdf
>> 55k (application/pdf)
>> * Slur.png
>> 4k (image/png)
>
> _
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line break anywhere-but-not-here ?
On Sun, Feb 28, 2016, at 07:17 AM, Malte Meyn wrote: > Am 28.02.2016 um 13:06 schrieb Graham King: > > Is there any way to > > tell her: "put line breaks wherever you wish, but_not here_" ? > > How about \noBreak? ;) That was my first instinct, and I found it in the docs, but when I took the code shared with the original question and inserted the \noBreak command, it did not appear to have any effect on the output on my installation of 2.19.36 Kristin -- Kristin Rollins kris...@verumsolum.com Portsmouth, VA ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line break anywhere-but-not-here ?
On Sun, Feb 28, 2016, at 07:24 AM, Malte Meyn wrote:
> Probably you put it at the wrong place. It has to be put at the place
> where the break would be. The following works for me:
>
> \version "2.19.36"
>
> \relative c'' {
>\repeat unfold 10 { c1 }
>c2\fermata r4 \breathe \tempo "Tempo Primo" r4 | \noBreak
>\repeat unfold 14 { c1 }
> }
I was just about to return sheepishly after noticing that it had taken
effect and my eyes had not taken note of the change in my haste.
My apologies.
Kristin
--
Kristin Rollins
kris...@verumsolum.com
Portsmouth, VA
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Using Google to find documentation (was Re: naturalize pitches)
Searching with Google tends to be more effective for me in solving my issues with learning LilyPond and troubleshooting my work, especially with the ability to simply type the query into the address bar of my browser. (Though that is after I took the time to go through the learning manual and at least review what documentation is available to become familiar with it.) The one thing I have learned, after a couple of instances of finding the wrong version's documentation (or multiple versions of the documentation): I always start my search with: lilypond 2.19 and then my search terms. That will usually make the official documentation for the proper version come to the top of the search results and lower the risk of finding answers that relate to previous versions. Kristin -- Kristin Rollins kris...@verumsolum.com Portsmouth, VA On Fri, Mar 18, 2016, at 06:44 AM, David Kastrup wrote: > That's one reason why it makes sense to look at the accompanying > documentation of a LilyPond installation rather than search blindly for > something on the net (which will frequently deliver outdated information > and infrequently advance information). ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
