Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-25 Thread Federico Bruni
Il giorno dom, 24/04/2011 alle 19.43 -0600, Carl Sorensen ha scritto: I find it simpler to just do \new TabStaff \relative c' { \chordGlissando bes\3 cis\2 fis\18 b\3 d\2 g\1 \chordGlissando bes='\3 cis\2 fis\18 b\3 d\2 g\1 } It still gets the warning, but I think it's

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-25 Thread Federico Bruni
Il giorno lun, 25/04/2011 alle 00.09 +0200, Federico Bruni ha scritto: Or should I rather edit Documentation/snippets/new/chord-glissando-in-tablature.ly? I've changed my mind and I think that I should edit this file instead of fretted-strings.itely. In the meanwhile I've realized that

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-25 Thread Carl Sorensen
On 4/25/11 11:26 AM, Federico Bruni fedel...@gmail.com wrote: Il giorno lun, 25/04/2011 alle 00.09 +0200, Federico Bruni ha scritto: Or should I rather edit Documentation/snippets/new/chord-glissando-in-tablature.ly? I've changed my mind and I think that I should edit this file instead

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-25 Thread Colin Campbell
On 11-04-25 11:33 AM, Carl Sorensen wrote: On 4/25/11 11:26 AM, Federico Brunifedel...@gmail.com wrote: Il giorno lun, 25/04/2011 alle 00.09 +0200, Federico Bruni ha scritto: Or should I rather edit Documentation/snippets/new/chord-glissando-in-tablature.ly? I've changed my mind and I

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-25 Thread m...@apollinemike.com
It appears to me right now that chordGlissando is a sufficiently rough hack that it should probably be removed from the distribution and just be present in the LSR. +1. I will have time this weekend to work on an implementation that uses a context property to control how glissandi are typeset

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-24 Thread Federico Bruni
Il giorno sab, 23/04/2011 alle 19.43 +0100, Graham Percival ha scritto: On Thu, Apr 21, 2011 at 04:52:52PM +0200, Federico Bruni wrote: I made several tries but none worked. This works: \octaveCheck c' \chordGlissando bes cis fis8 b\3 d g (full snippet attached)

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-24 Thread Carl Sorensen
On 4/24/11 4:09 PM, Federico Bruni fedel...@gmail.com wrote: I find it simpler to just do \new TabStaff \relative c' { \chordGlissando bes\3 cis\2 fis\18 b\3 d\2 g\1 \chordGlissando bes='\3 cis\2 fis\18 b\3 d\2 g\1 } It still gets the warning, but I think it's easier than the

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-23 Thread Graham Percival
On Thu, Apr 21, 2011 at 04:52:52PM +0200, Federico Bruni wrote: I made several tries but none worked. This works: \octaveCheck c' \chordGlissando bes cis fis8 b\3 d g (full snippet attached) Maybe it could be added in the Documentation (NR 2.4.1, Default tablatures)? I'd be

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-21 Thread Federico Bruni
Thanks Carl, yes, the issue is related to relative mode Il giorno gio, 21/04/2011 alle 07.13 -0600, Carl Sorensen ha scritto: put an octave check on the second chord. That should solve the problem. g b e8 a='' d fis I made several tries but none worked. This works: \octaveCheck c'