Re: LilyBuntu [don't read kainhofer.com!]
Am Samstag, 11. Dezember 2010, um 00:38:54 schrieb Graham Percival: Whatever it does to obtain a new set of manuals, any daily snapshot should do the same. No. The docs on kainhofer.com are not our official docs. It is a private server which Reinhold graciously makes available. Compiling the docs from scratch requires a fair amount of resources, ranging from CPU power to disk life (by using read/writes) to electricity. I agree that any official daily snapshot should build from scratch. But I don't think it's worth the resources it would take. A daily doc build was fantastic during GDP, but these days the docs don't change all that rapidly, and all doc contributors can build the docs themselves (mostly with lilybuntu). Okay, I have now changed the system of my doc builds: They are built from scratch nightly on my office machine (which is idling at night any way), and then rsync'ed to the server. So, now the docs in kainhofer.com should always be the really latest version. The out-of-source build worked just fine on my office machine, no idea what causes it to fail on the server. 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: LilyBuntu [don't read kainhofer.com!]
On Sun, Dec 12, 2010 at 1:16 PM, Reinhold Kainhofer reinh...@kainhofer.com wrote: Okay, I have now changed the system of my doc builds: They are built from scratch nightly on my office machine (which is idling at night any way), and then rsync'ed to the server. So, now the docs in kainhofer.com should always be the really latest version. Great! Thanks a lot, this will be quite useful in some cases. Cheers, Valentin. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fix 1336 (issue3594041)
On Sat, Dec 11, 2010 at 9:53 PM, n.putt...@gmail.com wrote: On 2010/12/11 23:23:46, Neil Puttock wrote: I think it would be better to create the missing column rather than aborting. Neil's approach looks better to me than Carl's, as it is closer to the place where skipTypesetting is handled. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fix 1336 (issue3594041)
On Dec 12, 2010, at 6:20 AM, Han-Wen Nienhuys hanw...@gmail.com wrote: On Sat, Dec 11, 2010 at 9:53 PM, n.putt...@gmail.com wrote: On 2010/12/11 23:23:46, Neil Puttock wrote: I think it would be better to create the missing column rather than aborting. Neil's approach looks better to me than Carl's, as it is closer to the place where skipTypesetting is handled. I completely agree Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Don't make paper columns if skipTypesetting = ##t. (issue3598041)
LGTM; regtest comparison shows nothing unexpected, and the docs build from scratch. Please push. http://codereview.appspot.com/3598041/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fix bookpart identifier crash with page-marker. (issue3585042)
LGTM; regtest comparison shows nothing unexpected, and the docs build from scratch. Please push. http://codereview.appspot.com/3585042/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Various to LM and NR from user email threads (issue3581041)
Lots of good discussion here, but I'm finding a bit confusing. James, could you extract whatever part(s) of your first patch that everybody agreed on, and make a separate patch that only does those? That way, we can get the obvious stuff pushed, and then focus on whatever not obvious stuff is left. I'd also suggest that once the obvious stuff is pushed, you create a patch for only 1 of the remaining files -- that will let us focus even more. Remember that patches should not only *be* good, they must be *seen* to be good. When there's a lot of unrelated stuff in the same patch, it's harder to see that stuff is good. http://codereview.appspot.com/3581041/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Installing ddd on LilyBuntu
I thought it'd be interesting to install the ddd graphical debugger on my LilyBuntu instance. I downloaded it OK, but when I run ./configure I get: configure: error: The X toolkit library '-lXt' could not be found. I can't find how to fix this with a Google search. Does anyone who runs/created LB know whether there is an X toolkit library installed? If so, what/where? If not, is it possible to install one? -- Phil Holmes Bug Squad ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Installing ddd on LilyBuntu
On Sun, Dec 12, 2010 at 06:13:35PM -, Phil Holmes wrote: I thought it'd be interesting to install the ddd graphical debugger on my LilyBuntu instance. I downloaded it OK, but when I run ./configure I get: As a general rule of thumb, never never ever download software for linux. Always use your package manager. Command-line: sudo aptitude install ddd Graphical: third top menu from the left, administration or preferences-synaptic package manager. this way, the system automatically installs (and configures!) any requirements to use whatever software you want. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Installing ddd on LilyBuntu
On 10-12-12 01:13 PM, Phil Holmes wrote: I thought it'd be interesting to install the ddd graphical debugger on my LilyBuntu instance. I downloaded it OK, but when I run ./configure I get: configure: error: The X toolkit library '-lXt' could not be found. You are missing the libxt-dev package. But, why do you want to build DDD yourself? If you simply want to use it to debug LilyPond, you can just install it from the repository. A lot easier, and will save you a lot of headache in the future. Also, is there a particular reason to prefer DDD for C++ debugging? I find Eclipse CDT a lot better in any thinkable respect. (But then again, I am biased, being one of the founders of the Eclipse project). ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Installing ddd on LilyBuntu
- Original Message - From: Boris Shingarov b...@shingarov.com To: lilypond-devel@gnu.org Sent: Sunday, December 12, 2010 6:46 PM Subject: Re: Installing ddd on LilyBuntu On 10-12-12 01:13 PM, Phil Holmes wrote: I thought it'd be interesting to install the ddd graphical debugger on my LilyBuntu instance. I downloaded it OK, but when I run ./configure I get: configure: error: The X toolkit library '-lXt' could not be found. You are missing the libxt-dev package. But, why do you want to build DDD yourself? If you simply want to use it to debug LilyPond, you can just install it from the repository. A lot easier, and will save you a lot of headache in the future. Also, is there a particular reason to prefer DDD for C++ debugging? I find Eclipse CDT a lot better in any thinkable respect. (But then again, I am biased, being one of the founders of the Eclipse project). The CG at http://lilypond.org/doc/v2.13/Documentation/contributor/debugging-c_002b_002b-code says As an alternative to running gdb at the command line you may try a graphical interface to gdb such as ddd: so I just did that. I knew nothing about package managers until Graham replied. Following that information, I'm now happily watching a debug window :-) -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Various to LM and NR from user email threads (issue3581041)
http://codereview.appspot.com/3581041/diff/1/Documentation/learning/fundamental.itely
File Documentation/learning/fundamental.itely (right):
http://codereview.appspot.com/3581041/diff/1/Documentation/learning/fundamental.itely#newcode2115
Documentation/learning/fundamental.itely:2115: no note heads are
produced and so no Stem or Beams are created either.}
On 2010/12/11 22:56:02, Neil Puttock wrote:
stems or beams
Leaving this file unedited for another patch until those other files
that have
consensus have been pushed.
http://codereview.appspot.com/3581041/diff/1/Documentation/notation/editorial.itely
File Documentation/notation/editorial.itely (right):
http://codereview.appspot.com/3581041/diff/1/Documentation/notation/editorial.itely#newcode145
Documentation/notation/editorial.itely:145: using the @code{fontSize}
property.
On 2010/12/11 22:56:02, Neil Puttock wrote:
This is a problem in markup only, thus applies to the \fontsize markup
command
(not the context property fontSize).
I suggested changing the definitions of the named commands to remove
the
inconsistency (via \abs-fontsize), but if we'd rather leave them as
they are
this knowissue should be moved to text.itely.
Done.
http://codereview.appspot.com/3581041/diff/1/Documentation/notation/repeats.itely
File Documentation/notation/repeats.itely (right):
http://codereview.appspot.com/3581041/diff/1/Documentation/notation/repeats.itely#newcode153
Documentation/notation/repeats.itely:153: number of endings. If you
must use bar checks then put
On 2010/12/10 23:41:50, Trevor Daniels wrote:
If you do use bar checks ...
Leaving this file unedited for another patch until those other files
that have consensus have been pushed.
http://codereview.appspot.com/3581041/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
http://codereview.appspot.com/3581041/diff/1/Documentation/notation/spacing.itely#newcode928
Documentation/notation/spacing.itely:928: @warning{Odd page numbers are
always on the right. If you want the
On 2010/12/11 14:01:10, Graham Percival wrote:
On 2010/12/11 00:36:29, Carl wrote:
I think that this should be a known issue, rather than a warning.
Agreed, this is definitely better as a known issue.
Done.
http://codereview.appspot.com/3581041/diff/1/Documentation/notation/staff.itely
File Documentation/notation/staff.itely (right):
http://codereview.appspot.com/3581041/diff/1/Documentation/notation/staff.itely#newcode278
Documentation/notation/staff.itely:278: @code{PianoStaff} does not, by
default, accept @code{ChordNames}.
On 2010/12/11 14:01:10, Graham Percival wrote:
This should be a known issue, instead of a warn... oh, oops, sorry,
it's already
a known issue. :)
Done.
http://codereview.appspot.com/3581041/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilybuntu 2
On Sun, Dec 12, 2010 at 12:27 PM, Graham Percival gra...@percival-music.ca wrote: I was hoping that guile 2.0 and/or texinfo 4.14 would be out by now, but it seems like that's going to be be released a few days after officially making lilybuntu 2. (not from insight into the development of either project; just an observation of the convenience of the universe) With that in mind, does anybody feel like cooking up lilybuntu 2 right now? I recommend - Ubuntu 10.04 LTS - nothing else fancy I'm on winter break right now, and I did the last lilybuntu so I can do this one too. I'll be glad to be able to contribute something again. It would be great if you could write a brief blurb about how to do it, because we'll probabaly want to update it once guile and texinfo have new releases. I'll take notes as I do it. Once 2.15 starts, I want to update the imagemagick compare command-line so that people with modern distributions can run the regtest check. However, that would break the regtest check in lilubuntu 1, which is not kosher. No urgency; I'm hoping to have lilybuntu 2 out in a month. I should be able to do it this week. Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
\unset Timing.defaultBarType does not work
Hi,
NR 1.2.5 Bars Bar lines states that
The default bar type used for automatically inserted bar lines is |.
If we change this towith \set Timing.defaultBarType =
\unset Timing.defaultBarType should change it back to | and print
again bar lines.
This is not the case.
\relative c' {
c1
c
\set Timing.defaultBarType =
c1
c
\unset Timing.defaultBarType % does not work
c1
c
\set Timing.defaultBarType = |
c1
c
}
Cheers,
Xavier
PS: \set is not working immediately, but only *after* the NEXT NOTE.
I suppose this is an inherent issue but it would be great if it could be
solved, it is really not logical and highly counter-intuitive...
--
Xavier Scheuer x.sche...@gmail.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
New Spanish PO file for 'lilypond' (version 2.13.42)
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Spanish team of translators. The file is available at: http://translationproject.org/latest/lilypond/es.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) All other PO files for your package are available in: http://translationproject.org/latest/lilypond/ Please consider including all of these in your next release, whether official or a pretest. Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context. The following HTML page has been updated: http://translationproject.org/domain/lilypond.html If any question arises, please contact the translation coordinator. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator. coordina...@translationproject.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \unset Timing.defaultBarType does not work
On Mon 13 Dec 2010, 00:45 Xavier Scheuer wrote:
Hi,
Hi!
NR 1.2.5 Bars Bar lines states that
The default bar type used for automatically inserted bar lines is |.
If we change this towith \set Timing.defaultBarType =
\unset Timing.defaultBarType should change it back to | and print
again bar lines.
This is not the case.
Thank you, added as 1447:
http://code.google.com/p/lilypond/issues/detail?id=1447
\relative c' {
c1
c
\set Timing.defaultBarType =
c1
c
\unset Timing.defaultBarType % does not work
c1
c
\set Timing.defaultBarType = |
c1
c
}
Cheers,
Xavier
PS: \set is not working immediately, but only *after* the NEXT NOTE.
I suppose this is an inherent issue but it would be great if it could be
solved, it is really not logical and highly counter-intuitive...
--
Dmytro O. Redchuk
Bug Squad
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
