[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: fixed vs relative

From: David Wright
Subject: Re: fixed vs relative
Date: Thu, 9 May 2019 14:29:14 -0500
User-agent: NeoMutt/20170113 (1.7.2)

On Thu 09 May 2019 at 20:20:36 (+0200), David Kastrup wrote:
> Gianmaria Lari <address@hidden> 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 fixed way....
> >
> > But what if the editor would help a bit? What if you enter music in
> > relative mode (don't worrying to specify the octave) but your editor would
> > propose the "correct" (nearest) octave to add?
> >
> > For example suppose your cursor is immediatly after
> >
> > b'
> >
> >
> > and then you type
> >
> > c
> >
> >
> > What if the editor proposes to autocomplete with '' ?
> >
> > This is just an idea.
> You know that Frescobaldi can convert absolute to relative and vice versa?

As can the   ly   standalone (derived from F~ possibly).

But if you can coerce an editor into doing this trick, I would suggest
that absolute is a better target than fixed. Perhaps you meant that anyway.

However, there may be a downside. With relative, a wrong decision on
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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]