Re: Copy pdf docs to new website folder (issue 5507046)
Hello, On 1 January 2012 23:14, wrote: > LGTM, but I had to add issue 2166 to track this. > > http://codereview.appspot.com/5507046/ This is now ready to 'push'. If you can attach a git formatted patch to the tracker http://code.google.com/p/lilypond/issues/detail?id=2166 I can push it for you, else I can download the diff from Rietveld. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
VirtualBox help
Hey all, In my GUB installation, my VirtualBox ran out of space and peetered out. So, I closed my VirtualBox down, resized the hard drive, and tried to boot again. However, it cannot restart (some message about GNOME power something something) and I think it's because the disk space is full. It's not even recognizing my root password :-/ Does anyone know how to do delete files on a VBox from the outside so that I can free up space? I know this question is more appropriate for a VirtualBox forum, but I figured that one of you may know... Alternatively, if that doesn't work, does anyone know how to recover files from a virtual hard drive? Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
Janek Warchoł writes:
>> \layout {
>> \context {
>> \Score
>> \with \settingsFrom { \compressFullBarRests }
>> }
>> \context {
>> \Staff
>> \with \settingsFrom { \accidentalStyle modern }
>> }
>> }
>> }
>> \end{lilypond}
>>
>> \ph is a music function written in Scheme. Can you understand it?
>
> Yes, but i get lost on \parallellMusic :(
It's intended for using. And yes, it likely could be simpler given
useful APIs for manipulating Scheme.
>> \settingsFrom is actually returning a Scheme expression for \with to
>> use. It makes things rather simpler than more complex, even though it
>> constitutes a Scheme expression.
>
> Um... i would really love to be able to type
> \layout {
> \compressFullBarRests
> \override Score.SpacingSpanner #'common-shortest-duration =
> #(ly:make-moment 6 10)
> etc...
> }
Well, create a layout modification type, let \layout accept Scheme
expressions of that type, write a Scheme function \layout-from in
analogue to \settingsFrom, and it becomes
\layout {
\layout-from { \compressFullBarRests
\override Score.SpacingSpanner #'common-shortest-duration =
#(ly:make-moment 6 10)
}
etc...
}
Stuff like that is reasonably straightforward to implement. It would
have the advantage that you don't have to know what contexts
\settingsFrom should be placed in.
Again:
>> Scheme is not hard. Programming is hard.
And sane program design is, apparently, even harder. People _don't_
_ever_ think about improving things. Instead they hobble along in
whatever clunky way they see others doing, complaining how clunky it is,
and likely making it much clunkier by bending it to situations fitting
even worse than what they have seen.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: VirtualBox help
Mike, On 4 January 2012 08:11, m...@apollinemike.com wrote: > Hey all, > > In my GUB installation, my VirtualBox ran out of space and peetered out. > So, I closed my VirtualBox down, resized the hard drive, and tried to boot > again. > > However, it cannot restart (some message about GNOME power something > something) and I think it's because the disk space is full. It's not even > recognizing my root password :-/ > Does anyone know how to do delete files on a VBox from the outside so that I > can free up space? I know this question is more appropriate for a VirtualBox > forum, but I figured that one of you may know... There are a couple of quick things you could do. 1. http://n00bsys0p.wordpress.com/2011/07/07/mount-partitions-from-a-virtualbox-vdi-in-linux/ I've not mounted a .vdi file in linux myself but I know that in Windows the various mount-and-browse .vdi files works well. I assume it is all default which is .vdi (you can choose the kind of 'Virtual Hard Disk' in later versions of VBOX - VHD, VMDK etc. but vdi is the default). 2. Create a new machine definition but point to the 'old' vdi as the boot drive - sometimes the problem is not so much in the OS but the XML def file that is associated with the vdi file. As long as you don't delete the vdi file itself (when you delete 'virtual machines' from the Vbox GUI you can opt to keep the files - which include the vdi file). 3. As 2 but use a new boot disk but also add an addition storage device and again point to the old vdi file, as if it were an addition separate piece of disk. > > Alternatively, if that doesn't work, does anyone know how to recover files > from a virtual hard drive? > See #1. Hope this helps. James PS this is why I use snapshots in Vbox :) -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
lilypond.patchy.gra...@gmail.com writes: > Begin LilyPond compile, commit: 2f25894efd8ad242b233d5a1d07afcfa087ebab2 > > Merged staging, now at: c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a > > Success:./autogen.sh --noconfigure > > Success:../configure --disable-optimising > > Success:nice make -j3 CPU_COUNT=3 > > Success:nice make test -j3 CPU_COUNT=3 > > *** FAILED BUILD *** > > nice make doc -j3 CPU_COUNT=3 > > Previous good commit: 2fd5a378f5d883536b1aac57583d261ce60a4043 > > Current broken commit: c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a My guess would be on commit 9f24e79a945ec4ab000d3e09ff2d2ac8208e2246 Author: Benkő Pál Date: Tue Jan 3 19:08:26 2012 +0100 do not tinker with pitched rest half rests should lie on a staff line, whole rests should hang from a staff line by default even for non-standard staves, except when the position is set by pitch. since c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a is just a rewording and quite trivial. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Segfault 2.15.23 Span_bar_stub_engraver
Jay Anderson writes: > On Tue, Jan 3, 2012 at 1:12 AM, m...@apollinemike.com > wrote: >> On Jan 3, 2012, at 9:02 AM, David Kastrup wrote: >>> If he hadn't rerun configure since before version 2.15.21, I think that >>> the compilation would likely have failed for other reasons. The problem >>> report is for 2.15.23. It may be worth for him to report the CXXFLAGS >>> setting in config.status just to be on the safe side, but I consider it >>> unlikely that this particular problem has not already been covered. >>> > > I pulled down lilypond and build new just last week. > > CXXFLAGS in config.status is: > - With optimization (default): "O2 -finline-functions -g -pipe > -fno-optimize-sibling-calls" > - Without optimization: "-g -pipe -fno-optimize-sibling-calls" > >> Are you using an optimized binary? Mine is unoptimized. Please try >> ./autogen.sh --disable-optimizing before compiling and let me know >> if that makes the segfault go away. > > I found --disable-optimising instead. Same result. > > I can't reproduce this on my wife's mac or on my laptop (also running > ubuntu 11.10). The only difference I can think of is I'm running > 64-bit and my laptop is 32-bit. Unless someone else can reproduce this > issue don't spend much more time on this. Can you use git bisect for identifying the commit where things go wrong for you? > I have a good solution (adding in the dynamics). Thanks! That sounds like a workaround rather than a solution. It would be good to find the actual reason. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Wed, Jan 04, 2012 at 09:38:57AM +0100, David Kastrup wrote: > lilypond.patchy.gra...@gmail.com writes: > > nice make doc -j3 CPU_COUNT=3 > > > > Previous good commit: 2fd5a378f5d883536b1aac57583d261ce60a4043 > > > > Current broken commit: c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a > > My guess would be on > > commit 9f24e79a945ec4ab000d3e09ff2d2ac8208e2246 > since c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a is just a rewording and > quite trivial. Apparently a later build succeeded. Either something's weird in Patchy, or it's yet another instance of some uninitialized variable or memory. Since there isn't much interest in cleaning up compiler warnings[1] so that we can use automatic tools to identify such problematic occurrences, I guess we'll just stumble forward as usual. [1] if your version of g++ doesn't find a ton of warnings -- on any architecture -- try using clang 3.0. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On Wed, Jan 04, 2012 at 12:48:49AM -0800, Graham Percival wrote: > Since there isn't much interest in cleaning > up compiler warnings[1] so that we can use automatic tools to > identify such problematic occurrences, I guess we'll just stumble > forward as usual. > > [1] if your version of g++ doesn't find a ton of warnings -- on > any architecture -- try using clang 3.0. This is a general form of "your" to mean "any person", not aimed specifically at David. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
Graham Percival writes: > On Wed, Jan 04, 2012 at 09:38:57AM +0100, David Kastrup wrote: >> lilypond.patchy.gra...@gmail.com writes: >> >nice make doc -j3 CPU_COUNT=3 >> > >> >Previous good commit: 2fd5a378f5d883536b1aac57583d261ce60a4043 >> > >> >Current broken commit: c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a >> >> My guess would be on >> >> commit 9f24e79a945ec4ab000d3e09ff2d2ac8208e2246 > >> since c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a is just a rewording and >> quite trivial. > > Apparently a later build succeeded. Either something's weird in > Patchy, or it's yet another instance of some uninitialized > variable or memory. My personal guess would be on parallel make. Uninitialized variable/memory situations usually are reproduceable with identical build. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: VirtualBox help
On 2012-01-04 09:11, m...@apollinemike.com wrote: In my GUB installation, my VirtualBox ran out of space and peetered out. So, I closed my VirtualBox down, resized the hard drive, and tried to boot again. You know, resizing the harddrive (i.e. partition) does not resize the filesystem itself. So your filesystem is still just as full as it was before. However, it cannot restart (some message about GNOME power something something) and I think it's because the disk space is full. It's not even recognizing my root password :-/ Yes, that's a typical sign... Does anyone know how to do delete files on a VBox from the outside so that I can free up space? I know this question is more appropriate for a VirtualBox forum, but I figured that one of you may know... There is a virtualbox-fuse file system, so you can mount a virtual harddrive and then delete files there Alternatively, if that doesn't work, does anyone know how to recover files from a virtual hard drive? I think you simply want to enlarge the file system to the full virtual harddisk size, right? There's that nice gparted live ISO image, from which you can boot your virtual machine (download the iso (~100MB), set it as the virtual box's CD drive, change boot order to boot from CD and run your virtualbox) and then resize the file system to the full available space. I did exactly that with my WinXP virtual machine and it worked just fine. 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 https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: VirtualBox help
On Jan 4, 2012, at 11:51 AM, Reinhold Kainhofer wrote: > On 2012-01-04 09:11, m...@apollinemike.com wrote: >> In my GUB installation, my VirtualBox ran out of space and peetered out. >> So, I closed my VirtualBox down, resized the hard drive, and tried to boot >> again. > > You know, resizing the harddrive (i.e. partition) does not resize the > filesystem itself. > So your filesystem is still just as full as it was before. >> However, it cannot restart (some message about GNOME power something >> something) and I think it's because the disk space is full. It's not even >> recognizing my root password :-/ > Yes, that's a typical sign... > >> Does anyone know how to do delete files on a VBox from the outside so that I >> can free up space? I know this question is more appropriate for a VirtualBox >> forum, but I figured that one of you may know... > > There is a virtualbox-fuse file system, so you can mount a virtual harddrive > and then delete files there >> Alternatively, if that doesn't work, does anyone know how to recover files >> from a virtual hard drive? > I think you simply want to enlarge the file system to the full virtual > harddisk size, right? > There's that nice gparted live ISO image, from which you can boot your > virtual machine (download the iso (~100MB), set it as the virtual box's CD > drive, change boot order to boot from CD and run your virtualbox) and then > resize the file system to the full available space. > > I did exactly that with my WinXP virtual machine and it worked just fine. Please disregard my previous e-mail - I answered my own questions. Rheinhold's suggestion worked like a charm. May his name be lauded in all the lands! Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: VirtualBox help
On 2012-01-04 12:05, m...@apollinemike.com wrote: Alternatively, if that doesn't work, does anyone know how to recover files from a virtual hard drive? I think you simply want to enlarge the file system to the full virtual harddisk size, right? There's that nice gparted live ISO image, from which you can boot your virtual machine (download the iso (~100MB), set it as the virtual box's CD drive, change boot order to boot from CD and run your virtualbox) and then resize the file system to the full available space. Opens up like a charm, but it seems that my drive is blocked @ 19.42 gigs (see screen shot) and that I can only fiddle with the swap space. Is this the right thing to do? You'll have to move (remove) the swap space so that you can enlarge your real data partition... 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 https://lists.gnu.org/mailman/listinfo/lilypond-devel
GUB calling 'false'
Hey all,
I'm getting adeptish at reading GUB barf, but what puzzles me is that the
command GUB called was 'false' (see the end of the copy and paste from the
logfile). Thoughts?
Cheers,
MS
MapLocate[/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root]
no files matching pattern: lib*.la
invoking rm -f
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/info/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/info/dir.old
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/share/info/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/share/info/dir.old
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/info/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/info/dir.old
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/share/info/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/share/info/dir.old
invoking LD_PRELOAD= cp -f sourcefiles/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/share/info/dir
invoking cd
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/share/info
&&
LILYPOND_EXTERNAL_BINARY=/home/mikesol/gub/target/linux-x86/root/usr/bin/lilypond
PATH=/home/mikesol/gub/target/tools/root/usr/bin:/home/mikesol/gub/target/linux-x86/root/usr/bin:$PATH
MALLOC_CHECK_=2
LD_LIBRARY_PATH=/home/mikesol/gub/target/tools/root/usr/lib:/home/mikesol/gub/target/linux-x86/root/usr/lib:${LD_LIBRARY_PATH-/foe}
GS_FONTPATH=/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/fonts:/home/mikesol/gub/target/linux-x86/root/usr/share/gs/fonts
GS_LIB=/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/Resource/Init:/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/Resource
install-info --info-dir=. lilypond-notation.info
install-info: warning: no info dir entry in `lilypond-notation.info'
invoking LD_PRELOAD= tar -C
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root -cjf
/home/mikesol/gub/uploads/lilypond-2.15.23-2.documentation.tar.bz2 .
invoking LD_PRELOAD= tar --exclude '*.signature' -C
/home/mikesol/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/out-www/online-root
-cjf /home/mikesol/gub/uploads/lilypond-2.15.23-2.webdoc.tar.bz2 .
Running dump_file
('install',
'/home/mikesol/gub/target/linux-x86/status/lilypond-doc-2.15.23-f3686ac8951d6627146d5224dc4660598ea8abe5',
'w')
{'permissions': 420}
*** Stage: package (lilypond-doc, linux-x86)
invoking false
Command barfed: false
Traceback (most recent call last):
File "bin/gub", line 233, in exceptional_build
build (settings, options, files)
File "bin/gub", line 229, in build
b.build_source_packages (names)
File "bin/../gub/buildrunner.py", line 334, in build_source_packages
self.spec_build (spec_name)
File "bin/../gub/buildrunner.py", line 262, in spec_build
deferred_runner.execute_deferred_commands ()
File "bin/../gub/runner.py", line 167, in execute_deferred_commands
cmd.execute (self.logger)
File "bin/../gub/commands.py", line 75, in execute
ignore_errors=self.ignore_errors)
File "bin/../gub/loggedos.py", line 93, in system
raise misc.SystemFailed (m)
SystemFailed: Command barfed: false
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Copy pdf docs to new website folder (issue 5507046)
On Wed, Jan 4, 2012 at 8:05 AM, James wrote: > Hello, > > On 1 January 2012 23:14, wrote: >> LGTM, but I had to add issue 2166 to track this. >> >> http://codereview.appspot.com/5507046/ > > This is now ready to 'push'. > > If you can attach a git formatted patch to the tracker > > http://code.google.com/p/lilypond/issues/detail?id=2166 > > I can push it for you, else I can download the diff from Rietveld. Attached. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB calling 'false'
"m...@apollinemike.com" writes: > Hey all, > > I'm getting adeptish at reading GUB barf, but what puzzles me is that > the command GUB called was 'false' (see the end of the copy and paste > from the logfile). Thoughts? It would be called explicitly to generate an exit status indicating failure. A typical application would be configure not finding a utility, and setting the respective environment variable (like TEX or whatever else) to false, with the expectation that this will only cause problems with some optional Makefile targets, not affecting the main compilation. I have not done any analysis of your specific problem, but maybe this rationale may help you in figuring out what is happening in your case. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB calling 'false'
- Original Message -
From:
To: "lilypond-devel Development"
Sent: Wednesday, January 04, 2012 12:04 PM
Subject: GUB calling 'false'
Hey all,
I'm getting adeptish at reading GUB barf, but what puzzles me is that the
command GUB called was 'false' (see the end of the copy and paste from the
logfile). Thoughts?
Cheers,
MS
MapLocate[/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root]
no files matching pattern: lib*.la
invoking rm -f
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/info/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/info/dir.old
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/share/info/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/share/info/dir.old
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/info/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/info/dir.old
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/share/info/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/usr/cross/share/info/dir.old
invoking LD_PRELOAD= cp -f sourcefiles/dir
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/share/info/dir
invoking cd
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root/share/info
&&
LILYPOND_EXTERNAL_BINARY=/home/mikesol/gub/target/linux-x86/root/usr/bin/lilypond
PATH=/home/mikesol/gub/target/tools/root/usr/bin:/home/mikesol/gub/target/linux-x86/root/usr/bin:$PATH
MALLOC_CHECK_=2
LD_LIBRARY_PATH=/home/mikesol/gub/target/tools/root/usr/lib:/home/mikesol/gub/target/linux-x86/root/usr/lib:${LD_LIBRARY_PATH-/foe}
GS_FONTPATH=/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/fonts:/home/mikesol/gub/target/linux-x86/root/usr/share/gs/fonts
GS_LIB=/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/Resource/Init:/home/mikesol/gub/target/linux-x86/root/usr/share/ghostscript/8.70/Resource
install-info --info-dir=. lilypond-notation.info
install-info: warning: no info dir entry in `lilypond-notation.info'
invoking LD_PRELOAD= tar -C
/home/mikesol/gub/target/linux-x86/install/lilypond-doc-2.15.23-root -cjf
/home/mikesol/gub/uploads/lilypond-2.15.23-2.documentation.tar.bz2 .
invoking LD_PRELOAD= tar --exclude '*.signature' -C
/home/mikesol/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/out-www/online-root
-cjf /home/mikesol/gub/uploads/lilypond-2.15.23-2.webdoc.tar.bz2 .
Running dump_file
('install',
'/home/mikesol/gub/target/linux-x86/status/lilypond-doc-2.15.23-f3686ac8951d6627146d5224dc4660598ea8abe5',
'w')
{'permissions': 420}
*** Stage: package (lilypond-doc, linux-x86)
invoking false
Command barfed: false
Traceback (most recent call last):
File "bin/gub", line 233, in exceptional_build
build (settings, options, files)
File "bin/gub", line 229, in build
b.build_source_packages (names)
File "bin/../gub/buildrunner.py", line 334, in build_source_packages
self.spec_build (spec_name)
File "bin/../gub/buildrunner.py", line 262, in spec_build
deferred_runner.execute_deferred_commands ()
File "bin/../gub/runner.py", line 167, in execute_deferred_commands
cmd.execute (self.logger)
File "bin/../gub/commands.py", line 75, in execute
ignore_errors=self.ignore_errors)
File "bin/../gub/loggedos.py", line 93, in system
raise misc.SystemFailed (m)
SystemFailed: Command barfed: false
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Can't help the specific, but I'm assuming this uses make? If so, you can
get (often lots of) extra information with the -d flag - i.e. make -d
target. Might give you extra info on what it's doing when it fails. Oh -
and redirect the output to a logfile with make -d target &> logfile.txt so
you can check more precisely what's going on.
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond hangs
[lilypond 35b7fddf]
I've just downloaded
http://www.mutopiaproject.org/ftp/BachJS/BWV1004/bwv-1004_5/bwv-1004_5.ly
applied this patch
--- BWV-1004_5.orig.ly 2012-01-04 14:17:02.0 +0100
+++ BWV-1004_5.ly 2012-01-04 14:10:15.0 +0100
@@ -1,9 +1,10 @@
-\version "2.13.10"
+\version "2.15.20"
\paper {
-page-top-space = #0.0
-%indent = 0.0
-line-width = 18.0\cm
+paper-width= 19000\cm
+paper-height = 10\cm
+line-width = 18000\cm
+ragged-right = ##t
ragged-bottom = ##f
ragged-last-bottom = ##f
}
and executed
lilypond BWV-1004_5.ly
Result: lilypond loops (at least it runs more than 10 minutes without
progress), slowly eating more and more memory.
Without the patch (this is, using normal line widths), it runs just
fine.
Debugging shows that the function System::gen_simple_spacers loops
forever.
Am I just too impatient or is this a real bug?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
On Jan 4, 2012, at 2:27 PM, Werner LEMBERG wrote:
>
> [lilypond 35b7fddf]
>
> I've just downloaded
>
> http://www.mutopiaproject.org/ftp/BachJS/BWV1004/bwv-1004_5/bwv-1004_5.ly
>
> applied this patch
>
> --- BWV-1004_5.orig.ly 2012-01-04 14:17:02.0 +0100
> +++ BWV-1004_5.ly 2012-01-04 14:10:15.0 +0100
> @@ -1,9 +1,10 @@
> -\version "2.13.10"
> +\version "2.15.20"
>
> \paper {
> -page-top-space = #0.0
> -%indent = 0.0
> -line-width = 18.0\cm
> +paper-width= 19000\cm
> +paper-height = 10\cm
> +line-width = 18000\cm
> +ragged-right = ##t
> ragged-bottom = ##f
> ragged-last-bottom = ##f
> }
>
> and executed
>
> lilypond BWV-1004_5.ly
>
> Result: lilypond loops (at least it runs more than 10 minutes without
> progress), slowly eating more and more memory.
>
> Without the patch (this is, using normal line widths), it runs just
> fine.
>
> Debugging shows that the function System::gen_simple_spacers loops
> forever.
>
> Am I just too impatient or is this a real bug?
>
>
>Werner
Probably a real bug.
The patch (which I wrote) was a crappy patch to begin with: I applied it to be
able to do some experiments with horizontal spacing, which I did, but they all
lead to circular dependencies so I gave up. I thought the change was innocuous
but if it's not there's no point keeping it - we can just revert.
I've posted a patch to fix this - if you get a chance, run the file with that
patch and lemme know if it causes any issues.
Cheers,
MS
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Removes ugly side bars from learning (issue 5498089)
On 3 jan 2012, at 11:32, Phil Holmes wrote: > - Original Message - From: > To: ; ; ; > ; ; > Cc: ; > Sent: Monday, January 02, 2012 9:23 PM > Subject: Re: Removes ugly side bars from learning (issue 5498089) > > >> could we get those @* turned into @example ? Just grit your teeth and >> ignore the yellow boxes for now? >> >> If you want to add a comment to remind us to change the @example when we >> have a better way of doing this, go ahead. >> >> http://codereview.appspot.com/5498089/ >> > > That's what I've done on my local-not-uploaded-for-review copy. Please stop including me in these mails. /Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
On 3 January 2012 21:47, Janek Warchoł wrote:
>
> > I am a TeX specialist, system programmer, Emacs specialist, the GNU
> > maintainer (and a rather pitiful one) for AUCTeX (lytex and itexi
> > anybody? preview-latex for Lilypond?)
Mmm... Preview for Lilypond? Sounds like a good start for a realtime GUI
for Lilypond (a better Denemo). I believe this will result in a fast
increase in number of Lilypond users. What do you think?
> I would have no problems spending a few hundred man years focused on
> > Lilypond. Except that I don't have a few hundred man years. Nobody
> > has. The next best option is spending time on multipliers. Getting
> > LilyPond in a shape where passersby find it intriguing, to a degree
> > where they get hooked and contribute manmonths of work over some time
> > without having planned to do so at the start.
>
> +1
>
and:
> > The only thing that is going to help is more eyes, more people who get
> interested, more people discovering dark corners and doing something
> about them.
and:
> To get there, we need serious programmers and serious musicians
> interested seriously in LilyPond. To a level where they start asking
> good questions. And we better be in a position to provide answers,
> since there is no more effective way to spend our time than on getting
> more people to spend their time, and love, and interest.
and:
> That's like + from me!
> In general, i agree that we should think in a more 'release-oriented'
> way ("last stable release was half a year ago, so we should make
> another one, so i'm fixing whatever needs to be fixed to make this
> possible") instead of 'free coding' way ("i care about this issue,
> i'll fix it. And that one. Oh, we have 0 criticals, so let's make a
> stable release before an obstruction occurs!"). To do so, we would
> have to work more as a team, less independently. How can we achieve
> that if GOP7 showed that we don't want to?
and:
> And we better be in a position to provide answers,
> > since there is no more effective way to spend our time than on getting
> > more people to spend their time, and love, and interest.
Regarding all those fragments of Janek's and David's emails: For some time
I have been observing how bug are being fixed in Lilypond and spent some
time on conversations with Janek.
For me there is almost no team work in Lilypond - only a bunch of geek
trying to fix some issues, but without a leader who coordinates all
actions. As far as I remember, some time ago you have tried hard to make
some big changes in Lilypond, but finally there was no big revolution...
Without a leader that will make key design & implementation decisions
Lilypond will improve in a slow pace, letting Finale and Sibellius gain
more and more users. Probably some of you will return to the old row - is a
goal of a Lilypond to substitue Finale or compete with Sibellius. I think
there is no point in loosing your energy *and time* on that.
Instead we should do as much as possible to constantly improve Lilypond.
That means not only fixing critical bugs, but also: anticipating future
stability problems, constantly improving end user documentation and the
quality of source code (reduce complexity, comment code and so on). By now
there is a huge work to be done and Lilypond needs someone who will form
guidelines and priorities.
Łukasz (Luke)
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to measure the code coverage of scheme part in Lilypond?
Thank you. The problem is i do not know how to call 'with-code-coverage' in Lilypond when executing the command "lilypond filename.ly". 2012/1/4 Ludovic Courtès > Hi Kai, > > Can you please reply to guile-u...@gnu.org and perhaps the Lilypond user > list too? This will allow others to contribute to the discussion or > learn from it. > > Kai Yu skribis: > > > Could you tell me how to collect code coverage of scheme when I executing > > the command "lilypond filename.ly"? BTW, I am a green hand of scheme > > language. > > Guile 2.0 has support for this (info "(guile) Code Coverage"). This > could be used for Lilypond, but you may have to add just a few lines of > Scheme code in Lilypond to call ‘with-code-coverage’ & co. > > I don’t know the specifics of Lilypond, so I can’t tell you exactly > where to add that. > > Thanks, > Ludo’. > > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
"m...@apollinemike.com" writes: > Probably a real bug. > > The patch (which I wrote) was a crappy patch to begin with: I applied > it to be able to do some experiments with horizontal spacing, which I > did, but they all lead to circular dependencies so I gave up. I > thought the change was innocuous but if it's not there's no point > keeping it - we can just revert. No change introducing any amount of complexity without purpose is innocuous. It will slow down people understanding LilyPond's code. In particular, if not even the patch author itself understands the code. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
> Probably a real bug. It seems so, but: > I've posted a patch to fix this - if you get a chance, run the file > with that patch and lemme know if it causes any issues. after applying your patch (http://codereview.appspot.com/5511044), it still loops, this time in `get_line_forces'. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
Łukasz Czerwiński writes: > On 3 January 2012 21:47, Janek Warchoł wrote: > >> >> > I am a TeX specialist, system programmer, Emacs specialist, the GNU >> > maintainer (and a rather pitiful one) for AUCTeX (lytex and itexi >> > anybody? preview-latex for Lilypond?) > > Mmm... Preview for Lilypond? Sounds like a good start for a realtime > GUI for Lilypond (a better Denemo). I believe this will result in a > fast increase in number of Lilypond users. What do you think? It won't. People who are into Emacs won't be into Finale or Sibelius anyway. It will increase the ratio of LilyPond users using Emacs for editing, and possibly the productivity of users of that combination. But recruiting new users to both LilyPond and Emacs at the same time is not going to show impressive results. It is a reasonable expectation to get preview-latex cooperate with lilypond-book in LaTeX mode with reasonable effort. To yield a sizable boost in productivity for LilyPond development, however, preview-latex would have to cooperate with Texinfo. Technologically, this is challenging and exciting. Unfortunately, for myself the excitement is somewhat stale since I already implemented preview-latex once. > Regarding all those fragments of Janek's and David's emails: For some time > I have been observing how bug are being fixed in Lilypond and spent some > time on conversations with Janek. > For me there is almost no team work in Lilypond - only a bunch of geek > trying to fix some issues, but without a leader who coordinates all > actions. We have coordinated procedures in place that several people spend sizable amounts of time on. This concerns the way new contributions are channeled, and how bugs get registered and releases get made. Graham is doing a lot of work keeping just that going and coordinated. New developments are not coordinated to a significant degree, and part of the reason is that there are no free resources to coordinate. > As far as I remember, some time ago you have tried hard to make some > big changes in Lilypond, but finally there was no big revolution... I am not sure who you are addressing. Nominally, you are replying to Janek, and Janek did spacing changes he not just tried to get through, but actually did. If you are trying to address my work: I did a lot of big changes to LilyPond but you would not notice much of it unless you read the manual, and even then much of it is underdocumented. A lot of it is hidden in making naively written code work and giving more power more easily accessible to the somewhat above-average user as opposed to the geniuses required before. > Without a leader that will make key design & implementation decisions > Lilypond will improve in a slow pace, letting Finale and Sibellius > gain more and more users. Forget Finale and Sibelius. They are not a problem we need to address since they are competing in a different space. Our real problem is LilyPond. > Probably some of you will return to the old row - is a goal of a > Lilypond to substitue Finale or compete with Sibellius. I think there > is no point in loosing your energy *and time* on that. Instead we > should do as much as possible to constantly improve Lilypond. Preaching to the choir, I see. > That means not only fixing critical bugs, but also: anticipating > future stability problems, constantly improving end user documentation > and the quality of source code (reduce complexity, comment code and so > on). By now there is a huge work to be done and Lilypond needs someone > who will form guidelines and priorities. There is no point in working on guidelines and priorities without capacities that would be guided and prioritized by them. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
> after applying your patch (http://codereview.appspot.com/5511044), it
> still loops, this time in `get_line_forces'.
Well, it doesn't loop.
Look at the attached two files:
The first file has 74 bars of a single voice, and `time' shows me the
following for processing it:
real0m52.985s
user0m52.707s
sys 0m0.188s
The other one is the same as the first file but has only 37 bars
real0m4.447s
user0m4.332s
sys 0m0.104s
It seems that we have some very bad exponential behaviour in
processing somewhere...
Conclusion: I was too impatient. I should have waited a few days
until lilypond will have completed the chaconne. My suggestion is to
send a copy of the current lilypond executable to the ASLSP project:
http://www.john-cage.halberstadt.de/
Werner
\version "2.15.20"
\paper {
paper-width= 19000\cm
paper-height = 10\cm
line-width = 18000\cm
ragged-right = ##t
ragged-bottom = ##f
ragged-last-bottom = ##f
}
#(set-global-staff-size 19)
% The score definition
melodyOne = \relative a' {
a4. a8 | % 1
e'4 e4. e8 | % 2
f4 d4. c8 | % 3
bes4 a g16 [( f e f ) ] | % 4
g16 [ ( e ) f ( d ) ] a'4. a8 | % 5
e'4 e4. e8 | % 6
f4 d4. d8 | % 7
bes'4 a8. [ g32 f ] g8. [ e16 ] | % 8
f8. s16 s2 | % 9 - Var 02
e8 r8 e8 r8 s4 | % 10
f8 r8 d8. [ f16] e8. [ d16] | % 11
d8 r8 cis8 r8 r8. a'16 | % 12
f8 s8 s2 | % 13 - Var 03
e8 r8 e8 r8 s4 | % 14
e8 r8 d8. [ f16 ] e8. [ cis16 ] | % 15
d8. [ e16 ] d4 ( cis8.) [ d16 ] | % 16
d8. [ e16 ] f8. [ g32 a ] bes8. [ f16 ] | % 17
e8. [ bes'16 ] a8. [ g16 ] a8. [ fis16 ] | % 18
g8. [ f16 ] e8. [ d32 cis ] d8. [ e16 ] | % 19
f8. [ g16 ] e8. [ f16 ] g8. [ e16 ] | % 20
f8. [ d32 e ] f8. [ g32 a ] bes8. [ f16 ] | % 21
e8. [ bes'16 ] a8. [ g16 ] a8. [ fis16 ] | % 22
g8. [ f16 ] e8. [ d32 cis ] d8. [ e16 ] | % 23
f8. [ g16 ] d8. [ cis32 b ] cis8. [ g16 ] | % 24
f8 [ f' e d cis d ] | % 25 - Var 06
g,8 [ a16 ( bes ) ] cis,8 [ bes' a g ] | % 26
f8 [ g16 ( a ) ] bes,8 [ d g d'16 ( cis ) ] | % 27
d8 [ f,8 ] e16 [ f g bes ] a [ g f e ] | % 28
f16 [ ( a d f ) ] f [ ( e g f ] e [ d cis d ) ] | % 29
g,16 [ bes fis g ] cis, [( e g ) bes ] a [ g e' g, ] | % 30
f16 [ cis d a ] bes [ ( d g ) a ] bes [ es cis d ] | % 31
gis,16 [( b d ) f ] e [ g cis, d ] a, [ ( e' d' ) cis ] | % 32
d8 [ f bes a gis d, ] | % 33
cis8 [ e' a g fis c, ] | % 34
b8 [ d' g f e bes, ] | % 35
a16 [ f'' e d ] cis8 [ a8 e'8 g,8 ] | % 36
f16 [ d f a ] d [ ( f bes ) a ] gis [ b gis e ] | % 37
}
melody = << \melodyOne >>
% The score definition
\score {
\context Staff <<
\set Staff.instrumentName = "Violine"
{ \clef treble \key d \minor \time 3/4 \partial 2 \melody }
>>
\layout { }
}
\version "2.15.20"
\paper {
paper-width= 19000\cm
paper-height = 10\cm
line-width = 18000\cm
ragged-right = ##t
ragged-bottom = ##f
ragged-last-bottom = ##f
}
#(set-global-staff-size 19)
% The score definition
melodyOne = \relative a' {
a4. a8 | % 1
e'4 e4. e8 | % 2
f4 d4. c8 | % 3
bes4 a g16 [( f e f ) ] | % 4
g16 [ ( e ) f ( d ) ] a'4. a8 | % 5
e'4 e4. e8 | % 6
f4 d4. d8 | % 7
bes'4 a8. [ g32 f ] g8. [ e16 ] | % 8
f8. s16 s2 | % 9 - Var 02
e8 r8 e8 r8 s4 | % 10
f8 r8 d8. [ f16] e8. [ d16] | % 11
d8 r8 cis8 r8 r8. a'16 | % 12
f8 s8 s2 | % 13 - Var 03
e8 r8 e8 r8 s4 | % 14
e8 r8 d8. [ f16 ] e8. [ cis16 ] | % 15
d8. [ e16 ] d4 ( cis8.) [ d16 ] | % 16
d8. [ e16 ] f8. [ g32 a ] bes8. [ f16 ] | % 17
e8. [ bes'16 ] a8. [ g16 ] a8. [ fis16 ] | % 18
g8. [ f16 ] e8. [ d32 cis ] d8. [ e16 ] | % 19
f8. [ g16 ] e8. [ f16 ] g8. [ e16 ] | % 20
f8. [ d32 e ] f8. [ g32 a ] bes8. [ f16 ] | % 21
e8. [ bes'16 ] a8. [ g16 ] a8. [ fis16 ] | % 22
g8. [ f16 ] e8. [ d32 cis ] d8. [ e16 ] | % 23
f8. [ g16 ] d8. [ cis32 b ] cis8. [ g16 ] | % 24
f8 [ f' e d cis d ] | % 25 - Var 06
g,8 [ a16 ( bes ) ] cis,8 [ bes' a g ] | % 26
f8 [ g16 ( a ) ] bes,8 [ d g d'16 ( cis ) ] | % 27
d8 [ f,8 ] e16 [ f g bes ] a [ g f e ] | % 28
f16 [ ( a d f ) ] f [ ( e g f ] e [ d cis d ) ] | % 29
g,16 [ bes fis g ] cis, [( e g ) bes ] a [ g e' g, ] | % 30
f16 [ cis d a ] bes [ ( d g ) a ] bes [ es cis d ] | % 31
gis,16 [( b d ) f ] e [ g cis, d ] a, [ ( e' d' ) cis ] | % 32
d8 [ f bes a gis d, ] | % 33
cis8 [ e' a g fis c, ] | % 34
b8 [ d' g f e bes, ] | % 35
a16 [ f'' e d ] cis8 [ a8 e'8 g,8 ] | % 36
f16 [ d f a ] d [ ( f bes ) a ] gis [ b gis e ] | %
Fixes mingw woes for Python (issue 5511046)
LGTM Carl http://codereview.appspot.com/5511046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reverts public interface for simple spacer. (issue 5511044)
LGTM. Carl http://codereview.appspot.com/5511044/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Updates makelsr to point to lilypond exe (issue 5489134)
- Original Message - From: To: ; Cc: ; Sent: Monday, January 02, 2012 9:11 PM Subject: Re: Updates makelsr to point to lilypond exe (issue 5489134) great idea! A few implementation quibbles, though. Thought I'd responded to this, but can't find a record of doing so. http://codereview.appspot.com/5489134/diff/1/scripts/auxiliar/makelsr.py File scripts/auxiliar/makelsr.py (right): http://codereview.appspot.com/5489134/diff/1/scripts/auxiliar/makelsr.py#newcode76 scripts/auxiliar/makelsr.py:76: lilypondexe=conv_path+'lilypond' I have a slight preference for lilypond_bin but this isn't a serious complaint. No worries - I'll change it. http://codereview.appspot.com/5489134/diff/1/scripts/auxiliar/makelsr.py#newcode184 scripts/auxiliar/makelsr.py:184: e = os.system (lilypondexe + " -dno-print-pages -dsafe -o /tmp/lsrtest " + dest) 1. why did you remove the -V flag? Because, IMHO, it produces a load of spurious garbage that is rarely of any interest for any reason. It certainly doesn't add anything to running makelsr - it just clutters the output out - it could be removed with more redirections, but I've got other places to sort that out. 2. AFAIK if you simply do + dest, it will break if there are any snippets with a space in the filename. I think that as a policy we don't allow those, but the '%s' % dest solution avoids that potential problem. Why not keep it there? http://codereview.appspot.com/5489134/ I couldn't make the %s syntax work. If you could quickly save me some time and provide syntax, I'll do it. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
David Kastrup writes:
> Janek Warchoł writes:
>
>>> \layout {
>>> \context {
>>> \Score
>>> \with \settingsFrom { \compressFullBarRests }
>>> }
>>> \context {
>>> \Staff
>>> \with \settingsFrom { \accidentalStyle modern }
>>> }
>>> }
>>> }
>>> \end{lilypond}
>>>
>>> \ph is a music function written in Scheme. Can you understand it?
>>
>> Yes, but i get lost on \parallellMusic :(
>
> It's intended for using. And yes, it likely could be simpler given
> useful APIs for manipulating Scheme.
>
>>> \settingsFrom is actually returning a Scheme expression for \with to
>>> use. It makes things rather simpler than more complex, even though it
>>> constitutes a Scheme expression.
>>
>> Um... i would really love to be able to type
>> \layout {
>> \compressFullBarRests
>> \override Score.SpacingSpanner #'common-shortest-duration =
>> #(ly:make-moment 6 10)
>> etc...
>> }
>
> Well, create a layout modification type, let \layout accept Scheme
> expressions of that type, write a Scheme function \layout-from in
> analogue to \settingsFrom, and it becomes
>
> \layout {
>\layout-from { \compressFullBarRests
> \override Score.SpacingSpanner #'common-shortest-duration =
> #(ly:make-moment 6 10)
>}
>etc...
> }
>
> Stuff like that is reasonably straightforward to implement. It would
> have the advantage that you don't have to know what contexts
> \settingsFrom should be placed in.
"layout-from" =
#(define-void-function (parser location music)
(ly:music?)
(_i "To be used in output definitions. Take the layout instruction
events from @var{music} and do the equivalent of context modifications
duplicating their effect.")
(define (musicop m mods)
(if (music-is-of-type? m 'layout-instruction-event)
(ly:add-context-mod
mods
(case (ly:music-property m 'name)
((PropertySet)
(list 'assign
(ly:music-property m 'symbol)
(ly:music-property m 'value)))
((PropertyUnset)
(list 'unset
(ly:music-property m 'symbol)))
((OverrideProperty)
(list 'push
(ly:music-property m 'symbol)
(ly:music-property m 'grob-property-path)
(ly:music-property m 'grob-value)))
((RevertProperty)
(list 'pop
(ly:music-property m 'symbol)
(ly:music-property m 'grob-property-path)
(case (ly:music-property m 'name)
((SequentialMusic SimultaneousMusic)
(for-each (lambda (x)
(musicop x mods))
(ly:music-property m 'elements)))
((ContextSpeccedMusic)
(module-set! (current-module)
(ly:music-property m 'context-type)
#{ \context { $(module-ref (current-module)
(ly:music-property m
'context-type))
$(musicop (ly:music-property m
'element)
(ly:make-context-mod))
} #}
mods)
(musicop music (ly:make-context-mod)))
It is a bit wonky, but should work for most purposes.
At least it works with
\layout-from \accidentalStyle "dodecaphonic"
and with the above example.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
(was) Some drum notation questions - (now) problem with noteheads in doc?
On 4 January 2012 18:55, James wrote: > Hello, > > On 4 January 2012 18:32, Vaylor Trucks wrote: >> I have been using lilypond for years for my own projects and have recently >> introduced it to a friend of mine. He is a drum instructor and has been >> reading >> drum notation for many years. He's pointed out some things that are >> non-standard about the way lilypond handles some drum notation tasks. Most >> of >> these I have been able to correct using a #(define block. There are, >> however, >> some things I have not yet been able to crack. >> >> First, for hi-hat, the notation for open and closed are correct, but for the >> half-open he would like to appear exactly like the open hi-hat notation, >> except >> the "o" above the stem of the note needs to have a single slash through it. >> >> Also, the note head for a China cymbal he notes by having a standard cross >> note >> head, but with a box around it. >> >> Can anyone point me in the right direction for making these changes? > > I have no experience of doing this but you might want to start here > > http://lilypond.org/doc/v2.14/Documentation/notation/modifying-stencils > > The percussion notes are all here: > > http://lilypond.org/doc/v2.14/Documentation/notation/percussion-notes I've just noticed that most of the note heads on http://lilypond.org/doc/v2.14/Documentation/notation/percussion-notes here are semibreves insetad of I assume lots of crosses and circles etc. The PDF from 2.15.22 also show this. Can someone verify this? -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Patches NSIS (issue 5498107)
Overall, I think it wiser to avoid touching the windows path, *but* this
concept has been reported to resolve the problem.
http://nsis.sourceforge.net/Special_Builds
If you can run GUB, can you try putting the changed parameter on the
scons command line, rather than patching the default parameters.
Changes in the upstream nsis could easily cause the patch no not apply.
http://codereview.appspot.com/5498107/diff/1/gub/specs/nsis.py
File gub/specs/nsis.py (right):
http://codereview.appspot.com/5498107/diff/1/gub/specs/nsis.py#newcode14
gub/specs/nsis.py:14: scons_flags = misc.join_lines ('''
NSIS_MAX_STRLEN=8192
http://codereview.appspot.com/5498107/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patches NSIS (issue 5498107)
- Original Message -
From:
To:
Cc: ;
Sent: Wednesday, January 04, 2012 7:00 PM
Subject: Patches NSIS (issue 5498107)
Overall, I think it wiser to avoid touching the windows path, *but* this
concept has been reported to resolve the problem.
http://nsis.sourceforge.net/Special_Builds
If you can run GUB, can you try putting the changed parameter on the
scons command line, rather than patching the default parameters.
Changes in the upstream nsis could easily cause the patch no not apply.
http://codereview.appspot.com/5498107/diff/1/gub/specs/nsis.py
File gub/specs/nsis.py (right):
http://codereview.appspot.com/5498107/diff/1/gub/specs/nsis.py#newcode14
gub/specs/nsis.py:14: scons_flags = misc.join_lines ('''
NSIS_MAX_STRLEN=8192
http://codereview.appspot.com/5498107/
I think this is highly likely to be the problem. Yesterday I tried putting
long strings into Windows registry, and got to over 70k characters before I
got bored. I concluded that it wasn't a problem with the length of strings
in the registry and therefore less likely to be a "feature" of windows PATH.
I assume that what happens is the path gets close to the NSIS string size
limit, is read, appended to, and thus truncated, and is then written back to
the registry.
If someone with GUB capability can create a test patch, I'd be happy to try
it out (tho' not tomorrow - working).
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Updates makelsr to point to lilypond exe (issue 5489134)
ok, I'm fine with removing the -V.
http://codereview.appspot.com/5489134/diff/1/scripts/auxiliar/makelsr.py
File scripts/auxiliar/makelsr.py (right):
http://codereview.appspot.com/5489134/diff/1/scripts/auxiliar/makelsr.py#newcode184
scripts/auxiliar/makelsr.py:184: e = os.system (lilypondexe + "
-dno-print-pages -dsafe -o /tmp/lsrtest " + dest)
e = os.system ("%s -dno-print-pages -dsafe -o /tmp/lsrtest '%s'" %
(lilypondexe, dest))
should do the trick
http://codereview.appspot.com/5489134/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
[PATCH] Documentation search - update version and Google syntax
Hello! There are two issues with the search box in the online documentation. One is that search in v2.15 documentation adds +v2.14 to the Google search, so it look in the older documentation. The other is that "+" doesn't have the old meaning since the introduction of Google Plus. To ensure that "v2.15" appears on the page or in the URL, it should be added in quotes. A simpler alternative would be to use this in the search: site:lilypond.org/doc/v2.15 That would tell Google to search documents only under lilypond.org/doc/v2.15, which is probably our intention. Here's the patch. Please let me know if a sign off or something like that is needed. It's my first ever patch for LilyPond. Doc search: update to version 2.15, use it in the "site:" part site:lilypond.org/doc/v2.15 means that we want to look only under that directory. Leading plus doesn't force the exact search anymore. --- Documentation/search-box.ihtml |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/search-box.ihtml b/Documentation/search-box.ihtml index d789109..1c9ceb4 100644 --- a/Documentation/search-box.ihtml +++ b/Documentation/search-box.ihtml @@ -1,11 +1,11 @@ http://google.com/search"; method="get" name="search" - onSubmit="search.q.value='site:lilypond.org +v2.14 ' + onSubmit="search.q.value='site:lilypond.org/doc/v2.15 ' + search.brute_query.value" - onMouseMove="search.q.value='site:lilypond.org +v2.14 ' + onMouseMove="search.q.value='site:lilypond.org/doc/v2.15 ' + search.brute_query.value" - onKeyUp="search.q.value='site:lilypond.org +v2.14 ' + onKeyUp="search.q.value='site:lilypond.org/doc/v2.15 ' + search.brute_query.value"> -- Regards, Pavel Roskin ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: problem with checking out staging branch
2012/1/4 David Kastrup : > Janek Warchoł writes: > >> 2012/1/3 Janek Warchoł : >>> 2012/1/3 David Kastrup : You don't have staging in your fetch line. That's why I recommended fetching * instead of just master. >>> >>> Ah!! You see, i wasn't smart enough to understand what you wrote >>> about that asterisk. >>> Everything works fine now, and i understand. Great! Many thanks!! >> >> Fetching all branches created a new problem: can i tell git that it >> should rebase branches against master by default? Because now when i >> checked a non-master, non-staging local branch and called 'git pull >> -r' he said >> >> You asked me to pull without telling me which branch you >> want to rebase against, and 'branch.mook.merge' in >> your configuration file does not tell me, either. Please >> specify which branch you want to use on the command line and >> try again (e.g. 'git pull '). >> See git-pull(1) for details. > > I usually rebase manually and instead do just "git fetch". > >> Of course i can do what he suggests, but it means either >> - a lot of typing 'git pull -r origin refs/heads/master' (if i got it right) >> - editing config file every time i create a branch (not nice). > > You can just create the branch as > > git checkout -b new-branch origin > > and git will know where to pull from. And you can always do > > git branch --set-upstream new-branch origin > > after having created it. ok, thanks. Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB calling 'false'
On Wed, Jan 04, 2012 at 01:04:06PM +0100, m...@apollinemike.com wrote: > *** Stage: package (lilypond-doc, linux-x86) > invoking false > Command barfed: false This might be related to Carl's suggestion that GUB cannot correctly download netpbm / samba / rsync / something like that. I've never noticed that problem, but then again I've never stared at the detailed output from GUB, and I always have those installed on my main OS anyway. When I'm back in Glasgow (leaving in 3 hours, probably at university at about noon on Friday), I'll try a full GUB download+rebuild from scratch, and check the output. For now, if you haven't already done so, try installing the extra packages that Carl suggested. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
GUB and unfortunate travel timing
Hey guys, It seems like we've got solutions for 1933, 1943, and 1948. 2160 was fixed as a side note to the website pdf patch by Alberto. Dealing with git branches (issue 2100) is the only one that isn't either finished or really close to being finished, but I expect that patch just needs something like 1 hour of writing+research+reviews. Unfortunately, I'm leaving for Glasgow in 3 hours, so any official releases with the fixed 1933/1943/1948 will have to wait until Friday afternoon. If you're really anxious to test stuff, by all means build binaries with those fixes, upload them to a private server, and ask users to test them. Best-case scenario: we could have the third release candidate on Friday 6 Jan, with the official 2.16 release on Friday 13 Jan. That's an extremely ambitious schedule, so it's more realistic to think of 2.16 before the end of January -- but given the sudden interest [1] in having a stable release, I think that's certainly doable! [1] recall that I define "interest" as "writing or discussing patches", not "writing emails to say how much you want other people to do some kind of work". Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: problem with checking out staging branch
2012/1/3 Graham Percival : > On Tue, Jan 03, 2012 at 08:45:45PM +0100, Janek Warchoł wrote: >> I guess i should change it into this: >> >> [core] >> [branch "master"] > > It's not a bad thing that we can ask git wizards to give us custom > advice on our .git/config, but this shouldn't be necessary. I > mean, the only time I've ever edited .git/config was to give > myself push ability, following the CG. > > Once you've got your system working, Janek, could you (in a > separate directory) do a fresh git clone, following the > instructions in > http://lilypond.org/doc/v2.15/Documentation/contributor/setting-up > and nowhere else, then see what happens if you follow the > instructions in the current patch for 2100 ? Everything looks fine, i can diff and checkout staging branch. Looks like only the transition was painful. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
2012/1/4 James : > hello, > > On 3 Jan 2012, at 22:26, Janek Warchoł wrote: >> I might have given you a wrong impression, i don't think its really >> that bad. There is some teamwork, but no leader indeed. > > to use an English expression ... poppycock! > > Janek you may have not noticed that the team of Colin, > Phil and myself along with some of the bug squad managed, > with the the help of Graham (if you want to call him a 'leader') > to process a quite impressive number of patches. > > Before we managed to get some kind of automation of > patch testing I personally was fielding about 6 new patches > a day, producing reg test diffs, make checks and the like. > Colin was managing all patch countdown and push requests > while Phil ran around, figuratively speaking, making sure > things were in order in terms of regressions between dev releases. > all co ordinated by graham - pretty much. > > in the meantime Mike, Keith, Carl and co had plenty of time > then to fix some long standing bugs, and I am seeing some > serious work by David to do whatever it is he does with the parser etc. Indeed, i didn't appreciate enough your work. I apologize. Please do not hesitate to correct me when i say something wrong again. Nevertheless, while administration is done very efficiently as you've shown, i'm not aware of any mid- or long-term goals set for Lily except GLISS. Correct me if i'm wrong, but my impression is that there is no particular direction in which we are going. my apologies again, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
2012/1/4 David Kastrup :
>>> \settingsFrom is actually returning a Scheme expression for \with to
>>> use. It makes things rather simpler than more complex, even though it
>>> constitutes a Scheme expression.
>>
>> Um... i would really love to be able to type
>> \layout {
>> \compressFullBarRests
>> \override Score.SpacingSpanner #'common-shortest-duration =
>> #(ly:make-moment 6 10)
>> etc...
>> }
>
> Well, create a layout modification type, let \layout accept Scheme
> expressions of that type, write a Scheme function \layout-from in
> analogue to \settingsFrom, and it becomes
>
> \layout {
> \layout-from { \compressFullBarRests
> \override Score.SpacingSpanner #'common-shortest-duration =
> #(ly:make-moment 6 10)
> }
> etc...
> }
ok... However - i'm very sorry to say this :/ - it would be better if
i wouldn't have to type \layout-from at all. I know that it's not
much typing, and that \layout-from is an improvement, but from the
end-user perspective it's in fact PITA: when use \layout, when
\layout-from? :( Again, i'm very sorry beacause from the
programmer's perspective it's nothing, but for simple users
understanding what \layout does is hard enough; in fact it would be
nice to get rid of it but that's impossible.
You know, i pretend to be a really dumb user. And i want to enter
notes, not some \overridden << \layoutish ##Scheme## >> :( :( :(
LilyPond will have a chance of winning large audiences when all input
that is needed to create a full Messiah score will be sth like:
\version x.x.x
\header { ... }
\movement = "Sinfony" {
violin = { (notes) }
...
}
\movement = "Comfort ye" {
\makeScore
\makeParts
:/
>>> Scheme is not hard. Programming is hard.
>
> And sane program design is, apparently, even harder. People _don't_
> _ever_ think about improving things. Instead they hobble along in
> whatever clunky way they see others doing, complaining how clunky it is,
> and likely making it much clunkier by bending it to situations fitting
> even worse than what they have seen.
:(
Have you looked at my patches and if so, does any of them do this?
2012/1/4 David Kastrup :
> "layout-from" =
> #(define-void-function (parser location music)
> (ly:music?)
> (_i "To be used in output definitions. Take the layout instruction
> events from @var{music} and do the equivalent of context modifications
> duplicating their effect.")
> (define (musicop m mods)
> (if (music-is-of-type? m 'layout-instruction-event)
> (ly:add-context-mod
> mods
> (case (ly:music-property m 'name)
> ((PropertySet)
> (list 'assign
> (ly:music-property m 'symbol)
> (ly:music-property m 'value)))
> ((PropertyUnset)
> (list 'unset
> (ly:music-property m 'symbol)))
> ((OverrideProperty)
> (list 'push
> (ly:music-property m 'symbol)
> (ly:music-property m 'grob-property-path)
> (ly:music-property m 'grob-value)))
> ((RevertProperty)
> (list 'pop
> (ly:music-property m 'symbol)
> (ly:music-property m 'grob-property-path)
> (case (ly:music-property m 'name)
> ((SequentialMusic SimultaneousMusic)
> (for-each (lambda (x)
> (musicop x mods))
> (ly:music-property m 'elements)))
> ((ContextSpeccedMusic)
> (module-set! (current-module)
> (ly:music-property m 'context-type)
> #{ \context { $(module-ref (current-module)
> (ly:music-property m
> 'context-type))
> $(musicop (ly:music-property m
> 'element)
> (ly:make-context-mod))
> } #}
> mods)
> (musicop music (ly:make-context-mod)))
>
>
> It is a bit wonky, but should work for most purposes.
>
> At least it works with
>
> \layout-from \accidentalStyle "dodecaphonic"
>
> and with the above example.
Wow, thanks! I hope that i understand what it does and that i'll be
able to use it :)
cheers,
Janek
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
Adding Luke to recipients again... (please remember to include him as he's not signed to our mailing lists), 2012/1/4 David Kastrup : > Łukasz Czerwiński writes: >> Regarding all those fragments of Janek's and David's emails: For some time >> I have been observing how bug are being fixed in Lilypond and spent some >> time on conversations with Janek. >> For me there is almost no team work in Lilypond - only a bunch of geek >> trying to fix some issues, but without a leader who coordinates all >> actions. > > We have coordinated procedures in place that several people spend > sizable amounts of time on. This concerns the way new contributions are > channeled, and how bugs get registered and releases get made. Graham is > doing a lot of work keeping just that going and coordinated. Indeed and this means: kudos to Graham and the patch/issue team! >> As far as I remember, some time ago you have tried hard to make some >> big changes in Lilypond, but finally there was no big revolution... > > I am not sure who you are addressing. Nominally, you are replying to > Janek, and Janek did spacing changes he not just tried to get through, > but actually did. Thank you David for being so kind, but i don't remember any important spacing issues fixed by me. (however i'm in the process of gathering data for a truly revolutionary move; unfortunately estimated time left before the report will be ready is something like 3 months, because of other stuff i have to do). >> Without a leader that will make key design & implementation decisions >> Lilypond will improve in a slow pace, letting Finale and Sibellius >> gain more and more users. > > Forget Finale and Sibelius. They are not a problem we need to address > since they are competing in a different space. I don't fully agree, but i guess discusssing this is not that important. >> That means not only fixing critical bugs, but also: anticipating >> future stability problems, constantly improving end user documentation >> and the quality of source code (reduce complexity, comment code and so >> on). By now there is a huge work to be done and Lilypond needs someone >> who will form guidelines and priorities. > > There is no point in working on guidelines and priorities without > capacities that would be guided and prioritized by them. I'm amused by your answer, David. It's very rational and succint; i know Luke and if something can show him what the problem is it's your answer. Luke, i remember that you were doing something for GIMP. Can you say how things work there, what the leadership looks like and what could we learn from them, bearing in mind little time each of us have? cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: explain how to add git-cl to PATH (issue 5503093)
second draft http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/source-code.itexi#newcode921 Documentation/contributor/source-code.itexi:921: @example should all this be in a Note? http://codereview.appspot.com/5503093/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Segfault 2.15.23 Span_bar_stub_engraver
On Wed, Jan 4, 2012 at 1:41 AM, David Kastrup wrote: > Can you use git bisect for identifying the commit where things go wrong > for you? Git bisect results: 20670d51f8d97fd390210dd239b3b2427f071e7c is the first bad commit commit 20670d51f8d97fd390210dd239b3b2427f071e7c Author: Mike Solomon Date: Fri Sep 30 08:16:07 2011 +0200 It looks like this was reverted and a revised version was committed the next day: 4f49b000d6e257724e311b406e2346b8388c1f0e. I've verified that the commit right before this doesn't cause a segfault and this one does. The only other information I have that's relevant is that I've only seen this segfault happen on my 64-bit OS and not 32-bit. -Jay ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
Werner LEMBERG gnu.org> writes: > Look at the attached two files: > > The first file has 74 bars of a single voice, and `time' shows me the > following for processing it: > The other one is the same as the first file but has only 37 bars > It seems that we have some very bad exponential behaviour in > processing somewhere... > > line-width = 18000\cm > ragged-right = ##t > ragged-last-bottom = ##f Well, you are creating an unusual line-breaking optimization problem. I think LilyPond uses a "total-fit" line-breaker, as made famous by TeX. The number of possible breaking patterns does go up exponentially with measure count (or word count for the TeX case). Good algorithms limit the number of breaking patterns that get evaluated, so that processing time increases slower-than-exponentially for large measure count. Here you have a case where you force the measures to fill more lines than they would need, and "ragged-right" makes all line-breaks feasible. You may have deprived the algorithm of its means to limit the number of line-breaking patterns it needs consider. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
>> line-width = 18000\cm >> ragged-right = ##t >> ragged-last-bottom = ##f > > Well, you are creating an unusual line-breaking optimization > problem. I'm very talented in finding unusual problems for almost every piece of software I'm using :-) > Here you have a case where you force the measures to fill more lines > than they would need, and "ragged-right" makes all line-breaks > feasible. You may have deprived the algorithm of its means to limit > the number of line-breaking patterns it needs consider. Lilypond definitely needs to protect against this. I suggest to either add an iteration counter somewhere or to estimate the number of iterations (per line? per page? whatever) in advance in case this is possible. Then LilyPond could provide one or more configuration values to limit the number of iterations. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
From: Werner LEMBERG Subject: Re: lilypond hangs Date: Thu, 05 Jan 2012 06:25:23 +0100 (CET) > >>> line-width = 18000\cm >>> ragged-right = ##t >>> ragged-last-bottom = ##f >> >> Well, you are creating an unusual line-breaking optimization >> problem. Note that lilypond behaves badly also if you say ragged-bottom = ##t ragged-last-bottom = ##t And this I now consider as a real bug: lilypond *must* recognize that it can typeset everything in a single, long line. Given this message http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00535.html it seems that previous versions of lilypond don't have this problem. Am I missing something? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: explain how to add git-cl to PATH (issue 5503093)
http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/source-code.itexi File Documentation/contributor/source-code.itexi (right): http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/source-code.itexi#newcode921 Documentation/contributor/source-code.itexi:921: @example On 2012/01/05 01:08:01, janek wrote: should all this be in a Note? I think you could make this much simpler. See the section http://lilypond.org/doc/v2.15/Documentation/contributor-big-page#problems Compiling on Mac OS X Follow that style. Were this me making this edit, I'd lift this section and just reword the bits for LilyDev. There is some assumption that if you've managed to install and get this far with LilyDev that you can handle cut-down instructions. Otherwise generally: use @example for just the stuff you'd type in the terminal, not any additional instructions. This makes it much clearer especially on the web pages. http://codereview.appspot.com/5503093/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Documentation search - update version and Google syntax
Pavel, On 4 January 2012 22:32, Pavel Roskin wrote: > Hello! > > There are two issues with the search box in the online documentation. > One is that search in v2.15 documentation adds +v2.14 to the > Google search, so it look in the older documentation. > > The other is that "+" doesn't have the old meaning since the > introduction of Google Plus. To ensure that "v2.15" appears on the > page or in the URL, it should be added in quotes. > > A simpler alternative would be to use this in the search: > > site:lilypond.org/doc/v2.15 > > That would tell Google to search documents only under > lilypond.org/doc/v2.15, which is probably our intention. > > Here's the patch. Please let me know if a sign off or something like > that is needed. It's my first ever patch for LilyPond. Thank you. There is a review process that does need to be followed. If you intend on doing more work for LilyPond then can you read: http://lilypond.org/doc/v2.15/Documentation/contributor-big-page#summary-for-experienced-developers In this case start at the 'reviews' bullet point about half way down. (I don't know your level of expertise so am assuming you are comfortable with these instructions) Essentially we have a tracker issue on Google code for logging the issues and we use Rietveld (all explained in the above link) for code review. However if you do not intend to do more LilyPond dev work then I am happy to handle this patch for you, but I'd prefer a git formatted patch if possible or at the very least a 'diff' file that I can then post for review on your behalf. This email seems to have just put the diffs inline (at least on my email reader). -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Segfault 2.15.23 Span_bar_stub_engraver
Jay Anderson writes: > On Wed, Jan 4, 2012 at 1:41 AM, David Kastrup wrote: >> Can you use git bisect for identifying the commit where things go wrong >> for you? > > Git bisect results: > 20670d51f8d97fd390210dd239b3b2427f071e7c is the first bad commit > commit 20670d51f8d97fd390210dd239b3b2427f071e7c > Author: Mike Solomon > Date: Fri Sep 30 08:16:07 2011 +0200 > > It looks like this was reverted and a revised version was committed > the next day: 4f49b000d6e257724e311b406e2346b8388c1f0e. I've verified > that the commit right before this doesn't cause a segfault and this > one does. The only other information I have that's relevant is that > I've only seen this segfault happen on my 64-bit OS and not 32-bit. Grob::get_vertical_axis_group is not protected against the case where g has an axis group interface but no Y_AXIs parent. The second if in Grob::vertical_less has a test that can obviously not be true. Either don't look like 64bit problems. Perhaps something needs a live-check? -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Documentation search - update version and Google syntax
James writes: > However if you do not intend to do more LilyPond dev work then I am > happy to handle this patch for you, but I'd prefer a git formatted > patch if possible or at the very least a 'diff' file that I can then > post for review on your behalf. > > This email seems to have just put the diffs inline (at least on my > email reader). It was a git diff included as a separate MIME part inline. It will likely depend on your mail reader whether it offers to save the part separately, in which case it should not meddle with its spacing and formatting. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Documentation search - update version and Google syntax
David On 5 January 2012 06:58, David Kastrup wrote: > James writes: > >> However if you do not intend to do more LilyPond dev work then I am >> happy to handle this patch for you, but I'd prefer a git formatted >> patch if possible or at the very least a 'diff' file that I can then >> post for review on your behalf. >> >> This email seems to have just put the diffs inline (at least on my >> email reader). > > It was a git diff included as a separate MIME part inline. It will > likely depend on your mail reader whether it offers to save the part > separately, in which case it should not meddle with its spacing and > formatting. > Thanks, I figured it was something like that, but the gmail web client doesn't seem to let me save this off separately (i've not worked out how so far) so I was reluctant to cut/paste. Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
Janek Warchoł writes:
> 2012/1/4 David Kastrup :
\settingsFrom is actually returning a Scheme expression for \with to
use. It makes things rather simpler than more complex, even though it
constitutes a Scheme expression.
>>>
>>> Um... i would really love to be able to type
>>> \layout {
>>> \compressFullBarRests
>>> \override Score.SpacingSpanner #'common-shortest-duration =
>>> #(ly:make-moment 6 10)
>>> etc...
>>> }
>>
>> Well, create a layout modification type, let \layout accept Scheme
>> expressions of that type, write a Scheme function \layout-from in
>> analogue to \settingsFrom, and it becomes
>>
>> \layout {
>> \layout-from { \compressFullBarRests
>> \override Score.SpacingSpanner #'common-shortest-duration =
>> #(ly:make-moment 6 10)
>> }
>> etc...
>> }
>
> ok... However - i'm very sorry to say this :/ - it would be better if
> i wouldn't have to type \layout-from at all.
\layout is not the place to accept arbitrary music.
> I know that it's not much typing, and that \layout-from is an
> improvement, but from the end-user perspective it's in fact PITA: when
> use \layout, when \layout-from?
\layout-from takes music and extracts context definitions.
> :( Again, i'm very sorry beacause from the programmer's perspective
> it's nothing, but for simple users understanding what \layout does is
> hard enough;
\layout definitions don't have a syntax compatible with music. For
example, \layout-from is a command you could not even write in music.
If \layout accepted music and mostly ignored it, simple users would not
understand what it does, and advanced users would not either.
> And i want to enter notes, not some \overridden << \layoutish
> ##Scheme## >> :( :( :(
Nobody keeps you from entering \compressFullBarRests and stuff right in
your music. That's their default place of writing them.
As a programmer, I prefer putting the declarations where they make sense
and apply document-wide. Nobody forces you to do it in that manner if
you prefer jamming everything explicitly into the music which, after
all, is the designed user interface for it.
[\layout-from]
>> It is a bit wonky, but should work for most purposes.
>>
>> At least it works with
>>
>> \layout-from \accidentalStyle "dodecaphonic"
>>
>> and with the above example.
>
> Wow, thanks! I hope that i understand what it does and that i'll be
> able to use it :)
It is wonky mostly because we don't have a Scheme interface to context
definitions (so I have to use #{ ... #} and fudge around with module-ref
and module-set! inside). I am actually surprised it works.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
Keith OHara writes: > Werner LEMBERG gnu.org> writes: > >> Look at the attached two files: >> >> The first file has 74 bars of a single voice, and `time' shows me the >> following for processing it: > >> The other one is the same as the first file but has only 37 bars > >> It seems that we have some very bad exponential behaviour in >> processing somewhere... >> > >> line-width = 18000\cm >> ragged-right = ##t >> ragged-last-bottom = ##f > > Well, you are creating an unusual line-breaking optimization problem. > > I think LilyPond uses a "total-fit" line-breaker, as made famous by > TeX. TeX uses linear programming optimization and not "total-fit". -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: critical issues
On Jan 5, 2012, at 1:20 AM, Janek Warchoł wrote: > Correct me if i'm wrong, but my impression is that > there is no particular direction in which we are going. > I think that it is very difficult to set these goals because different things interest different people. I know that Bertrand and I are chipping away at a long standing markup-improvement goal, and I'd like to get smoother 2D-object-on-the-plane-distance handling, and there's my dream of implementing some sort of mixed-integer-quadratic-programming engine in LilyPond (I did some tests with quantizing quadratic functions using linear functions, but it generates at least 1056 variables for a 500-measure score with 33 columns per measure and normal line widths quantized at horizontal intervals of 0.01...). I'm sure that other people have their pet projects as well. The ensemble of these projects is the "direction" of LilyPond, and I don't see why it would need more of a direction that that. In fact, I think that it is because of some sorta unified direction that for-profit programs can often miss out on adding experimental or innovative features. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond hangs
On Wed, 04 Jan 2012 21:42:59 -0800, Werner LEMBERG wrote:
From: Werner LEMBERG
Subject: Re: lilypond hangs
Date: Thu, 05 Jan 2012 06:25:23 +0100 (CET)
Note that lilypond behaves badly also if you say
ragged-bottom = ##t
ragged-last-bottom = ##t
Oh. That would be a less-unusual situation.
If you remove the override, this takes much more time for 400 notes than for
200.
\paper { paper-width= 1\mm }
{ \override Score.NonMusicalPaperColumn #'line-break-permission = ##f
\repeat unfold 400 { b'4 } }
Given this message []
it seems that previous versions of lilypond don't have this problem.
Jay compiles his own LilyPond, so he probably used a recent version for that.
I use 2.14.
This are of code hasn't changed (much) for a few years at least.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
