--On 23 June 2016 09:00 +0200 Simon Albrecht
wrote:
> With the current behaviour, it's impossible to discern that there
> are two different pitches to be played.
I first discovered this not from awareness of the actual fault, but
because I had an incorrect accidental in one part which didn't sho
Should we say explicitly in the doc that -I or --include option
requires absolute path(s)?
Paragraph to be modified is in Usage 1.2:
-I, --include=directory
Add directory to the search path for input files.
Multiple -I options may be given. The search will start in the
first defined dir
"Simon Albrecht" wrote in message
news:576b8928.6040...@mail.de...
On 23.06.2016 03:16, Andrew Bernard wrote:
I think the behaviour you show is normal lilypond semantics - although it
is not usually what one wants with different accidentals on the same
pitch.
I believe this is not a bug as it
Am 23.06.2016 um 09:19 schrieb Andrew Bernard:
> Fixing lilypond would presumably
> mean adopting one particular style that may not be what everybody wants.
or rather: setting *a default* that not everybody wants.
But having to override the default because it's not your preferred way
is clearly
Hi Simon,
What does Elaine Gould say about resolving this?
There are a lot of different styles to adopt when faced with this scenario,
and although the current lilypond approach is unreadable, you can fix it
according to whatever style you prefer. Fixing lilypond would presumably
mean adopting on
On 23.06.2016 03:16, Andrew Bernard wrote:
I think the behaviour you show is normal lilypond semantics - although it
is not usually what one wants with different accidentals on the same pitch.
I believe this is not a bug as it is up to the individual engraver to
resolve this according to their ow
