chord and chordChanges

2019-05-09 Thread Gianmaria Lari
Following code prints chord even if they don't change. \version "2.21.0" << \new Staff { c'4 d' e' f' \repeat volta 2 {c' d' e' f' | g' a' b' c''} } \new ChordNames { g1 \repeat volta 2 {g1|1} } >> To avoid to print chords always, I used \set chordChanges = ##t. but I w

Re: chord and chordChanges

2019-05-09 Thread David Kastrup
Gianmaria Lari writes: > Following code prints chord even if they don't change. > > \version "2.21.0" > << > \new Staff { > c'4 d' e' f' > \repeat volta 2 {c' d' e' f' | g' a' b' c''} > } > \new ChordNames { > g1 \repeat volta 2 {g1|1} > } >>> > > To avoid to print chords al

Re: chord and chordChanges

2019-05-09 Thread Gianmaria Lari
> > > \version "2.21.0" > << > \new Staff { > c'4 d' e' f' > \repeat volta 2 {c' d' e' f' | g' a' b' c''} > } > \new ChordNames \with { chordChanges = ##t } { > g1 \once \unset chordChanges \repeat volta 2 {g1|1} > } > >> > Thank you David, this is what I wanted! In the mean

Re: Moving a Clef bellow notes in other Staff to save horizontal space?

2019-05-09 Thread Stefano Troncaro
Lol, that's what I get for dealing with this stuff before going to sleep. I realized of my mistake after turning off the computer and laughed at the situation. I never doubted that someone would point out my stupidity. El jue., 9 may. 2019 a las 2:52, David Kastrup () escribió: > Stefano Troncaro

Re: chord and chordChanges

2019-05-09 Thread David Kastrup
Gianmaria Lari writes: >> >> >> \version "2.21.0" >> << >> \new Staff { >> c'4 d' e' f' >> \repeat volta 2 {c' d' e' f' | g' a' b' c''} >> } >> \new ChordNames \with { chordChanges = ##t } { >> g1 \once \unset chordChanges \repeat volta 2 {g1|1} >> } >> >> >> > > Thank you D

Re: chord and chordChanges

2019-05-09 Thread Gianmaria Lari
On Thu, 9 May 2019 at 14:18, David Kastrup wrote: > Gianmaria Lari writes: > > >> > >> > >> \version "2.21.0" > >> << > >> \new Staff { > >> c'4 d' e' f' > >> \repeat volta 2 {c' d' e' f' | g' a' b' c''} > >> } > >> \new ChordNames \with { chordChanges = ##t } { > >> g1 \once

Hiding cautionary clef

2019-05-09 Thread Orm Finnendahl
Hi, is there a straightforward way to remove a cautionary clef at the end of a line when the clef changes between the current and the next line while keeping it at the beginning of the next line? I tried different settings for break-visibility and \omit but that either removes the Clefs alltoget

Vertical spacing of numeric time signature

2019-05-09 Thread mskala
Is there any simple way to modify the vertical spacing between numerator and denominator in a numeric time signature? -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes. https://ansuz.sooke.bc.ca/ ___ lilypond-user mailing l

Re: Vertical spacing of numeric time signature

2019-05-09 Thread Malte Meyn
Am 09.05.19 um 16:53 schrieb msk...@ansuz.sooke.bc.ca: Is there any simple way to modify the vertical spacing between numerator and denominator in a numeric time signature? Not really simple. But it can be done by redefining the stencil: \version "2.21.0" #(define (fraction-with-gap gap)

Re: Vertical spacing of numeric time signature

2019-05-09 Thread mskala
On Thu, 9 May 2019, Malte Meyn wrote: > Am 09.05.19 um 16:53 schrieb msk...@ansuz.sooke.bc.ca: > > Is there any simple way to modify the vertical spacing between numerator > > and denominator in a numeric time signature? > > > > Not really simple. But it can be done by redefining the stencil: Than

fixed vs relative

2019-05-09 Thread Gianmaria Lari
I saw the discussion about fixed vs relative few times in the lilypond ml. I think it's a lot about personal taste and habit and personally I decided to stick to fixed mainly because I find fixing mistakes in relative mode is much more annoying than writing in fixed way But what if the editor

Re: Hiding cautionary clef

2019-05-09 Thread Aaron Hill
On 2019-05-09 6:37 am, Orm Finnendahl wrote: Hi, is there a straightforward way to remove a cautionary clef at the end of a line when the clef changes between the current and the next line while keeping it at the beginning of the next line? I tried different settings for break-visibility and \

Re: fixed vs relative

2019-05-09 Thread David Kastrup
Gianmaria Lari writes: > I saw the discussion about fixed vs relative few times in the lilypond ml. > > I think it's a lot about personal taste and habit and personally I decided > to stick to fixed mainly because I find fixing mistakes in relative mode is > much more annoying than writing in fix

Re: fixed vs relative

2019-05-09 Thread Urs Liska
Am 9. Mai 2019 20:20:36 MESZ schrieb David Kastrup : >Gianmaria Lari writes: > >> I saw the discussion about fixed vs relative few times in the >lilypond ml. >> >> I think it's a lot about personal taste and habit and personally I >decided >> to stick to fixed mainly because I find fixing mista

Re: fixed vs relative

2019-05-09 Thread Gianmaria Lari
On Thu, 9 May 2019 at 20:20, David Kastrup wrote: > Gianmaria Lari writes: > > > I saw the discussion about fixed vs relative few times in the lilypond > ml. > > > > I think it's a lot about personal taste and habit and personally I > decided > > to stick to fixed mainly because I find fixing mi

Re: fixed vs relative

2019-05-09 Thread David Wright
On Thu 09 May 2019 at 20:20:36 (+0200), David Kastrup wrote: > Gianmaria Lari writes: > > > I saw the discussion about fixed vs relative few times in the lilypond ml. > > > > I think it's a lot about personal taste and habit and personally I decided > > to stick to fixed mainly because I find fix

Re: fixed vs relative

2019-05-09 Thread David Kastrup
David Wright writes: > one note has a dramatic effect on the following music, but is easily > corrected with one tick. When this trick has been applied, many notes > may have to be individually tickled after the mistake is discovered. I was of the opinion that Frescobaldi can transpose regions.

Re: fixed vs relative

2019-05-09 Thread Gianmaria Lari
On Thu, 9 May 2019 at 21:32, David Wright wrote: > On Thu 09 May 2019 at 20:20:36 (+0200), David Kastrup wrote: > > Gianmaria Lari writes: > > > > > I saw the discussion about fixed vs relative few times in the lilypond > ml. > > > > > > I think it's a lot about personal taste and habit and pers

Re: fixed vs relative

2019-05-09 Thread Urs Liska
Am 9. Mai 2019 21:52:49 MESZ schrieb David Kastrup : >David Wright writes: > >> one note has a dramatic effect on the following music, but is easily >> corrected with one tick. When this trick has been applied, many notes >> may have to be individually tickled after the mistake is discovered. >

Re: fixed vs relative

2019-05-09 Thread Urs Liska
Am 9. Mai 2019 21:40:30 MESZ schrieb Gianmaria Lari : >On Thu, 9 May 2019 at 21:32, David Wright >wrote: > >> On Thu 09 May 2019 at 20:20:36 (+0200), David Kastrup wrote: >> > Gianmaria Lari writes: >> > >> > > I saw the discussion about fixed vs relative few times in the >lilypond >> ml. >> >

Re: Finetuning TextSpanner beginning and end positions?

2019-05-09 Thread Thomas Morley
Hi Stefano, Am Mi., 8. Mai 2019 um 05:16 Uhr schrieb Stefano Troncaro : > my workflow in these scenarios is to go to the description of the object > which is giving me trouble, see what interfaces and properties it has, and > from there work out what I need to do. This is also what the Lilypond

Re: fixed vs relative

2019-05-09 Thread David Wright
On Thu 09 May 2019 at 21:40:30 (+0200), Gianmaria Lari wrote: > On Thu, 9 May 2019 at 21:32, David Wright wrote: > > > On Thu 09 May 2019 at 20:20:36 (+0200), David Kastrup wrote: > > > Gianmaria Lari writes: > > > > > > > I saw the discussion about fixed vs relative few times in the lilypond >

python3-ly WAS Re: fixed vs relative

2019-05-09 Thread Andrew Bernard
HI David, Well I am delighted utterly. I can't use Frescobaldi anymore as the program takes minutes to position the cursor in my complex scores, due to issues that have been discussed on detail on the lists. So I switched to gvim (principally because the emacs lilypond mode is buggy and the indent

python3-ly reformat in vim

2019-05-09 Thread Andrew Bernard
For those who use vim, I'm posting this as result of my discovery of python3-ly reformat thanks to David Wright in the hope that others may find it useful. This is for Debian or Ubuntu, and assumes the Python package python3-ly is installed. Add this code to ~/.vimrc: " lilypond reformat (acb) "

Re: python3-ly reformat in vim

2019-05-09 Thread Werner LEMBERG
> [...] Note that, as with all code tidying programs, you can only > return the cursor to approximately the same position, as lines may > be added of deleted. Are you sure about that? In Emacs, I can set a marker property that `sticks' to a given character. As long as this character is not de

Re: python3-ly reformat in vim

2019-05-09 Thread Andrew Bernard
Hi Werner, Interesting. I'll have some investigation. But close enough is good enough for me. In the majority of cases in my work, no lines are added or deleted, so I end up back very close. Thanks! Andrew On Fri, 10 May 2019 at 15:32, Werner LEMBERG wrote: > > > [...] Note that, as with al

Re: fixed vs relative

2019-05-09 Thread Urs Liska
Am 10.05.19 um 02:46 schrieb David Wright: You know that Frescobaldi can convert absolute to relative and vice versa? As can the ly standalone (derived from F~ possibly). Sorry I don't understand. ly, packaged as python3-ly in Debian, has a number of commands hived off (I assume) fro

Re: python3-ly reformat in vim

2019-05-09 Thread Martin Tarenskeen
On Fri, 10 May 2019, Andrew Bernard wrote: Add this code to ~/.vimrc: " lilypond reformat (acb) " reformat buffer, and return cursor to about the same place. fun DoLilypondReformat()     let l = line(".")     let c = col(".")     :%!ly reformat     call cursor(l, c) endfun au Filetype lilypo

Re: python3-ly reformat in vim

2019-05-09 Thread Andrew Bernard
Hi Martin, That's probably from pasting into email. Andrew On Fri, 10 May 2019 at 16:27, Martin Tarenskeen wrote: > > > On Fri, 10 May 2019, Andrew Bernard wrote: > > > Add this code to ~/.vimrc: > > > > " lilypond reformat (acb) > > " reformat buffer, and return cursor to about the same plac