I think this is better in the bug mailing list. Thererfore I sent it
here again.
I try to follow the instructions on this page:
http://lilypond.org/doc/v2.14/Documentation/extending/scheme-sandbox.html
Unfortunately I get an error message, when I try to start guile.exe:
ERROR: In procedure pr
I downloaded the most recent development version for my Mac PPC (10.4) system,
and double-clicked the LilyPond.app after extracting the .tar.bz2 file. Normally
this opens up the test file that you can save & compile. This time, though, the
program would not start up. I get a dialog box showing "Lil
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_28
Comment #9 on issue 2256 by carl.d.s...@gmail.com: empty strings: tabStaff
insists on stringnumbers and looses notes
http://code.google.com/p/lilypond/issues/detail?id=2256
Pushed to staging as 9203ead
Comment #1 on issue 2266 by themu...@gmail.com:
@rlsrnamed{Name,Translation} translates also the name in the URI
http://code.google.com/p/lilypond/issues/detail?id=2266
I encounter the same problem with many pages of dev version's manuals, such
as : http://lilypond.org/doc/v2.15/Documentati
Comment #1 on issue 2265 by x.sche...@gmail.com: problem with
beam-shortened-length.ly
http://code.google.com/p/lilypond/issues/detail?id=2265
Duplicate of issue 2258 ,
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailm
Comment #1 on issue 1627 by themu...@gmail.com: global-staff-size effects
on grace notes (LilyPond 2.13.58)
http://code.google.com/p/lilypond/issues/detail?id=1627
Moreover, there is no other possible rendering between staff18.png and this
one, with \override Beam #'beamed-stem-shorten = #'
Updates:
Labels: Patch-review
Comment #6 on issue 1022 by lilypond...@gmail.com: \chordmode neglects
point-and-click
http://code.google.com/p/lilypond/issues/detail?id=1022#c6
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
bu
Hello,
On 30 January 2012 21:27, Ralph Palmer wrote:
> On Sun, Jan 29, 2012 at 9:38 AM, Federico Bruni wrote:
>>
>> Got no answers on -devel, so I forward here (probably more appropriate
>> place).
>>
>> Thanks,
>> Federico
>>
>> Il 05/01/2012 13:44, Federico Bruni ha scritto:
>>>
>>> Issue 1721
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2266 by ralphbug...@gmail.com: @rlsrnamed{Name,Translation}
translates also the name in the URI
http://code.google.com/p/lilypond/issues/detail?id=2266
Federico Bruni writes :
Issue 1721 reported that @rlsr{Name} keeps the text
On Sun, Jan 29, 2012 at 9:38 AM, Federico Bruni wrote:
> Got no answers on -devel, so I forward here (probably more appropriate
> place).
>
> Thanks,
> Federico
>
> Il 05/01/2012 13:44, Federico Bruni ha scritto:
>
>> Issue 1721 reported that @rlsr{Name} keeps the text in english but
>> translate
Status: Accepted
Owner:
Labels: Type-Ugly Regression
New issue 2265 by ralphbug...@gmail.com: problem with
beam-shortened-length.ly
http://code.google.com/p/lilypond/issues/detail?id=2265
Janek Warchol writes :
i think the output of beam-shortened-lengths.ly doesn't look good, see
in cu
2012/1/26 Janek Warchoł
> Hi,
>
> i think the output of beam-shortened-lengths.ly doesn't look good, see
> in current regtests
> http://www.lilypond.org/doc/v2.15/input/regression/collated-files.html
> . Am i missing something?
>
> cheers,
> Janek
>
Thanks, Janek.
I agree. It took me awhile to
Updates:
Status: Started
Owner: d...@gnu.org
Comment #5 on issue 1022 by d...@gnu.org: \chordmode neglects
point-and-click
http://code.google.com/p/lilypond/issues/detail?id=1022
(No comment was entered for this change.)
___
bug-li
Updates:
Labels: Patch-new
Comment #4 on issue 1022 by d...@gnu.org: \chordmode neglects
point-and-click
http://code.google.com/p/lilypond/issues/detail?id=1022#c4
Add location info to chords; issue 1022
What an embarrassingly longstanding bug.
http://codereview.appspot.com/5581049
Updates:
Labels: Patch-new
Comment #11 on issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263#c11
Remove basically all configurability. Reduce parser and lexer support
to hardwired minimum. Don't track the last chord in the l
for single staff-systems:
systems-per-page 1,2 --> ok; 3 --> fails; 4 --> ok; 5 -->fails
for double staff systems ( { << {\music} {\music} >> } instead of { \music })
processing fails for any value >1
(mac osx 10.7.2)
Am 30.01.2012 um 19:32 schrieb Phil Holmes:
> - Original Message
- Original Message -
From: "Martin Straeten"
To:
Cc:
Sent: Monday, January 30, 2012 6:04 PM
Subject: Re: exceeding processing time when processing multiple scores
within onebook
i can reproduce it with OS:
Windows XP 32bit
Mac OS X 10.7.2
kind regards,
Martin
AFAICS this funct
Julia Young-2 wrote:
>
> Please send me authorization for your program, as I am anxious to try it
> out!
>
welcome!
you don't need a license - just go to http://lilypond.org/ where you'll find
the download link.
Eluze
--
View this message in context:
http://old.nabble.com/I-am-a-real-person
i can reproduce it with OS:
Windows XP 32bit
Mac OS X 10.7.2
kind regards,
Martin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Please send me authorization for your program, as I am anxious to try it out!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
"Martin Straeten" wrote in message
news:ca+vre1kanpqauwyqnzqq1ez9dgjdn79zngrrn2fdx_n1m9w...@mail.gmail.com...
With current stable release 2.14.2 and development release 2.15.27
the processing time exceeds when several scores are typeset within
one book with given numer of systems per page.
Usin
"Phil Holmes" writes:
> "G.S. Williams" wrote in message
> news:loom.20120130t041720-...@post.gmane.org...
>> Hi,
>>
>> I've been tied up with classical music for several decades,
>> and we have always referred to
>> pairs of notes as "DUPLETS",
>> not,"TUPLETS:.why do you people in the U.S.A. a
"G.S. Williams" wrote in message
news:loom.20120130t041720-...@post.gmane.org...
Hi,
I've been tied up with classical music for several decades,
and we have always referred to
pairs of notes as "DUPLETS",
not,"TUPLETS:.why do you people in the U.S.A. always
change terminology?
I''m curious!
C
Updates:
Labels: -Patch-new Patch-review
Comment #10 on issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263
Patchy now shows no changes in output. This would be a candidate for
merging, so be sure to give it a serious beatin
With current stable release 2.14.2 and development release 2.15.27
the processing time exceeds when several scores are typeset within
one book with given numer of systems per page.
Using 2.13.20 the attached sample works fine
(even a real life book with > 30 piano scores can be processed);
with 2.
Comment #5 on issue 2178 by o...@villumsen.name: NR: clarify the
subsection "Automatic accidentals" of section 1.1.3
http://code.google.com/p/lilypond/issues/detail?id=2178
If a beginner's comment is allowed, I'm quite fond of the functionality and
flexibility offered by the current interfa
On 29 January 2012 12:20, Graham Percival wrote:
> On Sun, Jan 29, 2012 at 11:00:03AM +, James wrote:
>> Here Mr Holmes!
>>
>> On 29 January 2012 10:51, Phil Holmes wrote:
>> > I know Brett is no longer squadding, and that Marek and James have been
>> > taking up the slack. Could I have a ro
Comment #4 on issue 2178 by d...@gnu.org: NR: clarify the
subsection "Automatic accidentals" of section 1.1.3
http://code.google.com/p/lilypond/issues/detail?id=2178
This is the sort of thing that is very awkward to explain to users. It is
also awkward to use. Probably we should create an
Comment #3 on issue 2178 by o...@villumsen.name: NR: clarify the
subsection "Automatic accidentals" of section 1.1.3
http://code.google.com/p/lilypond/issues/detail?id=2178
Thank you, James, for your interest in my problem (my eks-problem; I
understand now what I had a problem understanding
Comment #9 on issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263#c9
Remove basically all configurability. Reduce parser and lexer support
to hardwired minimum. Don't track the last chord in the lexer/parser.
Instead establish it at
Comment #8 on issue 2263 by d...@gnu.org: Reimplement chord repetition
http://code.google.com/p/lilypond/issues/detail?id=2263#c8
Remove basically all configurability. Reduce parser and lexer support
to hardwired minimum. Don't track the last chord in the lexer/parser.
Instead establish it at
31 matches
Mail list logo
