> "kieren" == kieren macmillan <[EMAIL PROTECTED]> writes:
kieren> Mats,
>> I would have though that \override Hairpin #'bound-padding = #2.0
>> should do the job, but it seems that it only affect the right end,
>> not the left end. Of course, you could then use a combination of
>> X-offset a
Thanks Mark. My own solution, finally, was to define a dummy dynamic:
spacer = #(make-dynamic-script (markup ""))
and attach it to the starting note, where it displaces the left end of
the hairpin to the right by about the width of a notehead. It's not the
finest control, and it has kludge wr
On Mon, 12 May 2008 18:10:48 -0600
"Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> Graham,
>
> I'm sorry to be obtuse on this, but I want to do the job right. So I
> figure if I spend a bit of your time in the beginning, I'll save some
> at the end...
You're quite right to do so! Of course, no
Graham,
I'm sorry to be obtuse on this, but I want to do the job right. So I figure if
I spend a bit of your time in the beginning, I'll save some at the end...
policy.txt has the following:
BEGIN COPIED TEXT
% SECTION ORGANIZATION
The order of headings inside documentation sect
On Tue, 13 May 2008 01:39:48 +0200
"Francisco Vila" <[EMAIL PROTECTED]> wrote:
> 2008/5/13 Carl D. Sorensen <[EMAIL PROTECTED]>:
> > But when I look in http://web.uvic.ca/~gperciva/doc-src/,
> > there is no pitches.itely.
>
> Yes, there is one, look carefully. Just between "percussion.itely" an
Sorry! I was cleaning out that folder, and forgot that people
still need to see it. It's uploaded now.
Cheers,
- Graham
On Mon, 12 May 2008 17:13:06 -0600
"Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> Graham,
>
> I'm following your instructions in writing-sections.txt:
>
> REQUIRED READIN
2008/5/13 Carl D. Sorensen <[EMAIL PROTECTED]>:
> But when I look in http://web.uvic.ca/~gperciva/doc-src/,
> there is no pitches.itely.
Yes, there is one, look carefully. Just between "percussion.itely" and
"repeats.itely"
> Where do I find pitches.itely?
http://web.uvic.ca/~gperciva/doc-src
Graham,
I'm following your instructions in writing-sections.txt:
REQUIRED READING
(snip)
- NR 1.1 Pitches. Ideally, read it in your favorite output format
(either info, PDF, or HTML), *and* in source format
(pitches.itely). This is our "demonstration" chapter, so the
below points really j
On Mon, 12 May 2008 14:19:15 -0700
Graham Percival <[EMAIL PROTECTED]> wrote:
> We still have two "entry-level" positions:
Sorry, my mad rush to cancel the message failed.
We have three "entry-level" positions:
Unfretted strings
Winds
Ancient
I'd still like to reserve these two longer sections
On Mon, 12 May 2008 20:35:14 + (UTC)
Carl Sorensen <[EMAIL PROTECTED]> wrote:
> Oops -- I just checked current.txt and found that Jonathan's name is
> on it. If that's true, then put me down for Chords. I've been
> needing to learn more about chords...
Great, done!
We still have two "entry
Carl Sorensen byu.edu> writes:
>
> Graham Percival gmail.com> writes:
> >
> Graham,
>
> I've got some time now. Put me down for Fretted Strings.
>
> Carl Sorensen
>
Oops -- I just checked current.txt and found that Jonathan's name is on it. If
that's true, then put me down for Chords. I
Graham Percival gmail.com> writes:
>
> As you probably know, we're nearing the end of the Grand
> Documentation Project of LilyPond. It ends in Aug, so there's
> only three and a half months left.
>
> For more general background about GDP, see:
> http://web.uvic.ca/~gperciva/
>
Graham,
I've
Greetings everyone,
A new issue of the "Lilypond Report" is out:
http://valentin.villenave.info/The-LilyPond-Report-9
This week's issue discusses open-source hardware, accordion support,
intermediate files, LSR downtimes and bug statistics. I'd also like to
announce that next week's issue will b
Mats,
I would have though that
\override Hairpin #'bound-padding = #2.0
should do the job, but it seems that it only affect the right end, not the
left end.
Of course, you could then use a combination of X-offset and bound-padding
to get
what you want, but I'm not convinced that this is the e
Quoting Stefan Thomas <[EMAIL PROTECTED]>:
Oh, many thanks!
I don't understand why, but it helped!!
Once you think about it, it's fairly logical that the line-positions
property overrides the line-count property, especially if you look at
some of the examples of line-positions provided in the
Oh, many thanks!
I don't understand why, but it helped!!
2008/5/12 Trevor Daniels <[EMAIL PROTECTED]>:
> Stefan
>
> It seems that the #'line-positions setting remains in effect over a
> \stopStaff \startStaff, and overrules #'line-count. Include
>
> \override Staff.StaffSymbol #'line-positions
Stefan
It seems that the #'line-positions setting remains in effect over a
\stopStaff \startStaff, and overrules #'line-count. Include
\override Staff.StaffSymbol #'line-positions = #'(0)
in trommel and it should then work. Actually, if you specify
#'line-positions you don't need to speci
I would have though that
\override Hairpin #'bound-padding = #2.0
should do the job, but it seems that it only affect the right end, not
the left end.
Of course, you could then use a combination of X-offset and
bound-padding to get
what you want, but I'm not convinced that this is the expected
On Mon, 2008-05-12 at 22:20 +1000, Kim Bastin wrote:
> What's the override for moving the ends of a hairpin horizontally? I
> need to start one a little to the right of its default position because
> it collides with a cross-staffed note. But I can only find information
> about moving hairpins v
Dear lilypond-users,
I have a problem, that's going to drive me crazy at the moment!!
Why can't I do a change of staff lines in the below quoted example?
%% Begin %%
trommel = { \override Staff.StaffSymbol #'line-count = 1 \override
Staff.BarLine #'bar-size = #3 }
normalsystem = {\overr
What's the override for moving the ends of a hairpin horizontally? I
need to start one a little to the right of its default position because
it collides with a cross-staffed note. But I can only find information
about moving hairpins vertically. I tried this:
\once \override Hairpin #'X-offset
Ok.
So well.. I tweaked a little bit and now it seems to work. What I wanted
is just the anhang (appendix) to be typesetted by lilypond, the other
examples I wanted as simple images. So I kept the file structure and
just made a file anhang.lytex which I compiled (tanks very much for the
make file)
22 matches
Mail list logo