Re: Make doc error 2.13.10
On Wed, 2009-12-23 at 07:29 +0100, David Kastrup wrote: > Colin Campbell writes: > > > David Kastrup wrote: > >> > >> Nicolas integrated my define-markup-command patches recently. > >> Previous versions had reported memory problems which I could not > >> reproduce, but tried to fix nevertheless, and the revised version was > >> reported not to have the same problems. > > > > I've managed to build the docs (very much like the look of the web > > page, too!). Pulling in yesterday's patch didn't seem to fix it, but > > installing a boatload ( metric: shed-load) of texlive-fonts* seems to > > have done it. > > While memory-based errors are somewhat quirky, that makes it unlikely > that my change was the culprit. That's right. My commit 88d85985d caused the segfault, which was fixed yesterday. Cheers, Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Make doc error 2.13.10
Colin Campbell writes: > David Kastrup wrote: >> >> Nicolas integrated my define-markup-command patches recently. >> Previous versions had reported memory problems which I could not >> reproduce, but tried to fix nevertheless, and the revised version was >> reported not to have the same problems. > > I've managed to build the docs (very much like the look of the web > page, too!). Pulling in yesterday's patch didn't seem to fix it, but > installing a boatload ( metric: shed-load) of texlive-fonts* seems to > have done it. While memory-based errors are somewhat quirky, that makes it unlikely that my change was the culprit. Lilypond should not segfault on missing fonts, however. Do you think you can track this to some particular missing font or recipe, or is this too much work? > It appears that apt-get build-dep lilypond doesn't depend those font > packages. Which might be a bug in the Debian packaging, and also worth reporting if you can track it down. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
[PATCH] Nested properties in the \paper block
http://codereview.appspot.com/182042/show
This patch implements nested property setting for \paper block (and
\header block, etc) variables, similar to how \override works for nested
properties. In particular, you can do something like
\paper {
between-system-spacing #'space = #10
}
to override the 'space sub-property of between-system-spacing without
modifying the other sub-properties. Apart from being more convenient, it
will allow me to write better convert-ly rules for vertical spacing
variables.
Joe
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Make doc error 2.13.10
David Kastrup wrote: Graham Percival writes: On Mon, Dec 21, 2009 at 4:18 PM, Trevor Daniels wrote: Colin Campbell wrote Monday, December 21, 2009 3:33 PM After building LP 2.13.10 from git, I wanted an HTML copy of the docs, so I cd to /Documentation and did make doc. The result was a segfault: Try make doc in the directory above /Documentation, whatever you chose to call it. That shouldn't matter; I've make doc 'd in many directories before doing it in the topdir. I'm trying a full rebuild now; I'm getting some errors, but I'm not certain if they're just the expected random errors from using CPU_COUNT, or whether they're more serious. I'll report back in a while. Nicolas integrated my define-markup-command patches recently. Previous versions had reported memory problems which I could not reproduce, but tried to fix nevertheless, and the revised version was reported not to have the same problems. The commit would be bfbb8f784d69034c1ed351f6a00173338ee9aa04. It might be worth checking if reverting this particular commit cures the problem for the original poster. If yes, his g++ and guile versions would be important to know, and other platform details. If no, so much the better. For me, I mean. I've managed to build the docs (very much like the look of the web page, too!). Pulling in yesterday's patch didn't seem to fix it, but installing a boatload ( metric: shed-load) of texlive-fonts* seems to have done it. It appears that apt-get build-dep lilypond doesn't depend those font packages. At any rate, on to the first term test! Colin -- A good juggler can always find work. - attributed to L. Pacioli (1445 - 1517) ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc -- Add info on \version statements to Tutorial (issue179121)
On Tue, Dec 22, 2009 at 02:57:26PM -0700, Carl Sorensen wrote: > > All the changes have been made. A new version is pushed: > > http://codereview.appspot.com/179121 Looks fine; please push. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Use different types of events for cueDuring and quoteDuring (issue180114)
Hi Reinhold, Staff.itely ooks good, apart from one nitpick. Could you double-check this file for trailing spaces, please? Cheers, Ian http://codereview.appspot.com/180114/diff/21/1002 File Documentation/notation/staff.itely (right): http://codereview.appspot.com/180114/diff/21/1002#newcode1139 Documentation/notation/staff.itely:1139: It is possible to adjust which objects from the original voice are quoted "It is also possible". . . (just makes reading it flow better from the previous paragraph) http://codereview.appspot.com/180114 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [frogs] Patch for Issue #830
Thanks Carl - I've installed this too. Saves having to remember to do it as a separate action. Trevor - Original Message - From: "Carl Sorensen" To: "James Lowe" Cc: "Marc Hohl" ; "Mark Polesky" ; "Neil Puttock" ; "Lily-Devel List" ; Sent: Tuesday, December 22, 2009 2:26 PM Subject: Re: [frogs] Patch for Issue #830 On 12/22/09 5:48 AM, "James Lowe" wrote: Carl, Carl Sorensen wrote: We have now put a new script in scripts/auxiliar/ that will strip trailing whitespace. After you're done editing a file, just enter the following from a command prompt: ... Thanks for that, I'll make sure that I use that. What editor are you using? Just the default one that comes with the Lilybunto iso which is gedit. I don't care which one I use, but gedit is simple and has a nice search facilty and is inbuilt to 'file manager' pretty well. James, There is a plugin available for gedit to strip all trailing whitespace It's available for download at http://users.tkk.fi/~otsaloma/gedit/trailsave.gedit-plugin If you install this for gedit, not only will you never have this problem again, but when you edit the files you'll automatically remove trailing whitespace, so the files will get better over time. I'd recommend doing this, although you don't need to. I don't mind running the python CLI for now. It maybe something we could perhaps (we? :) ) incorporate into the lilycontrib.tcl file for us lesser mortals. Add another button or make it part of the commit/make button. Mark, Graham tried to get you interested in taking over lilycontrib.tcl. Are you interested? Thanks, Carl Thanks, Carl --- Join the Frogs! ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc -- Add info on \version statements to Tutorial (issue179121)
On 12/22/09 8:14 AM, "percival.music...@gmail.com"
wrote:
> ok, given the support for this idea, I'm ok with in theory. Comments
> below.
>
>
> http://codereview.appspot.com/179121/diff/1002/3
> File Documentation/learning/tutorial.itely (right):
>
> http://codereview.appspot.com/179121/diff/1002/3#newcode51
> Documentation/learning/tutorial.itely:51:
> Let's keep the separate @example, so that we can write
> @example
> \version "@version{}"
> @{
> ...
Sounds great. @version{} isn't listed in the CG. I'll add it.
>
> http://codereview.appspot.com/179121/diff/1002/3#newcode66
> Documentation/learning/tutorial.itely:66:
> This isn't important enough to have on this page; if we have too many
> warnings, people will start ignoring them.
>
OK.
> http://codereview.appspot.com/179121/diff/1002/3#newcode779
> Documentation/learning/tutorial.itely:779:
> Separate @node @subsection, please. The \version has nothing to do with
> omitting braces.
>
> Alternately, we could rename "omitting braces" to "omitted material".
I thought about the separate subsection and decided it was too short.
I'll be happy to change the section name.
>
> http://codereview.appspot.com/179121/diff/1002/3#newcode855
> Documentation/learning/tutorial.itely:855:
> Could we also get a paragraph about \version in 1.2.2? Also, remove
> 2.4.2 entirely.
>
Yes, I'll do that.
All the changes have been made. A new version is pushed:
http://codereview.appspot.com/179121
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Quoting different types of events for \cueDuring and \quoteDuring
Am Dienstag, 22. Dezember 2009 18:27:43 schrieb Ian Hulin: > Will the docs make the distinction about \quoteDuring vs. \cueDuring > usage clear? > I can see there is stuff in the amended docstrings in > define-context-properties.scm which will go into the docs somewhere but > do you feel that's enough for end-users? I've now written some sentences and examples in staff.itely to explain this in more detail: http://codereview.appspot.com/180114 Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Quoting different types of events for \cueDuring and \quoteDuring
Am Dienstag, 22. Dezember 2009 18:27:43 schrieb Ian Hulin: > Hi Reinhold, > > On 22/12/09 15:34, Reinhold Kainhofer wrote: > > Typically, \quoteDuring is used to duplicate everything in a voice, > > while \cueDuring is used to only quote the notes, but not e.g. > > phrasing, slurs, accents, markup, etc. > > > > So, this patch adds an additional property quotedCueEventTypes in > > addition to quotedEventTypes, which allows to quote different types > > for \cueDuring than for \quoteDuring. > > > > By default, \quoteDuring now quotes everything (i.e. StreamEvent), while > > \cueDuring quotes only notes, rest, ties, beams and tuplets. > > > > Here's the patch (also includes a regtest): > > http://codereview.appspot.com/180114 > > > > Okay to apply? > > Will the docs make the distinction about \quoteDuring vs. \cueDuring > usage clear? Actually, the docs already say that \quoteDuring is used to duplicate another voice (which was NOT true, only pitch and rhythm was quoted, but no articulations, slurs, etc.). > I can see there is stuff in the amended docstrings in > define-context-properties.scm which will go into the docs somewhere but > do you feel that's enough for end-users? The docs on quoteDuring and cueDuring is not very good right now. In particular, quotedEventTypes is documented only in one snippet, that removes quoting rests (but does not show how to quote more than only notes, rests and ties). Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Quoting different types of events for \cueDuring and \quoteDuring
Hi Reinhold, On 22/12/09 15:34, Reinhold Kainhofer wrote: Typically, \quoteDuring is used to duplicate everything in a voice, while \cueDuring is used to only quote the notes, but not e.g. phrasing, slurs, accents, markup, etc. So, this patch adds an additional property quotedCueEventTypes in addition to quotedEventTypes, which allows to quote different types for \cueDuring than for \quoteDuring. By default, \quoteDuring now quotes everything (i.e. StreamEvent), while \cueDuring quotes only notes, rest, ties, beams and tuplets. Here's the patch (also includes a regtest): http://codereview.appspot.com/180114 Okay to apply? Will the docs make the distinction about \quoteDuring vs. \cueDuring usage clear? I can see there is stuff in the amended docstrings in define-context-properties.scm which will go into the docs somewhere but do you feel that's enough for end-users? Cheers, (und fröhliche Weihnachten), Ian ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [frogs] Patch for Issue #830
On Tue, Dec 22, 2009 at 3:30 PM, Mark Polesky wrote: > Carl Sorensen wrote: >> Mark, Graham tried to get you interested in taking over >> lilycontrib.tcl. Are you interested? > > Well, I was avoiding it because it's written in yet another > scripting language that I don't know. No worries. Just leave it there; somebody will do it at some time. We won't advertise for new contributors before it's done, but other than that there's no rush. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
[PATCH] Quoting different types of events for \cueDuring and \quoteDuring
Typically, \quoteDuring is used to duplicate everything in a voice, while \cueDuring is used to only quote the notes, but not e.g. phrasing, slurs, accents, markup, etc. So, this patch adds an additional property quotedCueEventTypes in addition to quotedEventTypes, which allows to quote different types for \cueDuring than for \quoteDuring. By default, \quoteDuring now quotes everything (i.e. StreamEvent), while \cueDuring quotes only notes, rest, ties, beams and tuplets. Here's the patch (also includes a regtest): http://codereview.appspot.com/180114 Okay to apply? Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [frogs] Patch for Issue #830
Carl Sorensen wrote: > Mark, Graham tried to get you interested in taking over > lilycontrib.tcl. Are you interested? Well, I was avoiding it because it's written in yet another scripting language that I don't know. Am I being obtuse, do you think? I'm currently working on reorganizing the CG and I don't want to make too many promises because I may not have as much Pond time as I used to have. I'd also like to go through the other manuals at some point and relearn how to actually *use* LP, a skill which I appear to have largely lost in the three months that I took off. - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Alternative music font
On 12/22/09 12:45 AM, "Marc Hohl" wrote: > Carl Sorensen schrieb: >> >> On 12/21/09 1:52 PM, "Marc Hohl" wrote: >> >> >>> [...] >>> I like it much better. But I think that the bulb on the bottom of the clef needs to shift slightly to the right with this change. >>> Like the attached one? >>> You may use the pdf file for a printout. >>> >> >> This may be a bit too much different, or maybe it's just the change in the >> curvature that bothers me a bit. It feels like the curve at the bottom of >> the clef is too pointed somehow. Perhaps it's the transition that I'm >> responding to; I'm not really sure. >> > Perhaps I overdid it a bit; here is a version where the bulb is exaclty > half-way between > the first and the second attempt. Looks good to me. I'd also like to see half-way between this attempt and the first attempt, not because I think this is wrong, but because I tend to find optimum settings by finding "not enough" and "too much" and going between those two. But I'm not a great source for making aesthetic decisions. I'm an engineer, after all! Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [frogs] Patch for Issue #830
On 12/22/09 5:48 AM, "James Lowe" wrote: > Carl, > > Carl Sorensen wrote: > >> >> We have now put a new script in scripts/auxiliar/ that will strip trailing >> whitespace. >> >> After you're done editing a file, just enter the following from a command >> prompt: >> >> ... > > Thanks for that, I'll make sure that I use that. >> >> What editor are you using? >> > Just the default one that comes with the Lilybunto iso which is gedit. I > don't care which one I use, but gedit is simple and has a nice search > facilty and is inbuilt to 'file manager' pretty well. James, There is a plugin available for gedit to strip all trailing whitespace It's available for download at http://users.tkk.fi/~otsaloma/gedit/trailsave.gedit-plugin If you install this for gedit, not only will you never have this problem again, but when you edit the files you'll automatically remove trailing whitespace, so the files will get better over time. I'd recommend doing this, although you don't need to. > I don't mind > running the python CLI for now. > > It maybe something we could perhaps (we? :) ) incorporate into the > lilycontrib.tcl file for us lesser mortals. Add another button or make > it part of the commit/make button. Mark, Graham tried to get you interested in taking over lilycontrib.tcl. Are you interested? Thanks, Carl Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fix Tracker 918, Add extra RemoveEmpty*StaffContext functions to support "Frenched" scores (issue180095)
Hi Neil, On 21/12/09 23:34, n.putt...@gmail.com wrote: On 2009/12/21 00:33:59, Ian Hulin wrote: New patch-set uploaded with regressions in engraver-init.ly fixed. Now OK to push? LGTM, applied. Much obliged, Have a good Christmas, Cheers, Ian ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
