Patrick McCarty writes:
> On 2009-11-16, David Kastrup wrote:
>>
>> It still suffers from not doing short-circuit evaluation. For
>> readability and efficiency, I'd really prefer replacing
>> '(apply functional-or' with '(any'
>
> It looks like Neil removed the "is-harmonic" binding from
A Chordname like thing would take quite much time to implement and I
don't think it is important enough for most of the users to make it happen.
Though you can use the Lyrics context for this, because you can write
markups as lyric syllables if I'm right. On the lilypond-user list I'm
quite sure
Dear developers,
I have recently found Lilypond, and am discovering step by step what a wonderful
program it is, and what a quick and simple method to print beautiful music it
presents (once I am a little more acquainted with it at least).
I have been learning the basics og the program through wr
On 2009-11-16, David Kastrup wrote:
> Patrick McCarty writes:
>
> > Thanks, pushed.
>
> Thanks. The only caller (this is apparently in local namespace) as far
> as I can see is
>
> (define-public (fret-number-tablature-format string context event)
> (let* ((tuning (ly:context-property contex
Carl Sorensen writes:
> I appreciate your work on this.
>
> However, I am *not* in favor of moving in this direction to solve the
> problems you correctly identified.
>
> In my mind, the *last* thing we need is another opaque interface in
> LilyPond, where in the markup command we don't know whet
Le 17 nov. 2009 à 19:00, Carl Sorensen a écrit :
> David,
>
> I appreciate your work on this.
>
> However, I am *not* in favor of moving in this direction to solve the
> problems you correctly identified.
>
> In my mind, the *last* thing we need is another opaque interface in
> LilyPond, where
> You forgot "make doc-clean" in this sequence; in this case "make -C
> Documentation/ doc-clean" (which avoids rebuilding all snippets with
> lilypond-book) might be enough to get rid of your error with pdftex.
That worked, thanks,
Frédéric
___
lilyp
David,
I appreciate your work on this.
However, I am *not* in favor of moving in this direction to solve the
problems you correctly identified.
In my mind, the *last* thing we need is another opaque interface in
LilyPond, where in the markup command we don't know whether a certain
property is to
---
scm/define-markup-commands.scm |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/scm/define-markup-commands.scm b/scm/define-markup-commands.scm
index 08c24bb..fec895d 100644
--- a/scm/define-markup-commands.scm
+++ b/scm/define-markup-commands.scm
@@ -732,7 +732,6 @@
The already outcommented problematic \harp-pedal-verbose markup is
removed completely. Inlining make-harp-pedal makes it possible to use
the property binding mechanism of define-builtin-markup-command in
order to minimize inconsistencies between documentation and behavior.
---
scm/harp-pedals.scm
Am Dienstag, 17. November 2009 01:29:49 schrieb Han-Wen Nienhuys:
> On Mon, Nov 16, 2009 at 4:54 PM, Reinhold Kainhofer
>
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > while trying to fix some MIDI issues, I've now run into the problem that
> > in a performer's acknowledg
Le dimanche 15 novembre 2009 à 23:12 +0100, Frédéric Bron a écrit :
> did not know that (not in CG): I did the sudo apt-get build-dep
> lilypond. I have already tex2thml 1.82 (installed manually).
> redone git pull, make clean, make all, make doc.
You forgot "make doc-clean" in this sequence; in t
12 matches
Mail list logo
