Evan Driscoll writes:
> Great, thanks! I tried something like that, but never had the space between
> the offset amount and following _, which in retrospect makes sense but I
> didn't think of at the time. I also agree in that context just the X-offset
> version looks better and now I'm using tha
I think \tweak instead of the overrides does get the position change result
you're after
http://lilybin.com/vhf35h/17
> On 12 Apr 2022, at 23:02, Evan Driscoll wrote:
>
>
> Great, thanks! I tried something like that, but never had the space between
> the offset amount and following _, whic
Great, thanks! I tried something like that, but never had the space between
the offset amount and following _, which in retrospect makes sense but I
didn't think of at the time. I also agree in that context just the X-offset
version looks better and now I'm using that in one of the two places it
ap
On 2022-04-12 12:25 pm, Evan Driscoll wrote:
http://lilybin.com/vhf35h/5 for example.
I have a note that has two text decorations on it, c^"pizz"_"marc", as
well
as a dynamic \f.
By default everything gets stacked (http://lilybin.com/vhf35h/6), but
that
gets really busy -- there's actually a
http://lilybin.com/vhf35h/5 for example.
I have a note that has two text decorations on it, c^"pizz"_"marc", as well
as a dynamic \f.
By default everything gets stacked (http://lilybin.com/vhf35h/6), but that
gets really busy -- there's actually a tempo marking and rehearsal mark at
that place as
David Kastrup writes:
> Aaron Hill writes:
>
>> On 2020-07-28 10:15 am, David Kastrup wrote:
>>> Aaron Hill writes:
>>>
Feels like a hack, but would this help?
\version "2.20.0"
loremIpsum = \markuplist {
\bold { Lorem ipsum } dolor sit amet,
\italic cons
Aaron Hill writes:
> On 2020-07-28 10:15 am, David Kastrup wrote:
>> Aaron Hill writes:
>>
>>> Feels like a hack, but would this help?
>>>
>>> \version "2.20.0"
>>> loremIpsum = \markuplist {
>>> \bold { Lorem ipsum } dolor sit amet,
>>> \italic consectetur adipiscing elit.
>>> }
>>> \
On 2020-07-28 10:15 am, David Kastrup wrote:
Aaron Hill writes:
Feels like a hack, but would this help?
\version "2.20.0"
loremIpsum = \markuplist {
\bold { Lorem ipsum } dolor sit amet,
\italic consectetur adipiscing elit.
}
\markup {
\override #'(line-width . 40)
\wordwrap {
Aaron Hill writes:
> Feels like a hack, but would this help?
>
>
> \version "2.20.0"
>
> loremIpsum = \markuplist {
> \bold { Lorem ipsum } dolor sit amet,
> \italic consectetur adipiscing elit.
> }
>
> \markup {
> \override #'(line-width . 40)
> \wordwrap { $@loremIpsum $@loremIpsum
"Mike Stickles"
Subject: Re: Combining multiple markups into a single, word-wrappable one?
Mike Stickles writes:
> In the weekly service files I'm generating for my church, near the end
> is the text for a dismissal prayer. This prayer pretty much always has
> the same b
Mike Stickles writes:
> In the weekly service files I'm generating for my church, near the end
> is the text for a dismissal prayer. This prayer pretty much always has
> the same beginning and ending text, but a section in the middle varies
> from service to service. I've been trying (without su
On 2020-07-27 7:58 pm, Mike Stickles wrote:
In the weekly service files I'm generating for my church, near the end
is the text for a dismissal prayer. This prayer pretty much always has
the same beginning and ending text, but a section in the middle varies
from service to service. I've been tryin
In the weekly service files I'm generating for my church, near the end
is the text for a dismissal prayer. This prayer pretty much always has
the same beginning and ending text, but a section in the middle varies
from service to service. I've been trying (without success) to encode
these in var
Hi Urs,
On Mon, Sep 28, 2015 at 9:19 AM, Urs Liska wrote:
> Hi David,
>
> thank you very much!
>
You're welcome!
>
> Am 26.09.2015 um 01:25 schrieb David Nalesnik:
>
> Hi,
>
> ...
>
> To do what you want, it would be best of course to have a new grob.
>
> Defining new grobs has no user interf
Hi David,
thank you very much!
Am 26.09.2015 um 01:25 schrieb David Nalesnik:
> Hi,
>
> ...
>
> To do what you want, it would be best of course to have a new grob.
>
> Defining new grobs has no user interface at the moment. There is a
> regression text, input/regression/scheme-text-spanner.ly
>
On Fri, Sep 25, 2015 at 6:25 PM, David Nalesnik
wrote:
>
> Dashed lines may now (as of 2.19.27) be created using the function
> ly:line-interface::line. This takes a grob argument from which it extracts
> layout information. So you'd just override the 'style property. Dashed
> lines would be t
Hi,
On Fri, Sep 25, 2015 at 5:58 PM, Klaus Blum wrote:
> Hi Urs,
>
> the only thing I can offer is to use HorizontalBracket and replace its
> stencil by a box as shown in
> http://lsr.di.unimi.it/LSR/Item?id=1000
You could adapt ("coopt") an existing engraver, or ... (see below)
>
> Two dra
/Box-around-multiple-markups-tp181700p181707.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi all,
I want to engrave something like the attached scaned image for an
analytical music example. As you can see from the LilyPond attachments I
have achieved most of it already, but I'm out of luck with the different
boxes.
What I'd basically need is boxes that enclose two or more independent
Jean-marc LEGRAND wrote:
It could be that way, but I have to move it vertically... and the thing is
that when you use s64,
you have to pout it in all the staves, and make a maesure with no fixed measure
length...
Why? You could easily fake LilyPond into beleiving that the previous
note is short
TECTED]>
om> cc : lilypond-user@gnu.org
Objet : Re: mult
Jean-marc LEGRAND wrote:
Hi list !
I'm using lily2.4 on XP.
I have to put a rcomma AND a fingering on the same note. I'de like to have the
fingering just on top
of the note, but the rcomma just on the right, so at a different level.
I make :
\once \override TextScript #'extra-offset = #'(2.2 . -2)
Hi list !
I'm using lily2.4 on XP.
I have to put a rcomma AND a fingering on the same note. I'de like to have the
fingering just on top
of the note, but the rcomma just on the right, so at a different level.
I make :
\once \override TextScript #'extra-offset = #'(2.2 . -2) c8.^2 ^\tr. The 2
Hi Mats,
I hadn't seen that example until just now :-) (getting back to this after
being out of town for a bit). Unfortunately, it didn't seem to make much
difference (perhaps I put it in the wrong place).
What _did_ make a difference, oddly enough, was defining each voice as a
"Threa
Simple! Just make sure that the music and the dynamics belong
to the same Voice context. In your example, this is easiest
done by replacing \new Staff with \new Voice.
(If you start a Staff context with a << ...>>, a new Voice
context will be created for each line within that \simultaneous.)
Mats
On Mon, 06 Oct 2003 13:05:04 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> For dynamic markings, it may be more convenient to define them
> separately from the music, so you can choose when to include them:
> dynamicsA = \notes{ s1 \f \skip 1*10 s1 \pp ...}
How do you handle collisions when yo
Have you seen
http://lilypond.org/doc/v1.8/input/test/out-www/collated-files.html#maximum-rest-count.ly
Mats
Niki Pantelias wrote:
Hi Mats,
Thanks for the suggestions. Using \new or naming the voice contexts seems
to help in some ways (no more collisions between notes and rests) but make
Hi Mats,
Thanks for the suggestions. Using \new or naming the voice contexts seems
to help in some ways (no more collisions between notes and rests) but makes
matters worse in others (e.g., prints three rests instead of one where all
voices rest). Defining dymamics and articulations sepa
Niki Pantelias wrote:
Hi Graham (everyone),
Thanks for the reply. I have experimented a bit with \partcombine, but I
believe it is limited to only two voices; I need to put three or four voices
on a single staff. Also, I'd like to have the stems "shared" across
noteheads not set in oppo
Hi Graham (everyone),
Thanks for the reply. I have experimented a bit with \partcombine, but I
believe it is limited to only two voices; I need to put three or four voices
on a single staff. Also, I'd like to have the stems "shared" across
noteheads not set in opposite directions as \par
On Sat, 04 Oct 2003 11:57:45 -0400
Niki Pantelias <[EMAIL PROTECTED]> wrote:
> I'm trying to make a score which has several voices on a staff. I'm using
> identifiers to define each voice separately so that I can use the same input
> file to print out individual parts. Each definition contain
Hello everyone,
I'm trying to make a score which has several voices on a staff. I'm using
identifiers to define each voice separately so that I can use the same input
file to print out individual parts. Each definition contains its own dynamic
and articulation markings, etc.
The probl
32 matches
Mail list logo
