Am 15.07.2013 20:30, schrieb Kieren MacMillan:
Hello,
There are a lot of places where I would like to use abs-fontsize:
InstrumentName, LyricText, etc.
It would be nice if there were a built-in, intuitive, consistent, direct method
of setting an absolute font size, e.g.,
\override
I've just added a snippet to the LSR (`Percent repeat counters for
piano music'), but I'm not able to preview it. Since I don't have a
1.14 lilypond binary, I can't check whether the problem is in the file
(it compiles fine with 1.16 and the current development version).
However, even adding a
Hi,
in an edition I prepare I often have the situation that I want to dash
one sibling of a Slur (because the original edition forgot to start a
slur before the line break.
Is there a convenient way to do so without having to define two curves
and tweak them independently?
Thanks
Urs
2013/7/16 Urs Liska u...@openlilylib.org:
in an edition I prepare I often have the situation that I want to dash one
sibling of a Slur (because the original edition forgot to start a slur
before the line break.
Is there a convenient way to do so without having to define two curves and
tweak
Ok I' look into it.
Then I can do it myself and spare you all those \todo entries ;-)
Urs
Janek Warchoł janek.lilyp...@gmail.com schrieb:
2013/7/16 Urs Liska u...@openlilylib.org:
in an edition I prepare I often have the situation that I want to
dash one
sibling of a Slur (because the
- Original Message -
From: Werner LEMBERG w...@gnu.org
To: lilypond-user@gnu.org
Sent: Tuesday, July 16, 2013 7:34 AM
Subject: LSR preview broken?
I've just added a snippet to the LSR (`Percent repeat counters for
piano music'), but I'm not able to preview it. Since I don't have a
2013/7/16 Phil Holmes m...@philholmes.net:
- Original Message - From: Werner LEMBERG w...@gnu.org
To: lilypond-user@gnu.org
Sent: Tuesday, July 16, 2013 7:34 AM
Subject: LSR preview broken?
I've just added a snippet to the LSR (`Percent repeat counters for
piano music'), but I'm
Your snippet compiles fine with 2.14.2 (tested).
Thanks.
There are some problems in the LSR concerning cropped images.
Hmm, I don't think this affects my snippet.
Maybe simply approving it solves the issue :-)
Werner
___
lilypond-user
2013/7/16 Werner LEMBERG w...@gnu.org:
Your snippet compiles fine with 2.14.2 (tested).
Thanks.
There are some problems in the LSR concerning cropped images.
Hmm, I don't think this affects my snippet.
Maybe simply approving it solves the issue :-)
No. Already tested.
Werner
hi,
i have a question regarding the spacing of dynamic contexts. given the
following (contrived for simplicity) snippet:
\version 2.17.22
music = \relative c {
\clef bass
c4 c c c
c c c c
c,, c'' c c
}
pedals = {
\repeat unfold 5 {s2\sustainOn}
s4\sustainOn s4\sustainOff
}
\score
Hi Urs and Janek,
On Tue, Jul 16, 2013 at 2:07 AM, Urs Liska u...@openlilylib.org wrote:
Ok I' look into it.
Then I can do it myself and spare you all those \todo entries ;-)
Urs
Janek Warchoł janek.lilyp...@gmail.com schrieb:
2013/7/16 Urs Liska u...@openlilylib.org:
in an
- Original Message -
From: Simon Bailey si...@bailey.at
To: lilypond-user@gnu.org
Sent: Tuesday, July 16, 2013 12:10 PM
Subject: pedal markings in dynamic context
hi,
i have a question regarding the spacing of dynamic contexts. given the
following (contrived for simplicity) snippet:
Simon Bailey-5 wrote
hi,
i have a question regarding the spacing of dynamic contexts. given the
following (contrived for simplicity) snippet:
this is a very simplified example, but it highlights the problem. is there
any way to make the pedal markings in bar 1-2 and on beat 3 of bar 3
hi eluze, phil,
i realize the point of the dynamics context. and it does what i want it to do.
the case i cited is a borderline case where it does exactly what it says on the
box; however, the result is not satisfactory – one note forces the whole line a
long way from the staff.
here's what
- Original Message -
From: Simon Bailey si...@bailey.at
To: lilypond-user Mailinglist lilypond-user@gnu.org
Sent: Tuesday, July 16, 2013 2:09 PM
Subject: Re: pedal markings in dynamic context
see attached pdf. bar 3 especially is not really very pretty…
Not sure what's not pretty?
Hi Marc (et al.),
I had thought of such a feature some months ago; my syntax proposal
would be something like
\set fontScaling = #absolute
or
\set fontScaling = #relative
As long as this is per-grob, and not global, I'm fine with it.
a feature like this would come in handy for eps
On Tuesday, 16 July 2013 at 15:25, Phil Holmes wrote:
- Original Message -
From: Simon Bailey si...@bailey.at (mailto:si...@bailey.at)
To: lilypond-user Mailinglist lilypond-user@gnu.org
(mailto:lilypond-user@gnu.org)
Sent: Tuesday, July 16, 2013 2:09 PM
Subject: Re: pedal
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
Now I'm hoping we can make Lilypond Do The Right Thing™ out of the
box.
I have no idea what you would consider more right than what Mike
provided.
This might be a job for GLISS…
Not at all. It's not input syntax related.
--
David
Hi David,
I have no idea what you would consider more right than what Mike provided.
Here are a couple of things, any of which, if implemented, would make it more
right than what Mike provided:
1. The user doesn't have to add a function to a file, because Lilypond has it
built in.
2. The
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
Hi David,
I have no idea what you would consider more right than what Mike provided.
Here are a couple of things, any of which, if implemented, would make
it more right than what Mike provided:
1. The user doesn't have to add a
David,
That's not a question of wrong or right.
You didn't ask what was wrong or right — you said you had no idea what I would
CONSIDER to be more right, so I told you.
It's not at all clear what it should apply to.
Ah, another of your completely unhelpful answers. Thanks.
Before one even
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
David,
That's not a question of wrong or right.
You didn't ask what was wrong or right — you said you had no idea what
I would CONSIDER to be more right, so I told you.
It's not at all clear what it should apply to.
Ah, another of
On 2013-Jul-16, at 10:54, David Kastrup d...@gnu.org wrote:
I don't have time for this.
If anyone has time to discuss this with me in a reasonable, non-patronizing,
and non-pedantic way, feel free to contact me on- or off-list.
As always, I'm open to sponsoring work that will help move Lilypond
Hi there,
I am not at home ... so here is not a solution, but here is a little
snippet, that includes two functions, that may be helpful:
\version 2.16.1
musA = \relative c'' {
bes4 a c b
}
musB = #(music-map
(lambda (m)
(let* ((mus m)
(dur (ly:music-property mus 'duration)))
(if
Hello all,
I'm getting close with my Henle piano stylesheet(s) — see attached.
Once this is ready, I'm going to document it and put it up on the Lilyblog.
I think the last thing I need is an oval BarNumber enclosure (see photo).
Can anyone help with that?
Thanks,
Kieren.
inline:
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
Hello all,
I'm getting close with my Henle piano stylesheet(s) — see attached.
Once this is ready, I'm going to document it and put it up on the Lilyblog.
I think the last thing I need is an oval BarNumber enclosure (see photo).
Can
Hi David,
Try starting from
Thanks — that's very helpful!
Here's what I have from there:
\version 2.17
#(define-markup-command (ellipse layout props text) (markup?)
#:properties ((thickness 0.2) (x-padding 0.1) (y-padding 0.75))
(ellipse-stencil (interpret-markup layout props text)
2013/7/16 Kieren MacMillan kieren_macmil...@sympatico.ca:
Hi David,
Try starting from
Thanks — that's very helpful!
Here's what I have from there:
\version 2.17
#(define-markup-command (ellipse layout props text) (markup?)
#:properties ((thickness 0.2) (x-padding 0.1) (y-padding
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
What's the easy way of saying center the number in a box at least
'this big', but use the number's real extent if it's bigger than
that?
\hcenter-in does that.
#(define-markup-command (ellipse layout props text) (markup?)
#:properties
Hi everyone,
Thanks to David K and Harm (whose functions and suggestions I mashed up to make
the oval bar number formatter), we have a winner!
Well, at least for now… further tweaks coming once I've typeset the rest of the
movement. Then I'll do a side-by-side comparison of the printed version
OK, sorry ... I missed the point, you want pattern generation ;)
--snip--
#(use-modules (srfi srfi-60))
#(define-public pattern
(define-music-function (parser location n pitch dur)
(integer? ly:pitch? ly:duration?)
(let ((l (list)))
(define (pat i)
(if ( i n)
(append (pat (* 2 i))
Hi Harm,
sometime ago David Nalesnik and I were working on it.
Originally, it was 2.14.2-code but still works with 2.17.21.
Sorry I never responded to this — it's amazing!
This, IMHO, should be part of the default distro.
Many thanks!
Kieren.
___
32 matches
Mail list logo