On Wed, Nov 02, 2011 at 11:40:11PM -0700, Linus Arver wrote:
> The dot in
>
> \version "2.15.16"
> {
> ces''-.
> }
>
> is pushed up needless above the staff, when it can fit perfectly
> fine where the E note goes.
>
> Please see attachments.
>
> -Linus
> \version "2.15.16"
The dot in
\version "2.15.16"
{
ces''-.
}
is pushed up needless above the staff, when it can fit perfectly
fine where the E note goes.
Please see attachments.
-Linus
\version "2.15.16"
% the dot position here is fine
{
c''-.
}
% the dot in all three examples below is n
Phil Holmes-2 wrote:
>
> "Thomas Spuhler" wrote in message
> news:loom.20111027t065750...@post.gmane.org...
>> This bug looks similar to #1927 but for a different file:
>>
>> This is BibTeX, Version 0.99d (TeX Live 2011/Mageia)
>> The top-level auxiliary file: /tmp/tmpyckTc6bib2texi.aux
>> The
Comment #16 on issue 1503 by adam.spi...@gmail.com: Feature request:
simplify jazz chord display
http://code.google.com/p/lilypond/issues/detail?id=1503
Hmm, input/regression/chord-name-exceptions.ly seems to show a regression -
the slash between the 'Co7' and 'F' vanishes. Investigating .
On Wed, Nov 02, 2011 at 08:46:51PM +0100, David Kastrup wrote:
> b) in fact, other people _have_ seen that problem with Lilypond and have
> reported it for years, each time mentioning that it did occur
> sporadically, in connection with parallel make, and could be "fixed" by
> repeating the make ru
Julien Rioux writes:
> One should be careful not to take such guesses as postulates, as it
> seems I did. I don't think we want someone (the poster, or a good
> samaritan willing to spend some of their free time happily fixing
> things up in the lilypond build system) to spend time tracking down
On 02/11/2011 5:08 PM, David Kastrup wrote:
If you read all of the text I wrote above, you'll not find _any_
postulate. I am providing information and impressions from my own
experience and knowledge in order to help the original poster have a
better idea how to figure out what is wrong. I am n
Comment #15 on issue 1503 by adam.spi...@gmail.com: Feature request:
simplify jazz chord display
http://code.google.com/p/lilypond/issues/detail?id=1503
I think I am now finished. The new patch series is available at
https://github.com/aspiers/lilypond/commits/jazz
You can fetch it via
> > Yes, the dots on the lower voice should be both down, not one up and one
> > down.
http://code.google.com/p/lilypond/issues/detail?id=1266
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
- Original Message -
From: "Nick Payne"
To: "Phil Holmes"
Cc:
Sent: Tuesday, November 01, 2011 9:01 PM
Subject: Re: Polyphony, ledger lines, and dotted notes
On 02/11/11 01:45, Phil Holmes wrote:
- Original Message - From: "Nick Payne"
To:
Sent: Tuesday, November 01, 2
Comment #6 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c6
Fixes NoteColumn vs SpanBar collisions.
http://codereview.appspot.com/5323062
___
bug-lilypond
Status: Accepted
Owner:
Labels: Type-Other
New issue 2006 by pkx1...@gmail.com: MIDI volume goes beyond maximum after
staff change
http://code.google.com/p/lilypond/issues/detail?id=2006
As suggested the in thread "MIDI dynamics doesn't apply to multi-voice
measures", I converted the sco
Hello,
On Wed, Nov 2, 2011 at 3:46 PM, Pavel Roskin wrote:
> On Tue, 1 Nov 2011 15:46:47 -
> "Phil Holmes" wrote:
>
>> Please don't open a bug report yourself - that's the job of the bug
>> squad. Please could you create a lilypond source file that
>> demonstrates the problem in the form of
Julien Rioux writes:
> On 02/11/2011 4:04 PM, David Kastrup wrote:
>> Julien Rioux writes:
>>
>>> On 27/10/2011 7:01 AM, Thomas Spuhler wrote:
LANG= makeinfo --enable-encoding -I
/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.15.15/Documentation -I.
-I./out --no-split --no-head
Comment #5 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c5
Fixes NoteColumn vs SpanBar collisions.
http://codereview.appspot.com/5323062
___
bug-lilypond
On 02/11/2011 4:04 PM, David Kastrup wrote:
Julien Rioux writes:
On 27/10/2011 7:01 AM, Thomas Spuhler wrote:
LANG= makeinfo --enable-encoding -I
/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.15.15/Documentation -I.
-I./out --no-split --no-headers --output out/contributor.txt
out/contribu
On Tue, 1 Nov 2011 15:46:47 -
"Phil Holmes" wrote:
> Please don't open a bug report yourself - that's the job of the bug
> squad. Please could you create a lilypond source file that
> demonstrates the problem in the form of a "tiny" example:
> http://lilypond.org/website/tiny-examples.html
Julien Rioux writes:
> On 27/10/2011 7:01 AM, Thomas Spuhler wrote:
>> LANG= makeinfo --enable-encoding -I
>> /home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.15.15/Documentation -I.
>> -I./out --no-split --no-headers --output out/contributor.txt
>> out/contributor.texi
>> out/contributor.texi:
Updates:
Status: Fixed
Comment #7 on issue 1977 by pkx1...@gmail.com: BarLine #'bar-extent wrongly
documented as internal property
http://code.google.com/p/lilypond/issues/detail?id=1977
Pushed to dev\staging as
commit 2e13162f4b1b0d3669d2bfd6cf50becd66203581
James
__
On 27/10/2011 7:01 AM, Thomas Spuhler wrote:
LANG= makeinfo --enable-encoding -I
/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.15.15/Documentation -I.
-I./out --no-split --no-headers --output out/contributor.txt
out/contributor.texi
out/contributor.texi: No such file or directory
make[1]: **
Updates:
Status: Fixed
Comment #10 on issue 1917 by pkx1...@gmail.com: Hyperlinks in
web-big-page.html do not work
http://code.google.com/p/lilypond/issues/detail?id=1917
Pushed to dev\staging as
commit ab85e289fdec993c217bf139893da6407259c6ea
_
Updates:
Status: Fixed
Comment #6 on issue 1993 by pkx1...@gmail.com: Updates to bagpipe.ly
http://code.google.com/p/lilypond/issues/detail?id=1993
Pushed to dev\staging as
5da569aedb8a0bfa8e622d7ab8d04a3adbd8be40
___
bug-lilypond mailing li
Updates:
Status: Started
Owner: mts...@gmail.com
Comment #3 on issue 2005 by pkx1...@gmail.com: scripts move unnecessarily
away from accidentals
http://code.google.com/p/lilypond/issues/detail?id=2005
(No comment was entered for this change.)
Updates:
Labels: Patch-new
Comment #2 on issue 2005 by mts...@gmail.com: scripts move unnecessarily
away from accidentals
http://code.google.com/p/lilypond/issues/detail?id=2005#c2
Fixes issue 2005 (too much script padding between certain scripts and
accidental)
http://codereview.
Comment #3 on issue 1236 by adam.spi...@gmail.com: CG+scripts should use
$LILYPOND_GIT
http://code.google.com/p/lilypond/issues/detail?id=1236
For a shell script such as doc-section.sh, auto-detection is as simple as:
cd "`dirname $0`"
cd ../..
LILYPOND_GIT="`pwd`"
Obviously auto-detection
Updates:
Status: Started
Owner: mts...@gmail.com
Comment #16 on issue 1986 by pkx1...@gmail.com: Patch: Fixes slope errors
from incorrect X extents in Beam::print.
http://code.google.com/p/lilypond/issues/detail?id=1986
(No comment was entered for this change.)
_
Updates:
Owner: mts...@gmail.com
Comment #4 on issue 2000 by pkx1...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000
(No comment was entered for this change.)
___
bug-lilypo
Comment #3 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c3
Fixes NoteColumn vs SpanBar collisions.
http://codereview.appspot.com/5323062
___
bug-lilypond
Comment #15 on issue 1986 by mts...@gmail.com: Patch: Fixes slope errors
from incorrect X extents in Beam::print.
http://code.google.com/p/lilypond/issues/detail?id=1986#c15
Fixes slope errors from incorrect X extents in Beam::print.
http://codereview.appspot.com/5293060
__
Comment #14 on issue 1986 by mts...@gmail.com: Patch: Fixes slope errors
from incorrect X extents in Beam::print.
http://code.google.com/p/lilypond/issues/detail?id=1986#c14
Fixes slope errors from incorrect X extents in Beam::print.
http://codereview.appspot.com/5293060
__
Comment #4 on issue 1954 by d...@gnu.org: request: filter point-and-click
creation by events
http://code.google.com/p/lilypond/issues/detail?id=1954
lilyp...@googlecode.com writes:
Ask them to do
sudo apt-get build-dep lilypond
for you.
___
bug
Comment #3 on issue 1954 by gra...@percival-music.ca: request: filter
point-and-click creation by events
http://code.google.com/p/lilypond/issues/detail?id=1954
awesomeness. I'm slowly getting some lab computers set up to compile
lilypond (it's slow because I don't have root, so whenever I
32 matches
Mail list logo
