Re: Issue 2364 in lilypond: Patch: Don't use Bottom overrides (default when unspecified) in \tabFullNotation
Comment #7 on issue 2364 by d...@gnu.org: Patch: Don't use Bottom overrides (default when unspecified) in \tabFullNotation http://code.google.com/p/lilypond/issues/detail?id=2364 I think that is sufficient for verification. The point was that \tabFullNotation establishes global settings useful for typesetting a particular kind of tablature. Because of the now changed lines, you had to call it in a tablature-related context (TabStaff or so?). I think that was even documented, but pointless. Now I have committed a feature that turns commands like \tabFullNotation into context modifications in an output definition. While the implementation is smart enough to guess a useful "Bottom" context when other context specs precede the overrides/sets in question, relying on such smartness when nothing is gained by it seems unnecessary. I guess a test would compare the effects of \tabFullNotation on tab contexts when given in a non-tab context, before and after the patch. I don't think that it is worth investing all too much time in this: it does not fix a problem that seems to have bothered anyone so far. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open strings in tablature
Comment #15 on issue 2348 by m...@hohlart.de: Patch: Handling of open strings in tablature http://code.google.com/p/lilypond/issues/detail?id=2348 I stumbled upon comment #12 - how does this patch interfere with Mike's work? Are there any reasons not to include this patch in one of the next countdowns? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open strings in tablature
Updates: Status: Started Owner: d...@gnu.org Labels: -Patch-needs_work Patch-new Comment #16 on issue 2348 by d...@gnu.org: Patch: Handling of open strings in tablature http://code.google.com/p/lilypond/issues/detail?id=2348 I think that Colin may be confusing this with the transparent/stencil patches that have already been committed IIRC. There may or may not be merge conflicts. I am setting this issue to Patch-new. Once it passes the normal patch testing, I think I can justify pushing it for you (it is most convenient if you sent me a git-format-patch: make sure that the commit message is consistent with the whole content after the bazillion of changes the name choices went through). Would it be possible for somebody to register you as a member of the LilyPond project? It seems awkward to have to mark this issue as "owned" by me since I can't put ownership to you. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Updates: Status: Verified Comment #15 on issue 2346 by elu...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
call for help to verify issues 2360 and 2338
lacking the necessary installations I am not able to verify these two issues - can somebody spring in!? thanks Eluze -- View this message in context: http://old.nabble.com/call-for-help-to-verify-issues-2360-and-2338-tp33449643p33449643.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Status: Verified Comment #44 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Various Mac OS X users, credited below, have verified this issue on 2.15.32. The only Mac OS X configuration not covered is 10.4.11 on x86 So I'm marking this as verified. A big thanks from the bug squad to all the users who gave their time to help with this effort. MacOS X x86/ppc User Issue 2338 version on 2.15.32 -+-++ 10.4.11 ppc Ole Schmidt verified James Worltonverified -+-++ 10.4.11 x86 not verified -+-++ 10.5.8 ppc Stan Sanderson verified -+-++ 10.5.8 x86 Stan Sanderson verified -+-++ 10.6.8 x86 Ole Schmidt verified -+-++ 10.7.3 x86 Eric Schisselverified Hans Aikema verified -+-++ 10.7.x x86 Phillipe verified ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Comment #11 on issue 2360 by d...@gnu.org: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 Advice for verification: the reported problem was that the scheme-sandbox produces a failure while attempting to load the readline library. The nature of the "fix" is to not even try, so by default command line editing will not be available. Instead, the user initialization file for general guile sessions is loaded, and the documentation states how you can activate readline in there. The underlying problem, namely that the readline library has to be available before it can get loaded, persists, it just has been made "somebody else's problem". Using the user initialization file is actually the best method to ensure a consistent user experience and place overall preferences like readline. For our full-size packagings, it might be worth considering to package readline and its guile bindings. That would likely fall in the responsibility of the GUB setup, however. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Comment #12 on issue 2360 by d...@gnu.org: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 Pt, I forgot the advice: the important thing on the problematic platforms is that the Scheme sandbox should run without error now: it tries loading the user initialization file, something which was not done before. If the user did nothing whatsoever to create such a file, the desired result is nothing: no error, no behavior difference as compared to not trying to load that file. The scheme-sandbox should work, but command line editing won't without the user enabling it (and the respective libraries being installed). ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open strings in tablature
Updates: Labels: Patch-needs_work Comment #17 on issue 2348 by d...@gnu.org: Patch: Handling of open strings in tablature http://code.google.com/p/lilypond/issues/detail?id=2348#c17 Patchy the autobot says: Patchy actually does not complain, but the diffs show an inconsistent mixture of exclude (in engraver-init.ly) and restrain ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open strings in tablature
Comment #18 on issue 2348 by m...@hohlart.de: Patch: Handling of open strings in tablature http://code.google.com/p/lilypond/issues/detail?id=2348#c18 Handling of open strings in tablature This patch creates a switch called ignoreOpenStrings. When set to #f (default), LilyPond handles open strings as usual. Setting ignoreOpenStrings to #t excludes open strings and forces the fret calculation routine to find a fretted position even for pitches equal to an open string. http://codereview.appspot.com/5695058 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open strings in tablature
Comment #19 on issue 2348 by m...@hohlart.de: Patch: Handling of open strings in tablature http://code.google.com/p/lilypond/issues/detail?id=2348 Am 06.03.2012 11:20, schrieb lilyp...@googlecode.com: Corrected. Sorry for the nuisance. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \grace after \cadenzaOff suppresses auto-beams
Le 06/03/2012 01:04, Colin Hall disait :
[...]
Have you isolated a bug here?
I'm not sure about it but, thanks to the Scheme tutorial I just finished
to translate I'm now not so blind:
\displayMusic {
c1
\cadenzaOn d1 e \cadenzaOff
f1 }
and it looks like the D and E don't belong to the list of elements
attached to the right SequentialMusic.
As I understand it, here are the steps:
1 open a sequence MAIN
1.1 play a C
1.2 open a sequence (the cadenza)
1.2.1 define its properties
1.2.1.1 no timing
1.2.1.2 no beaming
1.3 play a D
1.4 play a E
1.5 open a sequence
1.5.1 define its properties
1.5.1.1 activate timing
1.5.1.2 synchronize the clock
1.5.1.3 activate beaming
1.6 play a F and close MAIN
I believe that, at least, steps 1.3 to 1.5 should be sub-parts of 1.2,
thus not sure about step 1.5.1.2
Please correct me if I'm wrong.
Cheers,
Jean-Charles
(make-music
'SequentialMusic
'elements
(list (make-music
'NoteEvent
'duration
(ly:make-duration 0 0 1 1)
'pitch
(ly:make-pitch -1 0 0))
(make-music
'SequentialMusic
'elements
(list (make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
#f
'symbol
'timing))
(make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
#f
'symbol
'autoBeaming
(make-music
'NoteEvent
'duration
(ly:make-duration 0 0 1 1)
'pitch
(ly:make-pitch -1 1 0))
(make-music
'NoteEvent
'duration
(ly:make-duration 0 0 1 1)
'pitch
(ly:make-pitch -1 2 0))
(make-music
'SequentialMusic
'elements
(list (make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
#t
'symbol
'timing))
(make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
(ly:make-moment 0 1 0 1)
'symbol
'measurePosition))
(make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
#t
'symbol
'autoBeaming
(make-music
'NoteEvent
'duration
(ly:make-duration 0 0 1 1)
'pitch
(ly:make-pitch -1 3 0
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \grace after \cadenzaOff suppresses auto-beams
Jean-Charles Malahieude writes:
> Le 06/03/2012 01:04, Colin Hall disait :
>>
>> [...]
>>
>> Have you isolated a bug here?
>>
>
> I'm not sure about it but, thanks to the Scheme tutorial I just
> finished to translate I'm now not so blind:
>
> \displayMusic {
>c1
>\cadenzaOn d1 e \cadenzaOff
>f1 }
>
> and it looks like the D and E don't belong to the list of elements
> attached to the right SequentialMusic.
>
> As I understand it, here are the steps:
> 1 open a sequence MAIN
> 1.1 play a C
> 1.2 open a sequence (the cadenza)
> 1.2.1 define its properties
> 1.2.1.1 no timing
> 1.2.1.2 no beaming
> 1.3 play a D
> 1.4 play a E
> 1.5 open a sequence
> 1.5.1 define its properties
> 1.5.1.1 activate timing
> 1.5.1.2 synchronize the clock
> 1.5.1.3 activate beaming
> 1.6 play a F and close MAIN
>
> I believe that, at least, steps 1.3 to 1.5 should be sub-parts of 1.2,
> thus not sure about step 1.5.1.2
>
> Please correct me if I'm wrong.
1.2 and 1.5 are just a convenient way of grouping several property
setting events into one music identifier like \cadenzaOn. You could
define
cadenzaOn = { \set ... \set ... }
also as
cadenzaOn = << \set ... \set ... >>
The difference is that in the second form, the time of the events runs
in parallel rather than in sequence, but since all events are
instantaneous, that does not cause different results.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Comment #13 on issue 2360 by pkx1...@gmail.com: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 I don't know if this is good enough to verify but in LilyDev (Ubuntu 10.04) I get james@DellVM:~$ lilypond scheme-sandbox GNU LilyPond 2.15.33 Processing `/home/james/lilypond-git/build/out/share/lilypond/current/ly/scheme-sandbox.ly' Parsing... guile> --snip-- Do I need to do anything more? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Comment #14 on issue 2360 by d...@gnu.org: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 That verifies this platform. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Comment #15 on issue 2360 by pkx1...@gmail.com: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 This is for Windows 7. I don't have XP --snip-- C:\Users>lilypond scheme-sandbox GNU LilyPond 2.15.32 Processing `C:/Program Files/LilyPond/usr/share/lilypond/current/ly/scheme-sandbox.ly' Parsing... guile> --snip-- ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2374 in lilypond: Placement of dot depending on \stemDown or \voiceTwo
Comment #5 on issue 2374 by janek.li...@gmail.com: Placement of dot depending on \stemDown or \voiceTwo http://code.google.com/p/lilypond/issues/detail?id=2374 Eluze: good idea, \voice... commands should be mentioned and a warning about \..Up/Down given. I think we shall mark this issue as invalid and open new Doc issue. David: i think it was about positioning of dots in one column across the staff, and Werner was involved. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates
Comment #16 on issue 2346 by janek.li...@gmail.com: Use convert-ly from latest development release for LSR updates http://code.google.com/p/lilypond/issues/detail?id=2346 Thanks, David, James, Colin and Eluze! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Updates: Status: Verified Comment #16 on issue 2360 by janek.li...@gmail.com: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 Here's what i got on XP. I guess this means issue is verified. C:\Documents and Settings\Janek>lilypond scheme-sandbox GNU LilyPond 2.15.32 Processing `C:/Program Files/LilyPond/usr/share/lilypond/current/ly/scheme-sandb ox.ly' Parsing... guile> ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: call for help to verify issues 2360 and 2338
On Tue, Mar 6, 2012 at 10:25 AM, -Eluze wrote: > > lacking the necessary installations I am not able to verify these two issues > - can somebody spring in!? Verified 2360 on WinXP. I think all is verified now. thanks, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: release candidate blocked due to issues to verify
On Fri, Mar 2, 2012 at 1:00 PM, Graham Percival wrote: > We now have zero Critical issues, so I'd like to have another > release canddiate. Unfortunately, there is still at least one > "issue to verify" in the list for 2.15.31, so I will not make a > release. > > http://code.google.com/p/lilypond/issues/list?can=7 No issues to verify in 2.15.32 list, too, so i hope we'll release new Candidate when 2356 is counted down. cheers, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2360 in lilypond: Scheme sandbox fails to load readline module
Comment #17 on issue 2360 by d...@gnu.org: Scheme sandbox fails to load readline module http://code.google.com/p/lilypond/issues/detail?id=2360 Looks good until further notice. I suppose that at one point of time the questions will pour in what it takes to actually enable readline support on platforms other than GNU/Linux. I have no clue about that. But then someone (TM) can find this out in relative peace. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2378 in lilypond: Patch: Various updates to reduce make doc output
Comment #4 on issue 2378 by philehol...@gmail.com: Patch: Various updates to reduce make doc output http://code.google.com/p/lilypond/issues/detail?id=2378 I'm happy to address those comments, but it'll be the weekend at the earliest. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2373 in lilypond: Windows Start Menu short cut to 'Examples' is invalid
Updates: Status: Fixed Labels: Fixed_2_15_32 Comment #4 on issue 2373 by philehol...@gmail.com: Windows Start Menu short cut to 'Examples' is invalid http://code.google.com/p/lilypond/issues/detail?id=2373 Marking this as fixed. Windows build 2.15.32 downloaded and installed, with no Lily shortcuts in the All Programs list prior to the install. All shortcuts now work. Needs a windows user to verify, with the same method. Optional uninstall first, then install 2.15.32 and verify all shortcuts work. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open strings intablature
wrote in message news:16-9567054385019064696-1793755249030035-lilypond=googlecode@googlecode.com... Would it be possible for somebody to register you as a member of the LilyPond project? It seems awkward to have to mark this issue as "owned" by me since I can't put ownership to you. I can do that if Marc emails me a Google mail. This can get over-whelmed by Lilypond bug mails, so bug squadders have found it convenient to create a new GMail address for the purpose. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open strings intablature
"Phil Holmes" writes: > wrote in message > news:16-9567054385019064696-1793755249030035-lilypond=googlecode@googlecode.com... >> >> Would it be possible for somebody to register you as a member of the >> LilyPond project? It seems awkward to have to mark this issue as >> "owned" by me since I can't put ownership to you. > > I can do that if Marc emails me a Google mail. This can get > over-whelmed by Lilypond bug mails, so bug squadders have found it > convenient to create a new GMail address for the purpose. I don't have a Google mail address either. That is not a requirement. You just need to register a developer account at Google, and since Marc already posts _comments_ on issues, he should have such an account. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2348 in lilypond: Patch: Handling of open stringsintablature
"David Kastrup" wrote in message news:87zkbtvkio@fencepost.gnu.org... "Phil Holmes" writes: wrote in message news:16-9567054385019064696-1793755249030035-lilypond=googlecode@googlecode.com... Would it be possible for somebody to register you as a member of the LilyPond project? It seems awkward to have to mark this issue as "owned" by me since I can't put ownership to you. I can do that if Marc emails me a Google mail. This can get over-whelmed by Lilypond bug mails, so bug squadders have found it convenient to create a new GMail address for the purpose. I don't have a Google mail address either. That is not a requirement. You just need to register a developer account at Google, and since Marc already posts _comments_ on issues, he should have such an account. -- David Kastrup OK. Still need that confirmation from Marc, and that he'd be happy to be added to the list of issue committers. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2373 in lilypond: Windows Start Menu short cut to 'Examples' is invalid
Updates: Status: Verified Comment #5 on issue 2373 by pkx1...@gmail.com: Windows Start Menu short cut to 'Examples' is invalid http://code.google.com/p/lilypond/issues/detail?id=2373 yep this is gone (windows 7). Attachments: Capture2_15_32.png 7.3 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2381 by janek.li...@gmail.com: Patch: Web: add GSoC ideas list http://code.google.com/p/lilypond/issues/detail?id=2381 Web: add GSoC ideas list A list of suggested projects for Google Summer of Code students is necessary to participate in the program. http://codereview.appspot.com/5753059 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Updates: Status: Started Labels: -Patch-new Patch-review Comment #1 on issue 2381 by janek.li...@gmail.com: Patch: Web: add GSoC ideas list http://code.google.com/p/lilypond/issues/detail?id=2381 This is urgent and i've checked that it makes and makes website, so i think i can set it to review. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Updates: Labels: -Patch-review Patch-new Comment #2 on issue 2381 by philehol...@gmail.com: Patch: Web: add GSoC ideas list http://code.google.com/p/lilypond/issues/detail?id=2381 Unless you've checked make doc and are sure it passes that, it's better to leave it at patch-new - that way patchy will check make, make doc, make test, etc. for you. Shouldn't take much time and is much safer. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Comment #3 on issue 2381 by janek.li...@gmail.com: Patch: Web: add GSoC ideas list http://code.google.com/p/lilypond/issues/detail?id=2381#c3 Web: add GSoC ideas list A list of suggested projects for Google Summer of Code students is necessary to participate in the program. http://codereview.appspot.com/5753059 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Verifying Issue 2338 OS X Lilypad not working Fwd: LilyPond 2.15.32 released
Am 06.03.2012 um 07:42 schrieb James:
> Hello,
>
> On 6 March 2012 02:36, James Worlton wrote:
>>
>> On Mar 5, 2012, at 4:41 PM, Colin Hall wrote:
>>
>>>
>>> Hi All,
>>>
>>> Thanks once again to all of you for volunteering to help the bug squad
>>> verify new Lilypond releases on MacOS X.
>>>
>>> We have a new release which includes a candidate fix for Issue 2338,
>>> the only remaining critical issue prior to the 2.16.0 release.
>>>
>>> http://code.google.com/p/lilypond/issues/detail?id=2338
>>>
>>> Please download 2.15.32 for your platform and check that it launches
>>> ok. If you have a lilypond file you can run through it, even better.
>>
>>
>> OSX 10.4.11 on PPC:
>> Lily 2.15.32 app opens fine, and compiled a file with several includes. No
>> problems for that part of it.
>>
>> However, my score had a construction similar to:
>>
>> \version "2.15.32"
>> \score {
>>\new Staff { a''4~ a''2.\fermata }
>> }
>>
>> In this case, the fermata collides with the tie. Is that a known issue?
>
> Yep.
>
> http://code.google.com/p/lilypond/issues/detail?id=570
>
> James
OS X 10.4.11 on PPC:
Everything works fine as reported before
OS X 10.6.8 on x86:
Everything fine too, app opens, several files compile without problems
ole
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2376 in lilypond: Automatic footnotes on \null markups causes unexpected results
Comment #12 on issue 2376 by d...@gnu.org: Automatic footnotes on \null markups causes unexpected results http://code.google.com/p/lilypond/issues/detail?id=2376 There is little enough reason to diverge, actually. page-layout-problem.cc is a total mess indiscriminately passing around pointers to Stencil and modifying them. As a result, there are not even enough physical Stencil objects to pass around for all the supposedly independent operations happening on them. I am currently cleaning this up as a diversion from the note collision programming. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Updates:
Labels: Patch-review
Comment #4 on issue 2381 by d...@gnu.org: Patch: Web: add GSoC ideas list
http://code.google.com/p/lilypond/issues/detail?id=2381#c4
Patchy the autobot says: LGTM.
/usr/local/tmp/lilypond/issue5753059_5001.diff:139: trailing whitespace.
familiarity with other scorewriters (for cross-testing) would be a nice
bonus.
/usr/local/tmp/lilypond/issue5753059_5001.diff:169: trailing whitespace.
@strong{Mentor(s):} Werner Lemberg
warning: 2 lines add whitespace errors.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Updates: Labels: Patch-new Comment #5 on issue 2381 by janek.li...@gmail.com: Patch: Web: add GSoC ideas list http://code.google.com/p/lilypond/issues/detail?id=2381#c5 Web: add GSoC ideas list A list of suggested projects for Google Summer of Code students is necessary to participate in the program. http://codereview.appspot.com/5753059 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Updates: Labels: -Patch-new Patch-review Comment #6 on issue 2381 by janek.li...@gmail.com: Patch: Web: add GSoC ideas list http://code.google.com/p/lilypond/issues/detail?id=2381 whitespace fixed. new patchset has only typo and whitespave changes, so i think there's no point in wasting your computation time - i'm setting it to review. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2376 in lilypond: Automatic footnotes on \null markups causes unexpected results
Updates: Labels: Patch-new Comment #13 on issue 2376 by d...@gnu.org: Automatic footnotes on \null markups causes unexpected results http://code.google.com/p/lilypond/issues/detail?id=2376#c13 Issue 2376: Automatic footnotes on \null markups causes unexpected results The page layout routines passed around pointers to stencils rather indiscriminately and worked on them rather than on stencil copies. Sort of copy-on-write without the copy. This tries working on actual copies where appropriate. http://codereview.appspot.com/5755058 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Verifying Issue 2338 OS X Lilypad not working Fwd: LilyPond 2.15.32 released
Hello
On 6 Mar 2012, at 02:36, James Worlton wrote:
>
> On Mar 5, 2012, at 4:41 PM, Colin Hall wrote:
>
>>
>> Hi All,
>>
>> Thanks once again to all of you for volunteering to help the bug squad
>> verify new Lilypond releases on MacOS X.
>>
>> We have a new release which includes a candidate fix for Issue 2338,
>> the only remaining critical issue prior to the 2.16.0 release.
>>
>> http://code.google.com/p/lilypond/issues/detail?id=2338
>>
>> Please download 2.15.32 for your platform and check that it launches
>> ok. If you have a lilypond file you can run through it, even better.
>
> OSX 10.4.11 on PPC:
> Lily 2.15.32 app opens fine, and compiled a file with several includes. No
> problems for that part of it.
>
> However, my score had a construction similar to:
>
> \version "2.15.32"
> \score {
> \new Staff { a''4~ a''2.\fermata }
> }
>
> In this case, the fermata collides with the tie. Is that a known issue?
Yep.
http://code.google.com/p/lilypond/issues/detail?id=570
James
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2376 in lilypond: Automatic footnotes on \null markups causes unexpected results
Updates: Labels: Patch-review Comment #14 on issue 2376 by d...@gnu.org: Automatic footnotes on \null markups causes unexpected results http://code.google.com/p/lilypond/issues/detail?id=2376#c14 Patchy the autobot says: LGTM. 3 lines add whitespace errors, but I trust you will fix this before committing. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
flood of mails with same issue
in the last months I've seen many mails with the same topic (or identical) addressed to several lists - this is a pain for several reasons, but my main concern is about where or how to answer these question so that if there is a reply on list A I don't have to send the same reply to list B (or C)! also, if somebody else replies on one list (only) this will not be visible on the other lists. this also means that I will never have a reliable overview of all the answers concerning this item. the problem can also be observed with issues on the tracker list - if an issue is being tracked, new answers to a list will not automatically be added to the tracker (and vice versa). is there a rule how such items should be treated? should we try to formulate something in this direction? eg. if a user asks for help on the user list and we find there is a bug with it, the discussion should go to the bug list (or maybe to the dev list). now the discussion goes on on the bug list - do we have to double everything to the user list? I don't know if I'm the only one with these "bad feelings" but I certainly would appreciate if this inflation could be stopped. another problem (maybe specific to Nabble): I have replied to many items and these replies didn't make it to the list - are they lost, will they appear later? sometimes I get warnings of Nabble alerts that my reply has not been accepted yet - but in fact they are already on the list… any contributions to this? thanks Eluze -- View this message in context: http://old.nabble.com/flood-of-mails-with-same-issue-tp33454680p33454680.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2376 in lilypond: Automatic footnotes on \null markups causes unexpected results
Comment #15 on issue 2376 by d...@gnu.org: Automatic footnotes on \null markups causes unexpected results http://code.google.com/p/lilypond/issues/detail?id=2376 Issue 2369 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2369 in lilypond: Strange interaction between page number settings and footnote
Updates: Status: Duplicate Owner: d...@gnu.org Mergedinto: 2376 Comment #2 on issue 2369 by d...@gnu.org: Strange interaction between page number settings and footnote http://code.google.com/p/lilypond/issues/detail?id=2369 However the fix to issue 2376 will be, I think we can agree that it will cover this issue as well. So I am marking this as a duplicate of that issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2335 in lilypond: 64 bit LilyPond segfaults
Comment #37 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults http://code.google.com/p/lilypond/issues/detail?id=2335 Any idea whether the fix for issue 2356 causes a difference here? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Unexpected warning, while enlarging staff-space
Hi,
this code gives an unexpected warning with 2.14.2 and 2.15.31. (No
warning with 2.12.3 )
\version "2.15.31"
\new Staff \with { \override StaffSymbol #'staff-space = #(magstep 4) }
\relative c''' { \voiceOne c8. c16 }
log:
programming error: No viable beam quanting found. Using unquanted y value.
continuing, cross fingers
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unexpected warning, while enlarging staff-space
2012/3/7 Thomas Morley :
> Hi,
>
> this code gives an unexpected warning with 2.14.2 and 2.15.31. (No
> warning with 2.12.3 )
>
>
> \version "2.15.31"
>
> \new Staff \with { \override StaffSymbol #'staff-space = #(magstep 4) }
> \relative c''' { \voiceOne c8. c16 }
>
>
> log:
> programming error: No viable beam quanting found. Using unquanted y value.
> continuing, cross fingers
>
>
>
> Cheers,
> Harm
Addition:
This comes out off a discussion on user:
http://lists.gnu.org/archive/html/lilypond-user/2012-03/msg00126.html
I suspect it leads to some weird output in real life examples
-> PNG attached to the mentioned post
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2327 in lilypond: Doc for preview command line option is hard to understand
Updates: Labels: -Patch-countdown Patch-push Comment #8 on issue 2327 by colinpkc...@gmail.com: Doc for preview command line option is hard to understand http://code.google.com/p/lilypond/issues/detail?id=2327 Counted down to 20120306, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2367 in lilypond: Notation Reference: Error in footnote documentation
Updates: Labels: -Patch-countdown Patch-push Comment #5 on issue 2367 by colinpkc...@gmail.com: Notation Reference: Error in footnote documentation http://code.google.com/p/lilypond/issues/detail?id=2367 Counted down to 20120306, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2356 in lilypond: Lilypond segfaults
Updates: Labels: -Patch-countdown Patch-push Comment #42 on issue 2356 by colinpkc...@gmail.com: Lilypond segfaults http://code.google.com/p/lilypond/issues/detail?id=2356 Counted down to 20120306, please push, although David and Neil have suggestions on Rietveld which could lead to a followup patch set. Calling for the push on this as it's marked Critical, and the suggestions sound as though they would improve the design of the patch but not the function. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2375 in lilypond: Patch: add ly:book-set-header!
Updates: Labels: -Patch-countdown Patch-push Comment #4 on issue 2375 by colinpkc...@gmail.com: Patch: add ly:book-set-header! http://code.google.com/p/lilypond/issues/detail?id=2375 Counted down to 20120306, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2370 in lilypond: Obsolete statement in Learning manual
Updates: Labels: -Patch-countdown Patch-push Comment #5 on issue 2370 by colinpkc...@gmail.com: Obsolete statement in Learning manual http://code.google.com/p/lilypond/issues/detail?id=2370 Counted down to 20120306, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Updates: Labels: -Patch-review Patch-push Comment #7 on issue 2381 by colinpkc...@gmail.com: Patch: Web: add GSoC ideas list http://code.google.com/p/lilypond/issues/detail?id=2381 Per Graham on Rietveld. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2381 in lilypond: Patch: Web: add GSoC ideas list
Updates: Status: Fixed Labels: -Type-Enhancement -Patch-push Type-Documentation Fixed_2_15_33 Comment #8 on issue 2381 by janek.li...@gmail.com: Patch: Web: add GSoC ideas list http://code.google.com/p/lilypond/issues/detail?id=2381 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2356 in lilypond: Lilypond segfaults
Updates: Status: Fixed Labels: Fixed_2_15_32 Comment #43 on issue 2356 by mts...@gmail.com: Lilypond segfaults http://code.google.com/p/lilypond/issues/detail?id=2356 Pushed as 2ccfd5a9f83819be67877522aeae7212fde3fefd. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2375 in lilypond: Patch: add ly:book-set-header!
Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_33 Comment #5 on issue 2375 by janek.li...@gmail.com: Patch: add ly:book-set-header! http://code.google.com/p/lilypond/issues/detail?id=2375 pushed as 744709d5ce7c67890c5c79f359f885a09cc26f27 thanks, Jan-Peter! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2382 in lilypond: Website: menu is misligned and colors in Community menu are wrong
Status: Accepted Owner: Labels: Type-Documentation Regression website New issue 2382 by janek.li...@gmail.com: Website: menu is misligned and colors in Community menu are wrong http://code.google.com/p/lilypond/issues/detail?id=2382 Last two positions in Community menu have wrong color (it should be similar to previous positions). Also, IIRC the menu bar was centered under the top bar, but now it isn't. This may be due to issue 2381 (commit cc5223ac26a5713c5901c02edf2868c26be10542) - sorry for that, it was necessary to push it fast. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: flood of mails with same issue
"-Eluze" wrote in message news:33454680.p...@talk.nabble.com... in the last months I've seen many mails with the same topic (or identical) addressed to several lists - this is a pain for several reasons, Could you give an example so I can see how they appeared on my system? -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
