Issue 1221 in lilypond: docs: Examples for \betweenLilyPondSystem contain two '#' instead of one
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Medium
New issue 1221 by brownian.box: docs: Examples for \betweenLilyPondSystem
contain two '#' instead of one
http://code.google.com/p/lilypond/issues/detail?id=1221
Reported by Spela Kermelj.
http://lilypond.org/doc/v2.13/Documentation/usage/latex -- examples for
\betweenLilyPondSystem contain two '#', should be only one.
\def\betweenLilyPondSystem#1{
% here:
\ifnum##12\else\expandafter\endinput\fi
}
\def\onlyFirstNSystems#1{
% here:
\def\betweenLilyPondSystem##1{%
% and here:
\ifnum##1#1\else\expandafter\endinput\fi}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: command: ragged-last-bottom=##f
On Sat 14 Aug 2010, 21:43 Spela Kermelj wrote: Thanks, I would have never found this solution myself... However, there's a typo in the manual, section Selected snippets, examples 2 and 4, should be \ifnum#1... instead of \ifnum##1... Thank you, added to tracker as issue 1221: http://code.google.com/p/lilypond/issues/detail?id=1221 -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1222 in lilypond: If one fingering has up orientation, then that what is left collides with accidental
Status: Accepted
Owner:
Labels: Type-Collision Priority-Medium
New issue 1222 by brownian.box: If one fingering has up orientation, then
that what is left collides with accidental
http://code.google.com/p/lilypond/issues/detail?id=1222
Reported by Nick Payne:
% -8 --
If the fingering for the C# is to the left, then the fingering for the
A automatically avoids the accidental. if the fingering for the C# is
above the note, whether placed by using ^ or with a \set command, then
the fingering for the A collides with the accidental.
\version 2.13.30
\relative c'' {
\set fingeringOrientations = #'(left)
cis-4 a-31
%
% 3 collides with sharp:
cis^4 a-3
\set fingeringOrientations = #'(up left)
%
% 3 collides with sharp:
cis-4 a-3
}
% -8 --
Attachments:
foo.png 1.3 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Chord fingering bug?
On Mon 16 Aug 2010, 17:19 Nick Payne wrote:
Is this a bug or a known problem or how things are supposed to work?
If the fingering for the C# is to the left, then the fingering for
the A automatically avoids the accidental. if the fingering for the
C# is above the note, whether placed by using ^ or with a \set
command, then the fingering for the A collides with the accidental.
\version 2.13.30
\relative c'' {
\override Fingering #'staff-padding = #'()
\override Fingering #'add-stem-support = ##f
\set fingeringOrientations = #'(left)
cis-4 a-31
cis^4 a-3
\set fingeringOrientations = #'(up left) cis-4 a-3
}
Thank you, i've added this to tracker as 1222:
http://code.google.com/p/lilypond/issues/detail?id=1222
(please, in such cases add bug-lilypond to Cc, thanks!)
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Installer defective
On Sun 15 Aug 2010, 18:37 Sanford Lung wrote: Upon trying to unzip lp 2.12.3 I get a dialogue that says: Unable to unarchive lilypond-2.12.3-1.darwin-x86.tar.bz2 into Downloads. (Error 32 - Broken pipe.) Help please. Please, Sanford Lung, can you check just everything --- free space on device, archive integrity etc-etc? iMac 2009. 3.0x MHz Intel, 4GB RAM, OSX 10.64 (Snow Leopard). Please, anyone else, can you prove is this a case? Thanks! -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1219 in lilypond: Broken tie may become a too small dot
Comment #3 on issue 1219 by brownian.box: Broken tie may become a too small
dot
http://code.google.com/p/lilypond/issues/detail?id=1219
Tie after line break is rather invisible.
To mimic that result i've set line-width to too small value, and notes
are engraved rather tight. But in real score (see above, test file and a
crop of real score) there is a lot of space to draw a tie (as it can be
seen with workaround presented).
% --- 8 ---
\version 2.13.30
\relative d'' {
\voiceTwo
d1( ~
\break
d4 d d d)
}
\paper {
indent = 0
ragged-right = ##t
line-width = 2\cm
}
% --- 8 ---
Attachments:
foo.png 1.4 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1041 in lilypond: Output suffix for score should be documented
Updates: Labels: Patch Comment #7 on issue 1041 by i...@hulin.org.uk: Output suffix for score should be documented http://code.google.com/p/lilypond/issues/detail?id=1041 I have produced a patch which is available for review on Rietveld http://codereview.appspot.com/2004041. Ian ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests
Comment #19 on issue 989 by pkx1...@hotmail.com: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 I think this is now done. of the 6 remaining snippets, 4 were committed yesterday and the last 2 have been put in the LSR by Phil. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1221 in lilypond: docs: Examples for \betweenLilyPondSystem contain two '#' instead of one
Comment #1 on issue 1221 by d...@gnu.org: docs: Examples for \betweenLilyPondSystem contain two '#' instead of one http://code.google.com/p/lilypond/issues/detail?id=1221 Inside of macros, you need to replicate # in order to get its original meaning. So the first definition is wrong, and the second definition is quite correct. I committed a fix. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1221 in lilypond: docs: Examples for \betweenLilyPondSystem contain two '#' instead of one
Comment #2 on issue 1221 by brownian.box: docs: Examples for \betweenLilyPondSystem contain two '#' instead of one http://code.google.com/p/lilypond/issues/detail?id=1221 Sorry, that was my (not Spela's) mistake. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
I don't find lilypond in my computer
Hi! I installed Ubuntu 10.04 LTS two weeks ago in my computer. I went to the download space (in german synaptic-paketverwaltung) and I downloaded lilypond, but I looked for the program in my computer and I didn't find it. Normally there's a place, where you can find all the programs that you download, but lilypond is not in this list. I hope you can help me, I really want to use this program! Thank you very much! Javi ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: I don't find lilypond in my computer
On Mon 16 Aug 2010, 07:56 Javi wrote: Hi! Hi! I installed Ubuntu 10.04 LTS two weeks ago in my computer. I went to the download space (in german synaptic-paketverwaltung) and I downloaded lilypond, but I looked for the program in my computer and I didn't find it. Normally there's a place, where you can find all the programs that you download, but lilypond is not in this list. As far as i understood --- you've downloaded lilypond binary and can not find downloaded file? If so, try to use search feature of your desktop manager. As a last resort --- try to right-click on link to lilypond binary and choose Save link target as... in popup menu. Then choose appropriate location to save in. Please excuse me if i misunderstood your question. If so, please clarify it in lilypond-user mailing list. Surely, the best place to get help regarding lilypond --- lilypond-user mailing list (http://lists.gnu.org/mailman/listinfo/lilypond-user), please ask any questions there. This list (bug-lilypond) is for other purposes. Thank you! -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: I don't find lilypond in my computer
Javi javid...@hotmail.com writes: I installed Ubuntu 10.04 LTS two weeks ago in my computer. I went to the download space (in german synaptic-paketverwaltung) and I downloaded lilypond, but I looked for the program in my computer and I didn't find it. Normally there's a place, where you can find all the programs that you download, but lilypond is not in this list. You probably mean the application menu. Lilypond is not an application, it is a compiler. You need to call it from the command line _after_ preparing your source file. You'll find the details in the lilypond documentation that need to get installed separately as lilypond-doc and will likely unpack into /usr/share/doc/lilypond-doc where you can browse through them with your browser. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc:
Jean-Charles, On 14/08/2010 17:09, Jean-Charles Malahieude wrote: Hi all! On my way to translate running.itely I notice that we have an @example environment that runs off the page in section LilyPond in chroot jail (starting line 509 of the source). It is reproduce as is in the full script for Ubuntu later on. Is it possible to split this script line? Yes, I checked CG doc policy: ...if possible, use a trailing backslash to break up a single line, indenting the next line with 2 spaces. I will make a simple patch and submit this to Graham. James ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc:
Le 16/08/2010 16:14, James disait : Jean-Charles, On 14/08/2010 17:09, Jean-Charles Malahieude wrote: Hi all! On my way to translate running.itely I notice that we have an @example environment that runs off the page in section LilyPond in chroot jail (starting line 509 of the source). It is reproduce as is in the full script for Ubuntu later on. Is it possible to split this script line? Yes, I checked CG doc policy: ...if possible, use a trailing backslash to break up a single line, indenting the next line with 2 spaces. I will make a simple patch and submit this to Graham. James You should have picked up http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00284.html The fact is that it is a full command line. It might perhaps be presented differently in the full script, just in order to be readable, but I have no idea as where to split this make closure. I made some attempts to run the full script on my box, but d I'm reluctant to crash it just before leaving for 10 days of vacation... Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc:
On Mon, Aug 16, 2010 at 3:47 PM, Jean-Charles Malahieude lily...@orange.fr wrote: Le 16/08/2010 16:14, James disait : Is it possible to split this script line? Yes, I checked CG doc policy: ...if possible, use a trailing backslash to break up a single line, indenting the next line with 2 spaces. I will make a simple patch and submit this to Graham. You should have picked up http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00284.html WTM?! James did everything correctly! - he checked our policy. - he discovered the way to break up a long line. Use a traiiling backslash is what I was hoping that you would discover if you did a the google searches that I asked you to. - he offered to take care of the patch. The fact is that it is a full command line. Unix uses a backslash to break up a long command-line. The resulting lines are parsed just like a full command line. ls \ -a \ -l \ *.png does exactly the same thing as ls -a -l *.png - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 612 in lilypond: spacing problem in tied chords with accidentals
Comment #6 on issue 612 by csny...@mvpsoft.com: spacing problem in tied chords with accidentals http://code.google.com/p/lilypond/issues/detail?id=612 When my patch was discussed, it seemed to me that the powers-that-be concluded that it was the wrong approach and not worth fixing up: http://lists.gnu.org/archive/html/lilypond-devel/2009-03/msg00344.html ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests
Comment #20 on issue 989 by percival.music.ca: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 LSR seems to be down; we won't have the latest 2 snippets until it's back up and we can download from the database. I agree that this issue seems done, though. :) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc:
Le 16/08/2010 17:02, Graham Percival disait : On Mon, Aug 16, 2010 at 3:47 PM, Jean-Charles Malahieude lily...@orange.fr wrote: Le 16/08/2010 16:14, James disait : Is it possible to split this script line? Yes, I checked CG doc policy: ...if possible, use a trailing backslash to break up a single line, indenting the next line with 2 spaces. I will make a simple patch and submit this to Graham. You should have picked up http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00284.html WTM?! James did everything correctly! - he checked our policy. - he discovered the way to break up a long line. Use a traiiling backslash is what I was hoping that you would discover if you did a the google searches that I asked you to. I googled for an example of such a long line with pipes and sed... I already know about it with makefiles but with shorter lines and do it when I can guess WHERE to split. Might feel better in two weeks, after vacations. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1215 in lilypond: Woodwind diagrams in the NR
Updates: Status: Started Owner: Carl.D.Sorensen Comment #4 on issue 1215 by percival.music.ca: Woodwind diagrams in the NR http://code.google.com/p/lilypond/issues/detail?id=1215 Carl said he wanted to do this. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1026 in lilypond: Documentation: adapting Lyrics when using \repeatTie
Updates: Status: Started Owner: tdanielsmusic Comment #6 on issue 1026 by percival.music.ca: Documentation: adapting Lyrics when using \repeatTie http://code.google.com/p/lilypond/issues/detail?id=1026 Trevor is rewriting the entire section, so he should take this into account. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1041 in lilypond: Output suffix for score should be documented
Updates: Status: Fixed Owner: --- Labels: fixed_2_13_31 Comment #8 on issue 1041 by percival.music.ca: Output suffix for score should be documented http://code.google.com/p/lilypond/issues/detail?id=1041 Pushed as 9748b8a77001b73bfd2bf35e27172a63d780c78d ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1223 in lilypond: doc for score-final mark mangles score-final tuplet bracket
Status: Started
Owner: PhilEHolmes
Labels: Type-Documentation Priority-Medium
New issue 1223 by percival.music.ca: doc for score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=1223
issue 573:
% The score-final mark badly mangles the score-final tuplet bracket:
% Actually, mark direction can be either up or down,
% but appears more clearly with the mark set down.
\version 2.11.37
\new Staff {
\set tupletFullLength = ##t
%% next line is required!
% \override TupletBracket #'full-length-to-extent = ##f
\time 1/8
\times 2/3 { c'16 c'16 c'16 }
\times 2/3 { c'16 c'16 c'16 }
\times 2/3 { c'16 c'16 c'16 }
\override Score.RehearsalMark #'break-visibility = ##(#t #t #t)
\override Score.RehearsalMark #'direction = #down
\override Score.RehearsalMark #'break-align-symbol = #'clef
\override Score.RehearsalMark #'self-alignment-X = #right
\mark Composed Feb 2007 - Feb 2008
}
This issue was fixed with an extra option. That option should be explained
in a snippet. The snippet should be added directly to LSR, tagged
with docs and rhythms, and imported into lilypond.
Phil Holmes is responsible for this.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 573 in lilypond: score-final mark mangles score-final tuplet bracket
Updates: Status: Fixed Owner: --- Comment #13 on issue 573 by percival.music.ca: score-final mark mangles score-final tuplet bracket http://code.google.com/p/lilypond/issues/detail?id=573 This was fixed almost two bloody years ago. The doc issue is a separate matter, and is now 1223. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1221 in lilypond: docs: Examples for \betweenLilyPondSystem contain two '#' instead of one
Updates: Status: Fixed Labels: fixed_2_13_31 Comment #3 on issue 1221 by percival.music.ca: docs: Examples for \betweenLilyPondSystem contain two '#' instead of one http://code.google.com/p/lilypond/issues/detail?id=1221 David pushed a fix in 814486057aa68c11988cb86375b44bf898cdc300 ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
\autoBeamOff
Dear LilyPonders,
while trying to typeset some vocal music I encountered some
difficulties with \autoBeamOff:
1) \autoBeamOff has no effect on other voices when used in a global
variable/ghost voice. It has to be turned on explicitly for each
voice. This is probably intentional but AFAIK not mentioned in the docs.
2) \autoBeamoff shows strange effects in combination with 16th notes
and \partcombine. \autoBeamOff only effects 16th notes when they
happen to be in the first measure of a combined part. All following
measures containing 16th notes are beamed automatically as if
automatic beaming had been turned on again. This looks like a bug to
me!? (No problems with \autoBeamOff in standard polyphonic notation)
In combination with \autoBeamOff \partcombine seems to require some
curly braces, e.g.:
\partcombine { \autoBeamOff\MusicPartOne } { \autoBeamOff
\MusicPartTwo }
I didn't find this information in the docs.
Here's an example (please uncomment/comment the first measure in each
variable):
\version 2.13.30
global = {
\time 2/4
\key f\major
\autoBeamOff
%s2
s2
}
Soprano = {
%f'8 f' f' f' |
g'16(a'16) bes'16 (g'16) f'16 (e'16) d'16(e'16) |
}
Alto = {
%f'8 f' f' f' |
d'4 bes8 bes8 |
}
\score {
\new Staff = SopranoAlto
\new Voice = globalSettings {
\global
}
\partcombine %\Soprano\Alto
%\autoBeamOff\Soprano
%\autoBeamOff\Alto
{ \autoBeamOff\Soprano }
{ \autoBeamOff\Alto }
\layout {
\context { \Staff
printPartCombineTexts = ##f
}
}
}
HTH
patrick
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Problem with 2.13.30?
Eluze wrote Sunday, August 15, 2010 10:20 AM Trevor Daniels wrote: The mingw binary of 2.13.30 gives the following error under Vista on my system: Running lilypond-book Traceback (most recent call last): File c:/program files/lilypond/usr/bin/lilypond-book.py, line 86, in ? import book_base as BookBase File out/book_base.py, line 4, in ? File out/book_snippets.py, line 9, in ? File c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py, line 352, in ? import msvcrt ImportError: No module named msvcrt Lilypond-book returned code 1 2.13.23 is fine whereas 2.13.25 + higher have the above messages ( i haven't loaded 2.13.24)! Thanks Eluze. To help track this down, 2.13.23 was built on 3 Jun 2010 2.13.24 was built on 14 Jun 2010 2.13.25 was built on 20 Jun 2010 Jan's change to MinGW as reported by Patrick: This could be related to Jan's recent changes to the MinGW Python build in GUB. Something related to msvcrt was added here: http://github.com/janneke/gub/commit/e3d46689d881045ceb2dbf31d7d4573709f781d8#L1R136 was made on 18 Jul 2010, so this can't be the cause. Reinhold's refactoring of lilypond-book modules was first included in the 2.13.24 release, so this looks a more likely cause. He made a series of changes terminating in commit 7d4265883794cec4ad0e7312f0787d0565fe757f on 11 Jun 2010. Bug-squad: can you please raise an issue for this. lilypond-book in the MinGW release is currently unusable. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1129 in lilypond: Font styles return to default when font size changed
Updates: Status: Accepted Owner: --- Comment #6 on issue 1129 by pnorcks: Font styles return to default when font size changed http://code.google.com/p/lilypond/issues/detail?id=1129 I don't really have any ideas about how to fix this at the moment. I made a few comments in this post that might be relevant: http://lists.gnu.org/archive/html/lilypond-user/2010-08/msg00160.html Anyone who wants to spend more time on this issue should also consider looking at issue 216. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \autoBeamOff
On 8/16/10 3:30 PM, Patrick Schmidt p.l.schm...@gmx.de wrote:
Dear LilyPonders,
while trying to typeset some vocal music I encountered some
difficulties with \autoBeamOff:
1) \autoBeamOff has no effect on other voices when used in a global
variable/ghost voice. It has to be turned on explicitly for each
voice. This is probably intentional but AFAIK not mentioned in the docs.
This is probably an argument for eliminating \autoBeamOff. As can be seen
in ly/property-init.ly, \autoBeamOff is an alias for
\set autoBeaming = ##f
If you want it to apply in a global voice, simply do
\set Score.autoBeaming = ##f
2) \autoBeamoff shows strange effects in combination with 16th notes
and \partcombine. \autoBeamOff only effects 16th notes when they
happen to be in the first measure of a combined part. All following
measures containing 16th notes are beamed automatically as if
automatic beaming had been turned on again. This looks like a bug to
me!? (No problems with \autoBeamOff in standard polyphonic notation)
This is a *very* challenging bug. Partcombine apparently works with 3
voices -- stem up single, stem down single, stem up combined.
An \autoBeamOff call in the first argument to partcombine will apply to the
voice that is active at the time the call is processed, either stem up
single or stem up combined. An \autoBeamOff call in the second argument
will apply to the voice that is stem down single.
In order to use \autoBeamOff to stop all autobeaming, it will be necessary
to use *3* calls to \autoBeamOff.
A workaround is to \set Staff.autoBeaming = ##f
Note -- I do consider this to be a bug with partcombine. There is a
workaround, however.
Here is a tiny example (you can uncomment and comment the various lines to
change the behavior):
\version 2.13
{
%\set Staff.autoBeaming = ##f % turns off all autobeaming
\partcombine
{
\autoBeamOff % applies to split up stems
\repeat unfold 4 a'16
%\autoBeamOff % applies to combined up stems
\repeat unfold 4 a'8
\repeat unfold 4 a'16
}
{
\autoBeamOff % applies to down stems
\repeat unfold 4 f'8
\repeat unfold 8 f'16 |
}
}
In combination with \autoBeamOff \partcombine seems to require some
curly braces, e.g.:
\partcombine { \autoBeamOff\MusicPartOne } { \autoBeamOff
\MusicPartTwo }
I didn't find this information in the docs.
This problem is not specific to \autoBeamOff. \partcombine always works on
the next two music expressions. Without the curly braces it would be
\autoBeamOff and \MusicPartOne that would be combined.
HTH,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel
Comment #19 on issue 1096 by musiccomposition: ly:parser-parse-string segfaults when directly called at toplevel http://code.google.com/p/lilypond/issues/detail?id=1096 New patch to use parser_error(). Attachments: 0001-don-t-allow-ly-parser-parse-file-to-continue-unless-.patch 1.7 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
