http://code.google.com/p/lilypond/issues/detail?id=170
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> slurs and dynamic texts are involved in collision resolution; check
> the avoid-slur properties on DynamicText and DynamicLineSpanner.
Indeed, this did the trick:
f1
\once \override DynamicText #'X-offset = #'-5.0
\once \override DynamicLineSpanner #'Y-offset = #'-5.0
\once \override
Hi. Just got a lilypond-devel email with first message about kievan
notes in it again. I'm not sure how that happened, but I'm sorry for the
repeat.
Fr. P
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/li
Werner LEMBERG escreveu:
>>> Change #'Y-offset on the DynamicLineSpanner too.
>> Yes, I got the same idea. However, I would prefer that Y-offset
>> were relative to the original position instead of being relative to
>> the vertical staff center. However, I can live with that.
>
> Hmm. The code
Werner LEMBERG escreveu:
>>> Well, it still doesn't work: I want to change Y-offset!
>>>
>>> {
>>> \override DynamicText #'Y-offset = #5.0
>>> \once \override DynamicLineSpanner #'outside-staff-priority = ##f
>>> c2\ff
>>> }
>> Change #'Y-offset on the DynamicLineSpanner too.
>
> Y
John Mandereau escreveu:
> Since the translated documentation itself is ready to be released, merge
> and apply your trick as you like.
>
> So, I have a question about merging branches, since I may need to do it
> sooner or later. IIRC, Han-Wen has once told Joe Neeman on the list that
> it was be
On Thursday 30 November 2006 06:01, you wrote:
> Hello, Panteleimon!
Hello, thank you for your response
> I fear the task of fully implementing kievan chant notation is more than
> just a question of adding thirteen glyphs.
> recognize at least pes ligatures (those pairwise stacked rhombic glyph
Sorry for the repeat, but I didn't initially send this to the developer's
list, just to certain developers. Since Juergen's reply went to the list I
thought I'd better correct my omission.
Second installment coming soon.
Fr. P
-- Forwarded Message --
Subject: Kievan "hatchet"
Hello,
I'm very excited about the new vertical collision avoiding code in
Lily-2.11.0 - it's something I've been waiting from 2.2. version on (I
had to always set vertical text-padding value manually) :). I have some
question about its implementation and usage:
1) Does this patch removes text coll
> > Change #'Y-offset on the DynamicLineSpanner too.
>
> Yes, I got the same idea. However, I would prefer that Y-offset
> were relative to the original position instead of being relative to
> the vertical staff center. However, I can live with that.
Hmm. The code below makes me believe that t
> > Well, it still doesn't work: I want to change Y-offset!
> >
> > {
> > \override DynamicText #'Y-offset = #5.0
> > \once \override DynamicLineSpanner #'outside-staff-priority = ##f
> > c2\ff
> > }
>
> Change #'Y-offset on the DynamicLineSpanner too.
Yes, I got the same idea. Ho
Jan Nieuwenhuizen wrote:
> Ok, thanks. We may want to merge then and use my silly
> build-html-docs-twice solution. Or was that reverted now, Han-Wen?
Since the translated documentation itself is ready to be released, merge
and apply your trick as you like.
So, I have a question about merging b
On 12/7/06, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> That's right -- you need to override DynamicLineSpanner instead of
> DynamicText (see the following example).
Well, it still doesn't work: I want to change Y-offset!
{
\override DynamicText #'Y-offset = #5.0
\once \override Dyn
> That's right -- you need to override DynamicLineSpanner instead of
> DynamicText (see the following example).
Well, it still doesn't work: I want to change Y-offset!
{
\override DynamicText #'Y-offset = #5.0
\once \override DynamicLineSpanner #'outside-staff-priority = ##f
c2\ff
Joe Neeman wrote:
Your assumption is correct. The grobs with low priority (maybe it should
be the other way around?) are positioned first. Once they are in place,
the skylines are recalculated to include them and the remaining grobs
are positioned. Grobs where outside-staff-priority is not a nu
On 12/7/06, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> >> well, it is using a priority field, which can have multiple values
> >> for a single grob type.
> >
> > Aah, if I understand you correctly, I can write
> >
> >
> >\override foo #'outside-staff-priority = #1
> >\override bar #'out
On 12/7/06, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > > If a user wants the symbol to be positioned at an absolute
> > > offset from its Y-parent, they can just set
> > > outside-staff-position to () in addition to setting Y-offset.
>
> Sorry, outside-staff-priority, not outside-staff-posit
Han-Wen Nienhuys wrote:
ssh+git://[EMAIL PROTECTED]/srv/git/lilypond.git/
Yay, it worked!
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Graham Percival escreveu:
> Mats Bengtsson wrote:
>> Try something like
>> git push [EMAIL PROTECTED]/srv/git/lilypond.git
>
> Nope, sorry.
>
> tsubasa:~/usr/src/lilypond gperciva$ git push
> [EMAIL PROTECTED]/srv/git/lilypond.git
> fatal: '[EMAIL PROTECTED]/srv/git/lilypond.git': unable to chdir
Mats Bengtsson wrote:
Try something like
git push [EMAIL PROTECTED]/srv/git/lilypond.git
Nope, sorry.
tsubasa:~/usr/src/lilypond gperciva$ git push
[EMAIL PROTECTED]/srv/git/lilypond.git
fatal: '[EMAIL PROTECTED]/srv/git/lilypond.git': unable to chdir
or not a git archive
fatal: unexpected
20 matches
Mail list logo
