Re: Issue 4211: Add an alternative quarter rest shaped like amirrored Z. (issue 177640043 by nine.fierce.ball...@gmail.com)

2014-12-03 Thread Phil Holmes
- Original Message - 
From: lemzw...@googlemail.com

To: nine.fierce.ball...@gmail.com
Cc: re...@codereview-hr.appspotmail.com; lilypond-devel@gnu.org
Sent: Tuesday, December 02, 2014 6:59 PM
Subject: Re: Issue 4211: Add an alternative quarter rest shaped like 
amirrored Z. (issue 177640043 by nine.fierce.ball...@gmail.com)





https://codereview.appspot.com/177640043/diff/20001/mf/feta-rests.mf
File mf/feta-rests.mf (right):

https://codereview.appspot.com/177640043/diff/20001/mf/feta-rests.mf#newcode438
mf/feta-rests.mf:438: rest := rest xscaled -1 shifted (w, 0);
Please use tabs for indentation


Explained here:

http://lilypond.org/doc/v2.19/Documentation/contributor/metafont-formatting-rules

--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


space-alist problem

2014-12-03 Thread Werner LEMBERG

What defines the distance between a time signature and the next note
*with an accidental* (in addition to the TimeSignatures
`extra-spacing-width')?  I would expect that the `first-note' (or
`next-note', if set) element of a TimeSignature's `space-alist'
handles this case also, but this assumption is apparently wrong, as
the example below shows...

In case this is a bug, it would be a quite serious one...


Werner

===

\relative c' {
  \time 4/4 c4 c c c |
  \time 3/4 c4 c c }
\relative c' {
  \override Staff.TimeSignature.space-alist.first-note =
#'(extra-space . 0.1)
  \time 4/4 c4 c c c |
  \time 3/4 c4 c c }
}

\relative c' {
  \time 4/4 cis4 cis cis cis |
  \time 3/4 cis4 cis cis }
\relative c' {
  \override Staff.TimeSignature.space-alist.first-note =
#'(extra-space . 0.1)
  \time 4/4 cis4 cis cis cis |
  \time 3/4 cis4 cis cis }
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: GUB and mpfr/mpc

2014-12-03 Thread Masamichi HOSODA
 I changed mingw.org's mingw-runtime to mingw-64 (32-bit).
 Then an error didn't occur and correct test.pdf was generated.
 
 https://github.com/trueroad/gub/tree/binutils-2.24
 
 I may pull request if you request it.
 
 Further, even if the runtime is mingw-w64,
 bad_alloc occurred when optimization was turned on.

 For both of bad_alloc prevented and optimization,
 I tried the following setting.
 Only one file (lily/skyline.cc) optimization is disabled
 and all other files optimization is enabled.
 
 Do you have a backtrace that might give us some more clue about where
 lily/skyline.cc has a problem?
 
 I thought that I had at one time proposed something to be changed (as
 part of some issue?) order to deal with possible memory corruption, but
 a quick look through the log messages does not turn up either a commit
 from me or a commit message ringing a bell.

 I turned off optimization to get correct backtrace,
 but bad_alloc didn't occur.
 Therefore I could get only incomplete backtrace.

 It seems that push_back in Skyline::internal_merge_skyline throws bad_alloc.
 I think the problem is Skyline::internal_merge_skyline
 and/or first_intersection.

 Skyline::internal_merge_skyline has a while loop with push_back.
 I think that the loop termination condition may break by optimization.
 
 I need more elements from the backtrace.  The problem most likely is
 that the Skyline is destructed before work with it is finished, and that
 means that somewhere in the call chain the Skyline is not maintained in
 a manner where the Lisp Garbage collector will consider it as still in
 use.
 
 So internal_merge_skyline is likely only the place where things blow up,
 but the actual cause will be further up in the call chain.

Here is first backtrace.
I stopped lilypond.exe by Ctrl-C
when the memory that lilypond.exe uses was increased rapidly.
I think that it was in the infinite loop.

```
C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bingdb lilypond.exe
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i686-w64-mingw32.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from lilypond.exe...done.
(gdb) r test.ly
Starting program: C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bin\lilypond.exe 
test.ly
[New Thread 7936.0x2234]
GNU LilyPond 2.19.16
Processing `test.ly'
Parsing...
test.ly:1: warning: no \version statement found, please add

\version 2.19.16

for future compatibility
Interpreting music...
Preprocessing graphical objects...[New Thread 7936.0x256c]

Program received signal SIGINT, Interrupt.
[Switching to Thread 7936.0x256c]
0x76cedbf6 in KERNELBASE!CtrlRoutine ()
   from C:\WINDOWS\SYSTEM32\KernelBase.dll
(gdb) bt
#0  0x76cedbf6 in KERNELBASE!CtrlRoutine ()
   from C:\WINDOWS\SYSTEM32\KernelBase.dll
#1  0x97b0d836 in ?? ()
#2  0x in ?? ()
(gdb) info thread
  Id   Target Id Frame
* 2Thread 7936.0x256c 0x76cedbf6 in KERNELBASE!CtrlRoutine ()
   from C:\WINDOWS\SYSTEM32\KernelBase.dll
  1Thread 7936.0x2234 0x77138fc0 in ntdll!RtlCompareMemoryUlong ()
   from C:\WINDOWS\SYSTEM32\ntdll.dll
