Hi Thomas, thanks for the reply.
I think there are two issues at play here. One issue is that user input
should never crash the program. It took nontrivial effort to track down
why my scores were crashing after upgrading Lilypond (since in some distant
past version, it didn't crash.) Even if th
Hope I interpreted Trevor's comment correctly. The roposed "new" order
did not occur to me since it violates causation: the (now) first change
is dependent on the second one. However, that is on an implementation
level and probably not interesting to the user.
https://codereview.appspot.com/74
Thomas Morley wrote
> 2013/2/24 David Kastrup <
> dak@
> >:
>> Thomas Morley <
> thomasmorley65@
> > writes:
>>
>>>
>>>
>>> Bar and bar number checks
>>>
>>> Bar checks help detect errors in the entered durations. A bar check
>>> may be entered using the bar symbol, |, at any place where a
Il 24/02/2013 17:54, Thomas Morley ha scritto:
Some more investigation:
The problem seems to be related to \midi
\score {
{ | d }
\midi { }
}
returns a segfault with 2.16.1 and 2.17.12
I can confirm it on 2.16.2 and 2.17.3
Thanks for the investigation and the minimal example.
Added her
Kieren MacMillan writes:
> Hello all,
>
> I'm working on a medium-sized score (chamber opera). I'm currently
> getting the following output:
>
> Drawing
> systems.../Applications/Lilypond/LilyPond.app/Contents/Resources/share/lilypond/current/scm/bar-line.scm:926:28:
> In procedure ly:grob-array-
Il 24/02/2013 16:02, David Kastrup ha scritto:
Can the bug team register a bug for it? If we don't get a response in
about two days from the original author, I'd suggest reverting it.
added as:
http://code.google.com/p/lilypond/issues/detail?id=3204
--
Federico
__
Keiren,
On 24 February 2013 19:01, Kieren MacMillan
wrote:
> Hello all,
>
> I'm working on a medium-sized score (chamber opera). I'm currently getting
> the following output:
>
> Drawing
> systems.../Applications/Lilypond/LilyPond.app/Contents/Resources/share/lilypond/current/scm/bar-line.scm:926
Hi James,
> does using '--loglevel=DEBUG'
> get you anything more useful?
No -- same output.
Thanks,
Kieren.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello all,
I'm working on a medium-sized score (chamber opera). I'm currently getting the
following output:
Drawing
systems.../Applications/Lilypond/LilyPond.app/Contents/Resources/share/lilypond/current/scm/bar-line.scm:926:28:
In procedure ly:grob-array-length in expression (ly:grob-array-le
On 24 févr. 2013, at 11:45, k-ohara5...@oco.net wrote:
> This still needs some cleanup, at least to remove the now-redundant
> \tupletOutsideStaffPriority
>
It's not redundant just cuz if it's not set, LilyPond will now issue a warning.
If you want the regtest to have a warning, we can convert
2013/2/24 David Kastrup :
> Thomas Morley writes:
>
>>
>>
>> Bar and bar number checks
>>
>> Bar checks help detect errors in the entered durations. A bar check
>> may be entered using the bar symbol, |, at any place where a bar line
>> is expected to fall. If bar check lines are encountered
James writes:
> David,
>
> I am unable to merge staging with master as staging fails make.
>
> Same error as I reported in patch test for 3202.
>
> Commit has made it into staging
>
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=1fc366d3002d654038489af1e6e0ee2ad6efa2bf
Looks lik
Thomas Morley writes:
>
>
> Bar and bar number checks
>
> Bar checks help detect errors in the entered durations. A bar check
> may be entered using the bar symbol, |, at any place where a bar line
> is expected to fall. If bar check lines are encountered at other
> places, a list of warning
Albrecht Jacobs wrote Sunday, February 24, 2013 9:03 AM
> In Section Text: Stand-alone two-column markup
>
> (http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/Text#Stand_002dalone-two_002dcolumn-markup)
>
> it would be easier to use this code:
>
> diff two-column-markup.ly two-column
2013/2/24 Steve Yegge :
> Here's a small input file which for me produces a bus error when compiled
> with version 2.16.2 on OS X 10.7.5 (intel):
>
> \version "2.16.2"
>
> music = {
> | d
> }
>
> \score {
> << \new Staff { \music } >>
> }
>
> \score {
> \music
> \midi {
> \context {
>
On 24 févr. 2013, at 17:18, David Kastrup wrote:
> "m...@mikesolomon.org" writes:
>
>> On 24 févr. 2013, at 16:37, d...@gnu.org wrote:
>>
>>> On 2013/02/24 13:27:39, mike7 wrote:
On 24 févr. 2013, at 12:40, mailto:d...@gnu.org wrote:
>>>
> Stupid question: could you not just check w
Il 24/02/2013 06:46, Steve Yegge ha scritto:
Here's a small input file which for me produces a bus error when
compiled with version 2.16.2 on OS X 10.7.5 (intel):
\version "2.16.2"
music = {
| d
}
\score {
<< \new Staff { \music } >>
}
\score {
\music
\midi {
\context {
We have a number of pictures that are used to make the docs and the website
clearer to understand - not the snippets, but other illustrative stuff,
like:
http://lilypond.org/doc/v2.17/Documentation/pictures/architecture-diagram.png
http://lilypond.org/website/pictures/flat-design.png
These are
David,
I am unable to merge staging with master as staging fails make.
Same error as I reported in patch test for 3202.
Commit has made it into staging
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=1fc366d3002d654038489af1e6e0ee2ad6efa2bf
Regards
James
In Section Text: Stand-alone two-column markup
(http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/Text#Stand_002dalone-two_002dcolumn-markup)
it would be easier to use this code:
diff two-column-markup.ly two-column-markup-1.1.ly
13,19c13,19
< \column {
< \line { \italic { O s
Here's a small input file which for me produces a bus error when compiled
with version 2.16.2 on OS X 10.7.5 (intel):
\version "2.16.2"
music = {
| d
}
\score {
<< \new Staff { \music } >>
}
\score {
\music
\midi {
\context {
\Score
midiInstrument = #"acoustic guitar (st
2013/2/24 Trevor Daniels :
>
>> Comment #3 on issue 3203 by philehol...@googlemail.com: Connecting bar
>> lines missing in piano staffs
>> http://code.google.com/p/lilypond/issues/detail?id=3203
>>
>> I'm in two minds, TBH. On the one hand, we always say "this is a
>> development version - use it
> Comment #3 on issue 3203 by philehol...@googlemail.com: Connecting bar
> lines missing in piano staffs
> http://code.google.com/p/lilypond/issues/detail?id=3203
>
> I'm in two minds, TBH. On the one hand, we always say "this is a
> development version - use it at your risk". And it's gene
"m...@mikesolomon.org" writes:
> On 24 févr. 2013, at 16:37, d...@gnu.org wrote:
>
>> On 2013/02/24 13:27:39, mike7 wrote:
>>> On 24 févr. 2013, at 12:40, mailto:d...@gnu.org wrote:
>>
>>> > Stupid question: could you not just check whether
>>> > outside-staff-priority has been set, and if it ha
> Does anyone else think we should rush out an updated development
> version?
I don't want a new release just for this very bug.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
"Phil Holmes" writes:
> 1. Please don't email me directly - please use the developer mailing
> list.
> 2. Please supply some code that illustrates the problem.
> 3. An immediate fix is to use 2.16.2. If there is a problem with
> 2.17.13 it will likely be fixed in due course, if you can provide a
Werner LEMBERG writes:
> [cd03b4ac]
>
>
> I just got this:
>
> articulate.ly:446:13: In procedure map in expression (map (lambda # #)):
> articulate.ly:446:13: Wrong number of arguments to #
>
> using this input:
>
> \version "2.17.13"
>
> \include "articulate.ly"
>
> \relative c' {
>
On 24 févr. 2013, at 16:37, d...@gnu.org wrote:
> On 2013/02/24 13:27:39, mike7 wrote:
>> On 24 févr. 2013, at 12:40, mailto:d...@gnu.org wrote:
>
>> > Stupid question: could you not just check whether
>> > outside-staff-priority has been set, and if it has, pass the buck
>> > to the right kind o
On 2013/02/24 13:27:39, mike7 wrote:
On 24 févr. 2013, at 12:40, mailto:d...@gnu.org wrote:
> Stupid question: could you not just check whether
> outside-staff-priority has been set, and if it has, pass the buck
> to the right kind of callback automatically? That way, the user
> does not need
[cd03b4ac]
I just got this:
articulate.ly:446:13: In procedure map in expression (map (lambda # #)):
articulate.ly:446:13: Wrong number of arguments to #
using this input:
\version "2.17.13"
\include "articulate.ly"
\relative c' {
\unfoldRepeats \articulate {
\repeat vol
- Original Message -
From: Karol Majewski
To: Phil Holmes
Sent: Sunday, February 24, 2013 12:52 PM
Subject: What happened to systemic barlines?
Hi Phil, something's wrong with 2.17.13. Barlines in piano staff
do not connect upper and lower staff by default! Any chances for
an immedia
On 24 févr. 2013, at 12:40, d...@gnu.org wrote:
> Stupid question: could you not just check whether outside-staff-priority
> has been set, and if it has, pass the buck to the right kind of callback
> automatically? That way, the user does not need to meddle with
> callbacks himself.
>
> https://
LGTM apart from the suggested change.
https://codereview.appspot.com/7404046/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/7404046/diff/1/Documentation/changes.tely#newcode83
Documentation/changes.tely:83: would have been the other way
1. Please don't email me directly - please use the developer mailing list.
2. Please supply some code that illustrates the problem.
3. An immediate fix is to use 2.16.2. If there is a problem with 2.17.13 it
will likely be fixed in due course, if you can provide a tiny example as
requested above
Stupid question: could you not just check whether outside-staff-priority
has been set, and if it has, pass the buck to the right kind of callback
automatically? That way, the user does not need to meddle with
callbacks himself.
https://codereview.appspot.com/7185044/
___
This still needs some cleanup, at least to remove the now-redundant
\tupletOutsideStaffPriority
The goal was to have outside-staff grobs figure their own Y-offset,
including the offset required for the outside-staff grobs to avoid each
other. The group of all objects on a line (VerticalAxisGroup
There's some book-keeping error that I can't find. The example at issue
3160 comes out wrong.
https://codereview.appspot.com/7304068/diff/16001/lily/align-interface.cc
File lily/align-interface.cc (right):
https://codereview.appspot.com/7304068/diff/16001/lily/align-interface.cc#newcode65
lily
37 matches
Mail list logo
