On Sun, Mar 20, 2022 at 1:26 AM Christopher Heckman
wrote:
>
> On Sun, Mar 20, 2022 at 12:44 AM wrote:
> >
> > Date: Sun, 20 Mar 2022 07:23:30 + (UTC)
> > From: Werner LEMBERG
> > [...]
> > > Fair point, though the intention here would be that backwards
> > > compatibility would only need to
Am Sonntag, dem 20.03.2022 um 15:48 +0100 schrieb Jonas Hahnfeld via
Discussions on LilyPond development:
> Am Donnerstag, dem 17.03.2022 um 22:38 +0100 schrieb Jonas Hahnfeld via
> Discussions on LilyPond development:
> > Am Donnerstag, dem 17.03.2022 um 22:10 +0100 schrieb Jean Abou Samra:
> > >
High priority issues (I'd like to get these done before I begin
integrating my GSoC work):
* A glyph should be created for SMuFL's clefChangeCombining
character.
Really? Why?
I was following precedent. Bravura includes it, even though it's a
zero-width empty character.
As far as I unde
Hi Benkő,
On 3/19/22 02:00, Benkő Pál wrote:
Hi Owen,
Owen Lamb ezt írta (időpont: 2022. márc. 19., Szo, 7:38):
Hi Benkő,
On 3/17/22 10:05, Benkő Pál wrote:
re the longest rests:
1. a perfect longa rest and a maxima rest are not the same;
2. a perfect longa rest should take three spaces (li
> On Mar 20, 2022, at 2:24 AM, Werner LEMBERG wrote:
>
> What about providing a new command `\upbeat` and moving `\partial`
> into oblivion? Compare this to `\tuplet` vs. `\times`.
Perhaps this is an American jazzism, but we would refer to those as \pickup
notes.
Am Donnerstag, dem 17.03.2022 um 22:38 +0100 schrieb Jonas Hahnfeld via
Discussions on LilyPond development:
> Am Donnerstag, dem 17.03.2022 um 22:10 +0100 schrieb Jean Abou Samra:
> > > Le 17 mars 2022 à 20:35, Jonas Hahnfeld > >
> > > Now merged. And while you can continue building with Guile 1
Le 20/03/2022 à 10:01, Aaron Hill a écrit :
All of those things *are* music, as far as LilyPond is concerned. It
is just that commands like \tempo have no duration, so the following
is nonsensical since the music has zero length:
\partial \tempo 4 = 90
Your "global" variable likely uses s
Entirely replacing the actual syntax would not be desirable in my opinion.
Consider the case when it is used in a “global” part/variable in an orchestral
score that usually contains rehearsal marks, tempo, key and time signature
changes and such. As I understand it having \partial to accept only
What if instead of `\upbeat` (which is weirdly named when used in the
end-of-music/phrase/hymn/passage scenario) this new thing is just called
`\partialMusic`?
It's backward compatible, does something easy to use in some simple
scenarios, leaves everything else in place for more refined use cases,
I do not really like the idea that much to be honest. Of course it would be
cool if we just have to specify the music and no duration, but in the end
\partial is not really a command about the music, but about the measure
structure. Binding it to some music would be a bit like having \time take
On 2022-03-20 3:17 am, David Kastrup wrote:
Aaron Hill writes:
Fair point, though the intention here would be that backwards
compatibility would only need to exist for a time.
I strongly disagree since \partial with a duration is the natural and
proper expression when writing a separate timin
Aaron Hill writes:
> On 2022-03-19 7:53 pm, Dan Eble wrote:
>> On Mar 19, 2022, at 20:53, Aaron Hill wrote:
>> ...
> A convert-ly rule would probably not be possible given the
> limited power
> of regular expressions. As such, \partial might need to support
> both
> duration
But as you say "most applications". Partial or incomplete measures
are not always anacruses. Hymns nearly always cut the final measure
short so it logically joins with the partial measure at the start of
the tune. You might also find incomplete measures in volta sections
when the starting
On 2022-03-20 1:56 am, Lukas-Fabian Moser wrote:
What about providing a new command `\upbeat` and moving `\partial`
into oblivion? Compare this to `\tuplet` vs. `\times`.
Werner
... Or you could use the brand new command \upbeat when music follows,
keep \partial, and you don't have to wo
On 2022-03-20 1:13 am, Leo Correia de Verdier wrote:
Entirely replacing the actual syntax would not be desirable in my
opinion. Consider the case when it is used in a “global” part/variable
in an orchestral score that usually contains rehearsal marks, tempo,
key and time signature changes and suc
What about providing a new command `\upbeat` and moving `\partial`
into oblivion? Compare this to `\tuplet` vs. `\times`.
Werner
... Or you could use the brand new command \upbeat when music follows,
keep \partial, and you don't have to worry about backwards
compatibility.
This makes
On Sun, Mar 20, 2022 at 12:44 AM wrote:
>
> Date: Sun, 20 Mar 2022 07:23:30 + (UTC)
> From: Werner LEMBERG
> [...]
> > Fair point, though the intention here would be that backwards
> > compatibility would only need to exist for a time. A warning could
> > be issued whenever a user applies th
What if you rotate them instead?
Rename the current \partial \partialDuration,
convert.ly now is just s/partial/partialDuration/
and \partial always takes music from now on
It's the same as Werner said, but keeps the good name
L
On Sun, 20 Mar 2022, 08:24 Werner LEMBERG, wrote:
>
> > A con
> A convert-ly rule would probably not be possible given the
> limited power of regular expressions. As such, \partial might
> need to support both duration and music arguments. Initially I
> thought this might not be possible, given that a naked duration
> can be treated as
19 matches
Mail list logo