(gdb) thread 1
[Switching to thread 1 (Thread 7936.0x2234)]
#0  0x77138fc0 in ntdll!RtlCompareMemoryUlong ()
   from C:\WINDOWS\SYSTEM32\ntdll.dll
(gdb) bt
#0  0x77138fc0 in ntdll!RtlCompareMemoryUlong ()
   from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x7718f95a in ntdll!RtlFindCharInUnicodeString ()
   from C:\WINDOWS\SYSTEM32\ntdll.dll
#2  0x7714dfb4 in ntdll!RtlAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#3  0x771eee08 in ntdll!RtlpNtSetValueKey ()
   from C:\WINDOWS\SYSTEM32\ntdll.dll
#4  0x7718f75a in ntdll!RtlFindCharInUnicodeString ()
   from C:\WINDOWS\SYSTEM32\ntdll.dll
#5  0x7714dfb4 in ntdll!RtlAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#6  0x76889ad1 in msvcrt!malloc () from C:\WINDOWS\SYSTEM32\msvcrt.dll
#7  0x6fcbddef in operator new (sz=40)
at 
/home/gub/gub/target/mingw/src/cross/gcc-4.8.2/libstdc++-v3/libsupc++/new_op.cc:51
#8  0x0060da2d in Skyline::internal_merge_skyline(std::listBuilding, 
std::allocatorBuilding *, std::listBuilding, std::allocatorBuilding *, 
std::listBuilding, std::allocatorBuilding *) const ()
#9  0x00611495 in Skyline::padded(double) const ()
#10 0x005fb306 in Separation_item::calc_skylines(scm_unused_struct*) ()
#11 0x6bf921c0 in scm_dapply ()
   from C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bin\libguile-17.dll
#12 0x in ?? ()
(gdb) quit
A debugging session is 

Re: scheme problem: colored background, layers

2014-12-03 Thread Urs Liska


Am 03.12.2014 22:31, schrieb Big Noise:

Hi everybody,

now I could finish two scores that have been waiting for that colored 
background trick. Maybe they are somewhat extreme examples...

If anyone is interested:
http://jkg-musik.jimdo.com/lilypond


This is absolutely great!
I think this would be a good item for http://lilypond.org/examples.html.

Otherwise it'd be cool if you could write something on Scores of Beauty 
about it.





For the colored arrows from the second example, I've created a snippet 
as well:

http://lsr.di.unimi.it/LSR/Item?u=1id=961


Am I seeing correctly that the arrows are coded with absolute 
coordinates from their starting points (i.e. they wouldn't adapt to 
layout changes)?
This is not at all diminishing your snippet, but it would be absolutely 
awesome if someone could extend this to override the stencil of, say, a 
slur, so the arrows would snap to two notes.


Best
Urs



Cheers,
Klaus

___
lilypond-user mailing list
lilypond-u...@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Fwd: Rest-dot spacing

2014-12-03 Thread Dan Eble
I think the PNG attachment was dropped from this mail to the bug list.  
Hopefully it comes through here.
— 
Dan

 Begin forwarded message:
 
 From: Dan Eble d...@faithful.be
 Subject: Rest-dot spacing
 Date: November 30, 2014 at 21:01:47 EST
 To: bug-lilypond bug bug-lilyp...@gnu.org
 
 Is it expected that these two ways of changing the appearance of a rest yield 
 different spacing between the rest and the dot?
 
 \version 2.19.15
 
 classicalQuarter = #(lambda (grob)
   (if (= (ly:grob-property grob 'duration-log 999) 2)
   (ly:grob-set-property! grob 'style 'classical))
   (ly:rest::print grob))
 
 
   \new Staff {
 \override Rest #'style = #'classical r4.
   }
 
 
 
   \new Staff {
 \override Rest #'stencil = \classicalQuarter r4.
   }
 
 

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: GUB and mpfr/mpc

2014-12-03 Thread Dan Eble
On Dec 3, 2014, at 07:37 , Masamichi HOSODA truer...@sea.plala.or.jp wrote:
 
 I changed mingw.org's mingw-runtime to mingw-64 (32-bit).
 Then an error didn't occur and correct test.pdf was generated.
 
 https://github.com/trueroad/gub/tree/binutils-2.24
 
 I may pull request if you request it.
 
 Further, even if the runtime is mingw-w64,
 bad_alloc occurred when optimization was turned on.

There is this at the end of skyline.cc:

  // Should add during ver2.19 (to avoid an endless loop
  // when  merging identical skylines with a vertical segment)
  // if (end = s2-front().end_) s2-pop_front();

Also, the mention of optimization reminds me of one of the horrors of floating 
point types: a value in a register can quietly be changed when it is written to 
memory.  Take a look at some of the “myths” in section 1 of 
https://hal.archives-ouvertes.fr/hal-00128124/en/ .

Do the skylines need to deal with the wide range of values that “double 
allows?  If not, replacing the Real class with a fixed-point math class would 
make the code a lot less scaring.
— 
Dan


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: GUB and mpfr/mpc

2014-12-03 Thread Dan Eble
On Dec 4, 2014, at 00:12 , Dan Eble d...@faithful.be wrote:
 
 There is this at the end of skyline.cc:
 
  // Should add during ver2.19 (to avoid an endless loop
  // when  merging identical skylines with a vertical segment)
  // if (end = s2-front().end_) s2-pop_front();

I meant at the end of internal_merge_skyline() in skyline.cc. (Fatigue strikes 
again.)

 make the code a lot less scaring.

scary (derp)
— 
Dan


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel