Updates:
Status: Verified
Comment #9 on issue 1971 by colinpkc...@gmail.com: Slashed flags no longer
work
http://code.google.com/p/lilypond/issues/detail?id=1971
Verified per Phil's instructions.
___
bug-lilypond mailing list
bug-lilypond@
Updates:
Labels: -Patch-new Fixed_2_15_21
Comment #8 on issue 1971 by philehol...@gmail.com: Slashed flags no longer
work
http://code.google.com/p/lilypond/issues/detail?id=1971
Fixed with cf93b1df71253b2686ceabacdf49a47e6908da64. To verify - go to the
NR, section 1.2.6 and scroll
Updates:
Labels: Patch-new
Comment #7 on issue 1971 by philehol...@gmail.com: Slashed flags no longer
work
http://code.google.com/p/lilypond/issues/detail?id=1971#c7
Update LSR and fix Issue 1971
Fixes Issue 1971
http://codereview.appspot.com/5436073
__
On 11-10-29 11:27 AM, lilyp...@googlecode.com wrote:
Comment #6 on issue 1971 by pkx1...@gmail.com: Slashed flags no longer
work
http://code.google.com/p/lilypond/issues/detail?id=1971
I've checked the snippet in ../new/.. and it looks fine.
So I don't know what happened during the makelsr.p
Comment #6 on issue 1971 by pkx1...@gmail.com: Slashed flags no longer work
http://code.google.com/p/lilypond/issues/detail?id=1971
I've checked the snippet in ../new/.. and it looks fine.
So I don't know what happened during the makelsr.py that Mike did.
Can I just delete the snippet in ../sn
Comment #5 on issue 1971 by pkx1...@gmail.com: Slashed flags no longer work
http://code.google.com/p/lilypond/issues/detail?id=1971
Ah OK I think I understand the issue now.
I think it's because there is a misplaced '%' comment.
The example in the snippet 'using-grace-note-slashes-with-normal-
Comment #4 on issue 1971 by colinpkc...@gmail.com: Slashed flags no longer
work
http://code.google.com/p/lilypond/issues/detail?id=1971
The code in the original report doesn't give slashed stems with 2.15.16 d/l
today, however changing Stem to Flag works properly. Also, the code is in
the
Comment #3 on issue 1971 by pkx1...@gmail.com: Slashed flags no longer work
http://code.google.com/p/lilypond/issues/detail?id=1971
Well I think we should verify this 'commit' and have a new tracker
for 'Doc' stuff. This keeps the trackers explicit. It also encourages devs
to fix stuff witho
Comment #2 on issue 1971 by philehol...@gmail.com: Slashed flags no longer
work
http://code.google.com/p/lilypond/issues/detail?id=1971
I'm not verifying this because I don't think the docs are quite right yet.
The snippet in the docs at
http://lilypond.org/doc/v2.15/Documentation/notati
On Oct 17, 2011, at 1:12 PM, m...@apollinemike.com wrote:
> On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
>
>> On 17 October 2011 11:41, Graham Percival wrote:
>>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
On 17 Oct 2011 07:56, "Peekay Ex" wrote:
> However
On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
> On 17 October 2011 11:41, Graham Percival wrote:
>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
However, and this is for Phil: could we not simply 'deprecate' the
sni
On Oct 17, 2011, at 12:49 PM, Neil Puttock wrote:
> On 17 October 2011 11:41, Graham Percival wrote:
>> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
However, and this is for Phil: could we not simply 'deprecate' the
sni
On 17 October 2011 11:41, Graham Percival wrote:
> On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>
>> > However, and this is for Phil: could we not simply 'deprecate' the
>> > snippet(s) like we do with any that won't work (properly) in
On Mon, Oct 17, 2011 at 08:22:54AM +0200, m...@apollinemike.com wrote:
> I think that there is an issue with file-touchability. Certain snippets in
> the docs are not editable,
Not editable by hand, you mean. convert-ly is still fine.
> and the convert-ly rules don't know how to handle this in
On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>
> > However, and this is for Phil: could we not simply 'deprecate' the
> > snippet(s) like we do with any that won't work (properly) in later
> > versions, and actually I think it was Mike t
Updates:
Status: Fixed
Comment #1 on issue 1971 by mts...@gmail.com: Slashed flags no longer work
http://code.google.com/p/lilypond/issues/detail?id=1971
Fixed with 84fa3cb9de968a45ef1bd07e9fe96cec1f3eaf87.
___
bug-lilypond mailing list
bug-l
On Oct 17, 2011, at 9:30 AM, Peekay Ex wrote:
> Mike
>
> On Mon, Oct 17, 2011 at 8:12 AM, m...@apollinemike.com
> wrote:
>> On Oct 17, 2011, at 9:09 AM, Neil Puttock wrote:
>>
>>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>>
However, and this is for Phil: could we not simply 'deprecate'
Mike
On Mon, Oct 17, 2011 at 8:12 AM, m...@apollinemike.com
wrote:
> On Oct 17, 2011, at 9:09 AM, Neil Puttock wrote:
>
>> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>>
>>> However, and this is for Phil: could we not simply 'deprecate' the
>>> snippet(s) like we do with any that won't work (proper
On Oct 17, 2011, at 9:09 AM, Neil Puttock wrote:
> On 17 Oct 2011 07:56, "Peekay Ex" wrote:
>
>> However, and this is for Phil: could we not simply 'deprecate' the
>> snippet(s) like we do with any that won't work (properly) in later
>> versions, and actually I think it was Mike that a week or s
On 17 Oct 2011 07:56, "Peekay Ex" wrote:
> However, and this is for Phil: could we not simply 'deprecate' the
> snippet(s) like we do with any that won't work (properly) in later
> versions, and actually I think it was Mike that a week or so ago
> pointed one out to me that was deprecated as of 2
Mike, Phil,
On Mon, Oct 17, 2011 at 7:16 AM, m...@apollinemike.com
wrote:
> On Oct 16, 2011, at 12:06 PM, lilyp...@googlecode.com wrote:
>
>> Status: Accepted
>> Owner:
>> Labels: Type-Critical Regression
>>
>> New issue 1971 by philehol...@gmail.com: Slashed flags no longer work
>> http://c
On Oct 17, 2011, at 12:43 AM, Graham Percival wrote:
> On Sun, Oct 16, 2011 at 11:02:22PM +0200, m...@apollinemike.com wrote:
>>
>> I think that by running convert-ly via the script in 10.9.4,
>> duplicate Flag #'transparent statements will be issued (every
>> time convert-ly sees a Stem #'transp
On Oct 16, 2011, at 12:06 PM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Critical Regression
>
> New issue 1971 by philehol...@gmail.com: Slashed flags no longer work
> http://code.google.com/p/lilypond/issues/detail?id=1971
>
> The NR
> (http://lilypond.org/
On Sun, Oct 16, 2011 at 11:02:22PM +0200, m...@apollinemike.com wrote:
>
> I think that by running convert-ly via the script in 10.9.4,
> duplicate Flag #'transparent statements will be issued (every
> time convert-ly sees a Stem #'transparent, it adds a Flag
> #'transparent for files created befo
On Oct 16, 2011, at 10:07 PM, Graham Percival wrote:
> On Sun, Oct 16, 2011 at 12:13:27PM +0200, m...@apollinemike.com wrote:
>>
>> Is there a way to run convert-ly on the docs to eliminate this sorta problem?
>
> Yes. By some incredible coincidence, it is discussed
> in CG 10.9.4 Automatically
On Sun, Oct 16, 2011 at 12:13:27PM +0200, m...@apollinemike.com wrote:
>
> Is there a way to run convert-ly on the docs to eliminate this sorta problem?
Yes. By some incredible coincidence, it is discussed
in CG 10.9.4 Automatically update documentation
http://lilypond.org/doc/v2.15/Documentatio
On Oct 16, 2011, at 12:06 PM, lilyp...@googlecode.com wrote:
> Status: Accepted
> Owner:
> Labels: Type-Critical Regression
>
> New issue 1971 by philehol...@gmail.com: Slashed flags no longer work
> http://code.google.com/p/lilypond/issues/detail?id=1971
>
> The NR
> (http://lilypond.org/
Status: Accepted
Owner:
Labels: Type-Critical Regression
New issue 1971 by philehol...@gmail.com: Slashed flags no longer work
http://code.google.com/p/lilypond/issues/detail?id=1971
The NR
(http://lilypond.org/doc/v2.15/Documentation/notation/special-rhythmic-concerns)says:
"The slash
28 matches
Mail list logo
