On Thu, Jul 30, 2009 at 10:09:17PM -0700, Patrick McCarty wrote:
On Thu, Jul 30, 2009 at 04:38:25PM -0700, Graham Percival wrote:
Remember that we can set background images in CSS. I recommend
keeping all such images in css/, and modifying the css file rather
than the raw texinfo.
Han-Wen Nienhuys wrote:
Braces are overloaded in LilyPond. In some cases they define scopes
(like \paper and \header), and in other cases, they just group
syntactic constructs (\book, \score, sequential musics).
The solution you propose sounds hairy to me. I think you probably
are
Patrick McCarty wrote:
I like this idea.
Having a list in an NR appendix would be just fine with me.
However, it would be difficult to auto-generate a lot of this
documentation, because not all of it is defined in LilyPond's
internals:
grob - LilyPond
prob - LilyPond
smob - Guile
Graham Percival wrote Friday, July 31, 2009 3:05 AM
Could you redistribute the material in LM 5.2 Scores and parts
elsewhere in the LM? Maybe beef up LM 2.4.1, maybe insert a new
LM 2.4.2 that continues the scores and parts theme, maybe
something in LM 3... whatever.
Done. I made a new
At 17:37 on 30 Jul 2009, Mark Polesky wrote:
Jonathan Kulp wrote:
I think it's possibly to detect keypresses in javascript.
1) Would it be cool or annoying to press n in the docs to
proceed to the next page? Admittedly this would be much more
useful in the LM than the NR.
I
A learning curve is always steep:
http://www.psywww.com/intropsych/ch07_cognition/learning_curve.html
Bert
Mark Knoop wrote:
At 17:37 on 30 Jul 2009, Mark Polesky wrote:
Jonathan Kulp wrote:
I think it's possibly to detect keypresses in javascript.
1) Would it be cool
Le jeudi 30 juillet 2009 à 19:42 -0700, Graham Percival a écrit :
The patch works for me; please push if you think it's ok.
LGTM, will push as soon as 'make doc' works again (I'm on it).
John
signature.asc
Description: Ceci est une partie de message numériquement signée
Le jeudi 30 juillet 2009 à 20:59 -0700, Graham Percival a écrit :
Attached patch works for me.
LGTM, will push with the other patch.
John
signature.asc
Description: Ceci est une partie de message numériquement signée
___
lilypond-devel mailing list
On Fri, Jul 31, 2009 at 09:18:45AM +0100, Trevor Daniels wrote:
Graham Percival wrote Friday, July 31, 2009 3:05 AM
Could you redistribute the material in LM 5.2 Scores and parts
elsewhere in the LM? Maybe beef up LM 2.4.1, maybe insert a new
Done. I made a new subsection at the end of LM
Graham Percival wrote Friday, July 31, 2009 10:50 AM
On Fri, Jul 31, 2009 at 09:18:45AM +0100, Trevor Daniels wrote:
It also uses \include, which isn't introduced anywhere, but
Woah, seriously? LM 3.1 is perfect for that. Anyway, I'll leave
this for you.
OK
Perhaps we should move
On Fri, Jul 31, 2009 at 12:00:53PM +0100, Trevor Daniels wrote:
Graham Percival wrote Friday, July 31, 2009 10:50 AM
- AU is looking really lean once we kill AU 1 and 2, so this would
give that manual more of a reason to exist.
Not a *good* reason, though
:)
Besides, suggestions for
Graham Percival wrote Friday, July 31, 2009 12:47 PM
On Fri, Jul 31, 2009 at 12:00:53PM +0100, Trevor Daniels wrote:
Graham Percival wrote Friday, July 31, 2009 10:50 AM
Besides, suggestions for writing files totally _sounds_ like
usage information to me. :)
Not sure about totally.
Hi guys,
Could someone checks paragraphs and the snippet I @ignored today in
Notation, chapter Spacing, in order to compile docs? Maybe they should
be deleted.
Best,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
On Fri, Jul 31, 2009 at 3:39 AM, Mark Poleskymarkpole...@yahoo.com wrote:
\score {
\relative {
%% value of afterGraceFraction inherited from previous score.
{ c1 \afterGrace d1 { c16[ d] } c1 }
#(define afterGraceFraction (cons 15 16))
{ c1 \afterGrace d1 { c16[ d] } c1 }
On Thu, Jul 30, 2009 at 11:22 PM, Mark Poleskymarkpole...@yahoo.com wrote:
here are some proposed updates for THANKS. I don't know who usually
takes care of this and/or who decides which names go where, but here are
You can make an EMERITUS section and put my name there, I think. I
can't
Bertalan Fodor wrote:
A learning curve is always steep:
http://www.psywww.com/intropsych/ch07_cognition/learning_curve.html
In the opposite sense, that is! See the last paragraph.
- Mark
___
lilypond-devel mailing list
Trevor Daniels wrote Friday, July 31, 2009 3:32 PM
Graham Percival wrote Friday, July 31, 2009 12:47 PM
Ah, I'd forgotten about those. Yes, 5.1.4 and 5.1.5 would be
better off in LM 3. Or maybe LM 4, since they both discuss
tweaks.
OK. I'll move 5.1.4 and 5.1.5 out sometime in
the next
Le lundi 27 juillet 2009 à 18:13 -0700, Graham Percival a écrit :
My apologies for being unclear in the past. (and my advanced
apologies for being unclear in the future, although hopefully I
won't be unclear about this specific issue)
Thanks, I've been preparing a detailed reply but have been
Hi Jan,
Le jeudi 30 juillet 2009 à 15:45 +0200, Jan Nieuwenhuizen a écrit :
Or just two very big (scalex4) glyphs,
clef+eight, flat/sharp + sixteenth?
This sounds better than a full bar of music: we don't want to make a
music piece so prominently, which could in particular distract the
reader,
On Fri, 2009-07-31 at 16:49 +0200, John Mandereau wrote:
Hi guys,
Could someone checks paragraphs and the snippet I @ignored today in
Notation, chapter Spacing, in order to compile docs? Maybe they should
be deleted.
They should be deleted, yes. I'll get working on some new docs.
Joe
2009/7/31 Graham Percival gra...@percival-music.ca:
I guess my basic complaint is that the logo doesn't do anything
for me -- a lily pad has nothing to do with notation. I'd be
happier if it had something musical in it.
Here I propose a possible solution. Merge John's snippet (made
Han-Wen Nienhuys wrote:
No. In the specific case, I'd recommend making another music
function that takes an argument, so you can pass the 15/16
explicitly, without mucking with variables.
So it sounds like you believe that one way or another, the burden
should be on the user. Then do you
On Fri, Jul 31, 2009 at 11:03 AM, Francisco Vilapaconet@gmail.com wrote:
2009/7/31 Graham Percival gra...@percival-music.ca:
I guess my basic complaint is that the logo doesn't do anything
for me -- a lily pad has nothing to do with notation. I'd be
happier if it had something musical in
Mark Polesky wrote Friday, July 31, 2009 7:10 PM
Han-Wen Nienhuys wrote:
No. In the specific case, I'd recommend making another music
function that takes an argument, so you can pass the 15/16
explicitly, without mucking with variables.
So it sounds like you believe that one way or
I made my first lilypond score for more than one instrument, and I
thought I'd give some comments on some of the things that were really
difficult from a beginner's perspective. I think it would be helpful to
have a section in the LM on migrating from Finale/Sibelius, or a
separate document,
Aw man, I meant to send this to the user list! Sorry about that.
-Jonathan
--- On Fri, 7/31/09, Jonathan Wilkes jancs...@yahoo.com wrote:
From: Jonathan Wilkes jancs...@yahoo.com
Subject: First Lilypond Score
To: lilypond-devel@gnu.org
Date: Friday, July 31, 2009, 9:18 PM
I made my first
Trevor Daniels wrote:
No, I don't think this is a *common* error.
I've never seen it mentioned on -user. And
it's too obscure for the LM anyway.
What we could do is add a full explanation of
parser (or global) variables in NR 6.8 Difficult
tweaks, together with your warning, and
In scm/documentation-generate.scm, I find this:
146 @appendixsec Function index
147
148 @printindex fn
...from which texinfo magically generates IR A. Indices:
http://kainhofer.com/~lilypond/Documentation/internals/Indices.html
I'd like the list (and others like it) to be sorted according
Hello,
Since Joe added a new Dynamics context to LilyPond, the two examples
mentioned in the subject are currently broken.
How should they be modified?
Attached is the current produced from latest git.
Thanks,
Patrick
attachment: piano-centered-dynamics.pngattachment:
Mark Polesky wrote Friday, July 31, 2009 8:51 PM
I'm okay with it. But I'd like to see what the others think. Am
I correct in thinking that if an object returns #t for this test
from within a .ly file, it qualifies as a parser variable?
#(defined? 'object-name)
Sorry, I don't know. Anyone
On Fri, 2009-07-31 at 14:00 -0700, Patrick McCarty wrote:
Hello,
Since Joe added a new Dynamics context to LilyPond, the two examples
mentioned in the subject are currently broken.
Thanks for pointing this out.
How should they be modified?
It should be sufficient to simply remove the
2009/7/31 Joe Neeman joenee...@gmail.com:
It should be sufficient to simply remove the definition of the Dynamics
context from these files (and the \accepts Dynamics part from
PianoStaff). The default Dynamics context is very similar (and drew
heavily from) the piano dynamics template, so it
On Fri, Jul 31, 2009 at 2:44 PM, Trevor Danielst.dani...@treda.co.uk wrote:
Mark Polesky wrote Friday, July 31, 2009 8:51 PM
I'm okay with it. But I'd like to see what the others think. Am
I correct in thinking that if an object returns #t for this test
from within a .ly file, it qualifies
2009/7/31 Patrick McCarty pnor...@gmail.com:
I *think* that's true.
Hmm, what about primitive procedures? I wouldn't class these as
identifiers, but they'll also return #t:
#(display (defined? 'car))
= #t
Since ly:parser-lookup returns EOL if it can't find the variable, the
following is
2009/7/30 Werner LEMBERG w...@gnu.org:
In notation-big-page.html, the output of the snippet which documents
\wordwrap-field is broken: It only shows the `title' field; the
`description' field is completely missing.
Oops, my fault.
Nicolas very kindly gave me some examples for this and a few
On Fri, Jul 31, 2009 at 01:11:02PM -0700, Mark Polesky wrote:
...from which texinfo magically generates IR A. Indices:
http://kainhofer.com/~lilypond/Documentation/internals/Indices.html
I'd like the list (and others like it) to be sorted according to
the algorithm in scm/lily-sort.scm.
On Fri, Jul 31, 2009 at 12:55:47PM -0300, Han-Wen Nienhuys wrote:
On Thu, Jul 30, 2009 at 11:22 PM, Mark Poleskymarkpole...@yahoo.com wrote:
here are some proposed updates for THANKS. I don't know who usually
takes care of this and/or who decides which names go where, but here are
You can
On Thu, Jul 30, 2009 at 6:54 AM, Werner LEMBERGw...@gnu.org wrote:
[git 17492869]
The \eyeglasses example image in notation-big-page.html is apparently
cut off at the right. This probably indicates that the bounding box
of this glyph has incorrect values.
Thanks for the report.
In current
Mark Polesky wrote:
Interesting idea. As a first attempt, I tried making the functionality
of the \arpeggioArrowUp command dependent on the 'connectArpeggios
context property, but obviously I'm doing something wrong. Does anyone
know why this doesn't work? Can anyone see how to make this
Mark Polesky wrote:
;; not sure if the conditional tests are necessary
(if PianoStaff
(arpeggio-generic PianoStaff
`(stencil X-extent arpeggio-direction dash-definition)))
(if Staff
(arpeggio-generic Staff
`(stencil X-extent
On Fri, 2009-07-31 at 18:58 -0700, Mark Polesky wrote:
Mark Polesky wrote:
Interesting idea. As a first attempt, I tried making the functionality
of the \arpeggioArrowUp command dependent on the 'connectArpeggios
context property, but obviously I'm doing something wrong. Does anyone
Joe Neeman wrote:
Have you tried using ly:context-property-where-defined instead of
searching for PianoStaff explicitly? There are non-PianoStaff contexts
containing Span_arpeggio_engraver, after all. Other than that, this is a
very cool trick!
Joe,
Thanks for the tip. I rewrote
Mark Polesky wrote:
Any objections? How close is this to being acceptable? I'll wait for
approval.
Okay, this is not ready yet. I found a confusing problem. When setting
connectArpeggios to #f after it has been #t, there's some issue with
the unreverted PianoStaff stencil somehow overriding
Hello,
Is scm/kpathsea.scm used anymore? If not, can it be removed from
LilyPond's source?
Thanks,
Patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
44 matches
Mail list logo
