Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-10-10 Thread lilypond
Updates: Status: Verified Comment #15 on issue 389 by v.villenave: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org h

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-09-19 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_34 Comment #14 on issue 389 by percival.music.ca: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 pushed as f8fd9c211e9ab17859841aa9ec98af731ab253c3 ___ bug-li

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-09-19 Thread lilypond
Comment #13 on issue 389 by percival.music.ca: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 ok, I've discovered that the LSR export is perfectly fine; it's just snippets in D/s/n/ and many of the translate texidoc strings. I've got an auto-backslash-escape

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-09-14 Thread lilypond
Updates: Status: Started Owner: percival.music.ca Comment #12 on issue 389 by percival.music.ca: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 aha, you're right! gperc...@futoi:~/src/lilypond/Documentation/snippets/new$ grep "@code{[a-z]"

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-09-14 Thread lilypond
Comment #11 on issue 389 by n.puttock: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 Hah, so it is. Silly me. :) What about snippets/new though? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-09-14 Thread lilypond
Comment #10 on issue 389 by percival.music.ca: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 Well, that's in the regtests, not the LSR->git import function. I think that's a separate issue, which I'll fix right now. ___

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-09-14 Thread lilypond
Comment #9 on issue 389 by n.puttock: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 If it can still happen, then I wouldn't class it as fixed. tablature-tremolo.ly: "Tremolos will appear on tablature staffs only if abFullNotation is active." ___

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-09-06 Thread lilypond
Comment #7 on issue 389 by n.puttock: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 Since nobody has mentioned any \t chars again, I'll make this verified. I doubt anybody's mentioned it since (AFAICT) any characters which need escaping in snippets are pro

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #6 on issue 389 by percival.music.ca: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 Since nobody has mentioned any \t chars again, I'll make this verified. ___ bug-lilypond

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-08-19 Thread lilypond
Updates: Status: Invalid Comment #5 on issue 389 by percival.music.ca: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 I can't see any \t characters in Documentation/snippets/ . Also, we've had many changes in LSR since 2007. I think this was fixed s

Re: Issue 389 in lilypond: \t -> tab in LSR snippets

2010-01-03 Thread lilypond
Updates: Owner: --- Labels: -Type-Defect Type-Build Comment #4 on issue 389 by percival.music.ca: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 (No comment was entered for this change.) -- You received this message because you are listed in the

Issue 389 in lilypond: \t -> tab in LSR snippets

2009-06-30 Thread codesite-noreply
Updates: Labels: -devel-help Maintainability Comment #3 on issue 389 by gpermus: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of th

Issue 389 in lilypond: \t -> tab in LSR snippets

2009-06-15 Thread codesite-noreply
Updates: Labels: devel-help Comment #2 on issue 389 by gpermus: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or beca

Issue 389 in lilypond: \t -> tab in LSR snippets

2007-08-17 Thread codesite-noreply
Issue 389: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 Comment #1 by hanwenn: LilyPond will interpret \t in the input as tab. These need to be escaped when generating the texidoc strings. Issue attribute updates: Summary: \t -> tab in LSR snippets

Issue 389 in lilypond: \t -> tab in LSR snippets

2007-07-03 Thread codesite-noreply
Issue 389: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 New issue report by gpermus: input/lsr/other/using* doesn't happen in the manual texinfo, but apparently something's different about the collated-files texinfo. (devel team: I'm handling this bug) Issu