%% slur does not look at accidentals
\score {
\relative c''{
a1 a a a a
a2. g16( b d fis)
}}
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
When having a separated dynamic markings staff, using (in 3/4 measure
timing)
s2.\f
shows Forte sometimes in the beginning of the measure and sometimes in
the middle of the measure. Also, when trying to force the positioning, using
s8\f s8 s2
shows the marking the same way as before. Sometimes it
On Friday 27 August 2004 02:14, Han-Wen Nienhuys wrote:
> Because the Lilypond doesn't care what users do. It's more that we
> want to have a uniform style so our manual and examples look uniform.
> Better that we don't set Official Guidelines, rather, we could present
> our style as an option.
>
>
Graham Percival <[EMAIL PROTECTED]> writes:
> I can't think of anything to recommend other than
[snip]
sounds good to me. I think it hasn't to be in a section "official
guidelines" but could in something like "suggestions" (or whatever). You
could also put suggestions of how to deal with lily fil
On 27-Aug-04, at 1:14 AM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
The question of an "official" LilyPond style comes up every so often.
(ie something like "always begin with a \version string, then
the \headers. Violinx should be written as violinOne, violinTwo,
etc")
Because the Lilypo
If the Emacs/jedit/vim/... modes, the templates and the examples in the
documentation follow a common style, than that's probably what most
users will follow as well, without the need for any official documented
standard.
/Mats
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
The question of a
[EMAIL PROTECTED] writes:
>
> The question of an "official" LilyPond style comes up every so often.
> (ie something like "always begin with a \version string, then
> the \headers. Violinx should be written as violinOne, violinTwo, etc")
>
> I used to like the idea, but now I've moved into the "d
