[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Inconsistent crescendo endings (and kate weirdness)
From: |
Wol |
Subject: |
Inconsistent crescendo endings (and kate weirdness) |
Date: |
Mon, 26 Aug 2024 22:46:34 +0100 |
User-agent: |
Mozilla Thunderbird |
I've got a little mwe, but my crescendo endings seem a little random. On
line 1, the crescendo ends on the bar line, but the \! is on the g flat.
On line 2, the \! is on the g, and the crescendo ends on the g as I
would expect. Any ideas why?
It's almost as if lilypond is randomly deciding that \! is or is not a
dynamic marking, and therefore that the crescendo should not or should
end actually on the note to which it is attached.
On that slightly different kate note, it may be obvious that kate is my
preferred editor on linux, but when I'm typing in my lilypond source,
kate is "randomly" outdenting my lines. It's obvious what's happening -
when I type " -> " for a staccato, or end a " {} " pair, it recognises
as ">" as part of a closing ">>", or "}" as a close, and thinks it
should outdent. Except why would you outdent for staccato? Why would you
outdent for decrescendo? Why would you outdent for finishing enclosing a
bit of text.
I might be able to fix this for myself, if I knew where to look, if some
kind soul could point me?
And a little caesura problem too - is that a new keyword in 2.25? Do I
need to upgrade? I'm currently using my laptop, so digging into that one
is not something I fancy doing on this computer - it's playing up.
TIA
Cheers,
Wol
mwe.ly
Description: Text Data
mwe.pdf
Description: Adobe PDF document
- Inconsistent crescendo endings (and kate weirdness),
Wol <=