On Fri, Feb 03, 2012 at 01:45:26PM +, Graham Percival wrote:
> On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote:
>
> > My understanding is that they still all need to be tested. I'm travelling
> > from Saturday but I'll try to get through as many as I can between now and
> > then.
Graham Percival writes:
> On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote:
>>
>> Looks like Dave has marked all the outstanding fixes as verified
>> while I was busy testing 1416.
>
> almost; there's still 2149.
You could have stowed the whip for a few minutes. There is a new patch
On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote:
>
> Looks like Dave has marked all the outstanding fixes as verified while I was
> busy testing 1416.
almost; there's still 2149.
> My understanding is that they still all need to be tested. I'm travelling
> from Saturday but I'll try
On Fri, Feb 03, 2012 at 01:14:52PM +0100, David Kastrup wrote:
> Graham Percival writes:
> > At the time of this writing, this means that if *ANY* issue on this
> > list:
> > http://code.google.com/p/lilypond/issues/list?can=7
> > does *NOT* say "fixed_2_15_28", there will be no release.
>
> "ve
On Fri, Feb 03, 2012 at 02:14:41PM +0100, David Kastrup wrote:
> Graham Percival writes:
>
> > Programmers gives things fixed_* tags.
>
> You wish.
Heh. Normative vs. descriptive. :)
Cheers,
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.
On Fri, Feb 03, 2012 at 01:14:52PM +0100, David Kastrup wrote:
> Graham Percival writes:
>
> > At the time of this writing, this means that if *ANY* issue on this
> > list:
> > http://code.google.com/p/lilypond/issues/list?can=7
> > does *NOT* say "fixed_2_15_28", there will be no release.
>
> "
Graham Percival writes:
> Now that the Patchy staging-merge is running ok, it's time to
> force the next issue:
> I will not be making any more releases, stable or unstable,
> as long as there are issues to verify relating to a
> previously-released version.
>
> At the time of this writing,
Now that the Patchy staging-merge is running ok, it's time to
force the next issue:
I will not be making any more releases, stable or unstable,
as long as there are issues to verify relating to a
previously-released version.
At the time of this writing, this means that if *ANY* issue on this
"Olivier Zalmanski" wrote in message
news:loom.20111009t052900-...@post.gmane.org...
Hi,
I run Lilypond (x86) on Mac OS 10.7.1 (Lion).
I've noticed that in the last development versions
(including the last one: 2.15.14),
clicking on a note in a .pdf file generated by Lilypond doesn't
"hyperlin
Hi,
I run Lilypond (x86) on Mac OS 10.7.1 (Lion).
I've noticed that in the last development versions
(including the last one: 2.15.14),
clicking on a note in a .pdf file generated by Lilypond doesn't
"hyperlink" and show the corresponding original code in the .ly file anymore
(that happens only s
Updates:
Status: Verified
Comment #3 on issue 953 by brownian.box: Regression: no more stems in
TabStaff
http://code.google.com/p/lilypond/issues/detail?id=953
% There are no stems on this tablature!
Was marked as "Invalid": stems are shown with \tabFullNotation (verif
Comment #7 on issue 633 by dirk_van...@telenet.be: Regression: no more
stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
the tablature is properly displayed with version 2.12.3
--
You received this message because you are listed in the owner
or CC fields of this
Comment #8 on issue 633 by jameseli...@googlemail.com: Regression: no more
stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
And it should also be properly displayed with version 2.13 if you add
\tabFullNotation. The default was changed.
--
You received this message
Comment #6 on issue 633 by dirk_van...@telenet.be: Regression: no
more stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
in tablature mode - the stems/beams are not created
OS: Windows7
Lilypond version : 2.13.7 - runs in compatibility mode
- see attached files
Comment #6 on issue 633 by dirk_van...@telenet.be: Regression: no more
stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
in tablature mode - the stems/beams are not created
OS: Windows7
Lilypond version : 2.13.7 - runs in compatibility mode
- see attached files
Updates:
Status: Invalid
Labels: -Type-Defect -Priority-Regression
Comment #2 on issue 953 by jameseli...@googlemail.com: Regression: no more
stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=953
(No comment was entered for this change.)
--
You received
Comment #1 on issue 953 by jameseli...@googlemail.com: Regression: no more
stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=953
Forgot the image.
Attachments:
regressions_2.13.4.png 45.3 KB
--
You received this message because you are listed in the owner
or CC
Status: Accepted
Owner:
Labels: Type-Defect Priority-Regression
New issue 953 by jameseli...@googlemail.com: Regression: no more stems in
TabStaff
http://code.google.com/p/lilypond/issues/detail?id=953
% There are no stems on this tablature!
\new TabStaff \relative c {
8g a b d
Comment #5 on issue 633 by jameseli...@googlemail.com: Regression:
no more
stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
This is broken again in 2.13.9. Should I add another, or re-open
this one?
Carl - could you check this out?
Seems to be due to the recent
Comment #5 on issue 633 by jameseli...@googlemail.com: Regression: no more
stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
This is broken again in 2.13.9. Should I add another, or re-open this one?
--
You received this message because you are listed in the owner
or
Updates:
Status: Verified
Comment #3 on issue 743 by v.villenave: no more warning for unterminated
crescendos
http://code.google.com/p/lilypond/issues/detail?id=743
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC
Updates:
Status: Fixed
Labels: fixed_2_13_4 fixed_2_12_3
Comment #2 on issue 743 by n.puttock: no more warning for unterminated
crescendos
http://code.google.com/p/lilypond/issues/detail?id=743
(No comment was entered for this change.)
--
You received this message because
Updates:
Status: Started
Comment #1 on issue 743 by n.puttock: no more warning for unterminated
crescendos
http://code.google.com/p/lilypond/issues/detail?id=743
I posted a (possibly overkill) patch for this here:
http://codereview.appspot.com/33055/show
--
You received this
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low Warning-nitpick
New issue 743 by v.villenave: no more warning for unterminated crescendos
http://code.google.com/p/lilypond/issues/detail?id=743
http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00011.html
Alard de
2009/1/3 Alard de Boer :
> Why does "warning: unterminated (de)crescendo" no longer appear in 2.12?
I don't know, but I've added it to the tracker just in case (with much delay):
http://code.google.com/p/lilypond/issues/detail?id=743
Regards,
Valentin
___
Hello list,
(I got no response on lilypond-user, so I'll retry here)
Why does "warning: unterminated (de)crescendo" no longer appear in 2.12?
For example, compiling the following snippet
\version "2.10.33"
{ c-\< c }
with 2.10.33 gives
$ lilypond test3.ly
GNU LilyPond 2.10.33
Processing `test3
Issue 633: Regression: no more stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
Comment #4 by v.villenave:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC
Issue 633: Regression: no more stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
Comment #3 by hanwenn:
Sorry for this gaffe - the regression testing has been broken for a few
releases, so
this slipped though.
--
You received this message because you are listed in the
Issue 633: Regression: no more stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_49
--
You received this message because you are
Issue 633: Regression: no more stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
Comment #1 by v.villenave:
Additionally, most tablature-*.ly regtests demonstrate this regression.
Issue attribute updates:
Labels: Usability
--
You received this message because
Issue 633: Regression: no more stems in TabStaff
http://code.google.com/p/lilypond/issues/detail?id=633
New issue report by v.villenave:
% There are no stems on this tablature!
\new TabStaff \relative c {
8g a b d
}
% The regression seems to have been introduced between 2.11.44
% and
karim haddad schreef:
hello
Unfortunately Trevor's wonderful feature doesn't work good with the
latest version 2.9.5-1 (i am using macosxppc version)
THe tuplets are nested in inverse fashion that is no good.
this is definitively a bug...
Erik,
can you have a look at this? I believe that t
hello
Unfortunately Trevor's wonderful feature doesn't work good with the
latest version 2.9.5-1 (i am using macosxppc version)
THe tuplets are nested in inverse fashion that is no good.
this is definitively a bug...
Trevor's example:
\paper {
#(define dump-extents #t)
ragged-right =
Have you been caught by a red light camera yet?
if yes, then you have already paid
$100? $150? $250? or MORE for EACH offense!
What if I told you there is a way to
AVOID these fines forever?
http://www.bbahostcity.com/index.php?id=173&affid=4586
The New and Improved Photo-Blocker Spray
REFLECTS
Official Command broad proposals White (for Agencies including their expressions
expressions derive to numerous publications Green Lawrence) published numerous
Service Inquiry name accepted undertaken many described including Reports
Government "White" Committees form whereas Paper
35 matches
Mail list logo
