Comment #1 on issue 1753 by carl.d.s...@gmail.com: Ehancement: tab for
diatonic instruments
http://code.google.com/p/lilypond/issues/detail?id=1753
A workaround can be made by using fretLabel together with
fret-letter-tablature-format:
notes = \relative c'' {
d4\1 e\1 fis\1 g\1
a4\1
Updates:
Status: Verified
Comment #7 on issue 1508 by colinpkc...@gmail.com: Key signature wrong with
cued music
http://code.google.com/p/lilypond/issues/detail?id=1508
(No comment was entered for this change.)
___
bug-lilypond mailing lis
Comment #6 on issue 1508 by colinpkc...@gmail.com: Key signature wrong with
cued music
http://code.google.com/p/lilypond/issues/detail?id=1508
Verified 2.15.3
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinf
Updates:
Status: Verified
Comment #8 on issue 1666 by colinpkc...@gmail.com: Docs problem:
fretted-string-harmonics-in-tablature snippet
http://code.google.com/p/lilypond/issues/detail?id=1666
(No comment was entered for this change.)
___
On 11-07-08 04:51 PM, Janek Warchoł wrote:
W dniu 8 lipca 2011 14:40 użytkownik Carl Sorensen napisał:
On 7/8/11 1:51 AM, "Janek Warchoł" wrote:
Hi Blake,
unfortunately the only thing we can do now is to add this to our issue
tracker.
Dear Bugsquad, should this be added as a comment to
http
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1753 by colinpkc...@gmail.com: Ehancement: tab for diatonic
instruments
http://code.google.com/p/lilypond/issues/detail?id=1753
2011/6/17 Blake Thornton :
> Has anyone done anything with Lilypond for tab for diatonic
Updates:
Labels: -fixed_2_14_2 backport
Comment #4 on issue 1748 by carl.d.s...@gmail.com: Defect in glissando
handling
http://code.google.com/p/lilypond/issues/detail?id=1748
Unfortunately, I couldn't get a clean make after cherry-picking this
patch. So it's not backported.
__
Status: Started
Owner: lemniska...@gmail.com
Labels: Type-Enhancement Priority-Medium Patch-review
New issue 1752 by lemniska...@gmail.com: redesigning G clef in our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
changing shape of the G clef
makes upper loop smaller,
bottom c
Updates:
Labels: fixed_2_14_2
Comment #4 on issue 1712 by carl.d.s...@gmail.com: Braces redesigned
http://code.google.com/p/lilypond/issues/detail?id=1712
Backported
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mai
Updates:
Labels: fixed_2_14_2
Comment #3 on issue 1748 by carl.d.s...@gmail.com: Defect in glissando
handling
http://code.google.com/p/lilypond/issues/detail?id=1748
Backported
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lis
Updates:
Labels: -backport fixed_2_15_4
Comment #4 on issue 1733 by carl.d.s...@gmail.com: \displayLilyMusic
ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
Backported
___
bug-lilypond mailing list
bug-lilypond@gnu.o
Updates:
Labels: fixed_2_14_2
Comment #16 on issue 1701 by carl.d.s...@gmail.com: default accidental
style prints too many 'extra' naturals
http://code.google.com/p/lilypond/issues/detail?id=1701
Yes, I should have added the flag.
___
bug-
W dniu 8 lipca 2011 14:40 użytkownik Carl Sorensen napisał:
> On 7/8/11 1:51 AM, "Janek Warchoł" wrote:
>
>> Hi Blake,
>>
>> unfortunately the only thing we can do now is to add this to our issue
>> tracker.
>> Dear Bugsquad, should this be added as a comment to
>> http://code.google.com/p/lilypo
2011/7/7 Dmytro O. Redchuk :
> Sorry for somewhat late reply (this message have been flagged in my mailbox
> since Mon 14 Feb 2011) -- if you consider this issue as still unresolved,
> please let me know. Thanks!
Thank you for remembering such an old e-mail!
Neil's suggestion worked for me (thanks
Status: Started
Owner: n.putt...@gmail.com
Labels: Type-Defect Priority-Medium
New issue 1751 by n.putt...@gmail.com: Most analysis brackets get incorrect
event-cause info, breaking point-and-click & \tweak
http://code.google.com/p/lilypond/issues/detail?id=1751
Since the Horizontal_bracket_e
Comment #4 on issue 1110 by nicolas@gmail.com: Wrong octave of
repetition chord with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
The doc is the spec. If it's not in the doc, then it's unspecified.
Whether a specific case should be specified can be d
Hello,
)-Original Message-
)From: Graham Percival [mailto:gra...@percival-music.ca]
)Sent: 08 July 2011 15:56
)To: James Lowe
)Cc: Urs Liska; bug-lilypond@gnu.org
)Subject: Re: Documentation suggestion: transposition resulting in triple
)accidentals
)
)On Fri, Jul 08, 2011 at 02:33:07PM +0
Updates:
Labels: backport2_14
Comment #3 on issue 1750 by pkx1...@gmail.com: Documentation suggestion:
transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
Pushed as 70a015a514dd4af9e9aa7d643f8bbcb1e58c0a70
I don't think we need an @li
Graham Percival writes:
> On Fri, Jul 08, 2011 at 03:06:27PM +, James Lowe wrote:
>>
>> Welcome back. Did you have a nice time in Italy?
>
> I'm still in bloody hot Italy. Go to google images and enter:
> padova aula magna
> I'm sitting in the corner of the room opposite the lecturn. (I
Hello
)-Original Message-
)From: Graham Percival [mailto:gra...@percival-music.ca]
)Sent: 08 July 2011 16:10
)To: James Lowe
)Cc: Urs Liska; bug-lilypond@gnu.org
)Subject: Re: Documentation suggestion: transposition resulting in triple
)accidentals
)
)On Fri, Jul 08, 2011 at 03:06:27PM +00
On Fri, Jul 08, 2011 at 03:06:27PM +, James Lowe wrote:
>
> Welcome back. Did you have a nice time in Italy?
I'm still in bloody hot Italy. Go to google images and enter:
padova aula magna
I'm sitting in the corner of the room opposite the lecturn. (I
gave my talk at that lecturn -- the s
On Fri, Jul 08, 2011 at 02:33:07PM +, James Lowe wrote:
> Hello
>
> )Therefore I'd suggest the following addition to the docs:
>
> Added as http://code.google.com/p/lilypond/issues/detail?id=1750
... the mao?
Screw the issue number, screw the patch. It's short,
to-the-point, and it's only
Comment #2 on issue 1750 by lilyli...@googlemail.com: Documentation
suggestion: transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
Sorry, please change the second line of the multiline comment to
"eseses ceses asasas feses beseses"
Hello,
)-Original Message-
)From: Graham Percival [mailto:gra...@percival-music.ca]
)Sent: 08 July 2011 15:56
)To: James Lowe
)Cc: Urs Liska; bug-lilypond@gnu.org
)Subject: Re: Documentation suggestion: transposition resulting in triple
)accidentals
)
)On Fri, Jul 08, 2011 at 02:33:07PM +0
Comment #1 on issue 1750 by lilyli...@googlemail.com: Documentation
suggestion: transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
The real-world example to this issue.
\version "2.15.3"
melody = \relative des'' {
des4 bes ges es as2. as4
Hello
)-Original Message-
)From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
)[mailto:bug-lilypond-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of Urs Liska
)Sent: 08 July 2011 14:12
)To: bug-lilypond@gnu.org
)Subject: Documentation suggestion: transposition resulting in tr
Status: Accepted
Owner:
Labels: Type-Documentation Priority-High
New issue 1750 by pkx1...@gmail.com: Documentation suggestion:
transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
--snip---
together with Janek Warchol I ran into trouble
Hello list,
together with Janek Warchol I ran into trouble transposing harmonically
complex music.
In order to transpose a piece from e flat to c sharp minor we had to
first transpose a middle section enharmonically (\transpose e fes)
because it would otherwise end up having an untolerable amo
On 7/8/11 1:51 AM, "Janek Warchoł" wrote:
> Hi Blake,
>
> unfortunately the only thing we can do now is to add this to our issue
> tracker.
> Dear Bugsquad, should this be added as a comment to
> http://code.google.com/p/lilypond/issues/detail?id=703
> or as a new issue?
> Carl, i dare to cc you
Comment #3 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
Can you guess the actual output of the following snippet?
More important: can you devise a coherent rule set where people would
Comment #1 on issue 1110 by brownian.box: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
Issue 1747 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypo
Comment #2 on issue 1110 by brownian.box: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
Issue 1747 contains a sample code with no #{ #} syntax.
___
bug-lilypond mailing lis
Updates:
Status: Verified
Mergedinto:
Comment #6 on issue 1747 by brownian.box: parallelmusic problem: q-notation
does not work in \relative
http://code.google.com/p/lilypond/issues/detail?id=1747
Verified as duplicate of Issue 1110.
_
Updates:
Status: Duplicate
Mergedinto: 1110
Comment #5 on issue 1747 by brownian.box: parallelmusic problem: q-notation
does not work in \relative
http://code.google.com/p/lilypond/issues/detail?id=1747
(No comment was entered for this change.)
__
Hi Blake,
unfortunately the only thing we can do now is to add this to our issue tracker.
Dear Bugsquad, should this be added as a comment to
http://code.google.com/p/lilypond/issues/detail?id=703
or as a new issue?
Carl, i dare to cc you because you are knowledgeable on Frets (and
also the issue
2011/7/8 Martin Tarenskeen :
>
> On Fri, 8 Jul 2011, Janek Warchoł wrote:
>> I'm not a good schemer, so i cannot fix it, but i've added it to the
>> tracker:
>> http://code.google.com/p/lilypond/issues/detail?id=1745
>>
>
> id=1745 does not seem to be related to Subject ?
oops, i pasted wrong link
On Fri 08 Jul 2011, 00:14 Nicolas Sceaux wrote:
> Le 7 juil. 2011 à 12:13, lilyp...@googlecode.com a écrit :
>
> >
> > Comment #3 on issue 1747 by brownian.box: parallelmusic problem: q-notation
> > does not work in \relative
> > http://code.google.com/p/lilypond/issues/detail?id=1747
> >
> > P
On Thu 07 Jul 2011, 17:24 Ole Vedel Villumsen wrote:
> Only I feel this information is perhaps lacking from the docs. I would have
> expected the full story to be in
> http://lilypond.org/doc/v2.14/Documentation/notation/displaying-pitches#automatic-accidentals,
> or at least a reference to it. Am
On Thu, Jul 7, 2011 at 3:19 PM, Dmytro O. Redchuk
wrote:
> Now there is 1702, "Unaesthetic beam slope", which reflects this situation, I
> believe:
> http://code.google.com/p/lilypond/issues/detail?id=1702
Yes, it's the one. I was worried it could go unaddressed in the 2.15 dev cycle.
Thanks for
39 matches
Mail list logo
