Re: severe chord repetition problem

David Kastrup wrote: Actually, if q stands for "last _chord_" rather than "last note event", then removing octave indicators is not sufficient since intervening notes might have shifted the meaning. Correct, that's the remaining drawback from the notes-chord-memorization; otherwise, this one p

Re: severe chord repetition problem

Wilbert Berendsen writes: > Op maandag 07 december 2009 schreef David: > >> The editor needs to be suitably clever to have this work properly in >> \relative mode. Ok, should be sufficient to remove octave indicators >> from the first chord note, so this is probably not overly hard. > > Yes Fres

Re: severe chord repetition problem

Op maandag 07 december 2009 schreef David: > The editor needs to be suitably clever to have this work properly in > \relative mode. Ok, should be sufficient to remove octave indicators > from the first chord note, so this is probably not overly hard. Yes Frescobaldi does exactly this :-), and it

Re: severe chord repetition problem

Wilbert Berendsen writes: > Op zondag 06 december 2009 schreef David: > >> That, in turn, means that the more brainpower is invested in Lilypond to >> make it do "the right thing", the harder it gets for Lilypond-reading >> programs to get it right as well. > > I second this. My program Frescobal

Re: severe chord repetition problem

Op zondag 06 december 2009 schreef David: > That, in turn, means that the more brainpower is invested in Lilypond to > make it do "the right thing", the harder it gets for Lilypond-reading > programs to get it right as well. I second this. My program Frescobaldi has a LilyPond parser that can un

Re: severe chord repetition problem

Alexander Kobel writes: > Nicolas Sceaux wrote: >> I was also thinking about that: >> Should the chord repetition function be enabled by default, or should >> the interested user write e.g. \include "chord-repetititon-init.ly" ? >> >> The call to a memorization function for every chords does not

Re: severe chord repetition problem

Nicolas Sceaux wrote: I was also thinking about that: Should the chord repetition function be enabled by default, or should the interested user write e.g. \include "chord-repetititon-init.ly" ? The call to a memorization function for every chords does not look like a good idea wrt performances.

Re: severe chord repetition problem

Le 6 déc. 2009 à 13:09, Alexander Kobel a écrit : > I'm not sure, though, if such a policy-based version is possible via Scheme > (read: at runtime), since it seems to affect the parser. This is what I was beginning to think about. I will introduce a new customizable function for the memorizatio

Re: severe chord repetition problem

David Kastrup wrote: Nicolas Sceaux writes: Concerning chord repetition, the issues that have been raised are: - \relative mode A patch is available for review at If nobody objects I'll commit it within a few days. Maybe there should be a common strateg

Re: severe chord repetition problem

Nicolas Sceaux wrote: Le 6 déc. 2009 à 06:28, Werner LEMBERG a écrit : Concerning chord repetition, the issues that have been raised are: - Which elements should be copied? Restrict the memorization to note chords (like ), and exclude simple notes and rests? I was recently in a situation where

Re: severe chord repetition problem

Nicolas Sceaux writes: > Le 6 déc. 2009 à 06:28, Werner LEMBERG a écrit : > >> >> Please see #924. > > This one is fixed. > > Concerning chord repetition, the issues that have been raised are: > > - \relative mode > A patch is available for review at > If n

Re: severe chord repetition problem

Le 6 déc. 2009 à 06:28, Werner LEMBERG a écrit : > > Please see #924. This one is fixed. Concerning chord repetition, the issues that have been raised are: - \relative mode A patch is available for review at If nobody objects I'll commit it within a few d

severe chord repetition problem

Please see #924. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel