b property path
>
> \once \override
>
> ParenthesesItem.stencils = #(lambda (grob)
>
>
> I've had this in my standard include file for quite some time. What might I
> need to change to remove the error?
You could try running convert-ly on the file to find out.
--
David Kastrup
David Kastrup writes:
> Jean Abou Samra writes:
>
>> Folks,
>>
>> I am getting tired at the number of questions of the type
>> "Why doesn't this work anymore?" which can be answered by
>> "Just Run convert-ly! (TM)". I suspect that the eff
s?
Different major number. Possibly also odd major number and different
minor number, but I guess stable releases are done frequently enough
these days that it's unlikely a distribution will package an unstable
one.
I think we should very much avoid syntax changes within an even major
number.
--
David Kastrup
Jean Abou Samra writes:
> Le 07/02/2022 à 21:18, David Kastrup a écrit :
>> The obvious thing would be to do process-music like we do
>> process-acknowledged: translators should be robust against multiple
>> calls; and whenever new events are announced to some translato
ome type will
only be consumed after no events of such type can still be produced.
Indeed, we already know which types a translator may consume (that's
what its set of listeners tells us), so we'd only need to declare what
types it may emit.
--
David Kastrup
olta 3 ...
What if you want the old repeat sign but alternatives?
--
David Kastrup
arted off.
Thanks!
--
David Kastrup
supporting documentation and/or examples of actual previous use, I
propose we scrap the whole bunch without replacement.
--
David Kastrup
's shoes sounds difficult. I
> would volunteer, but I still plan to contribute patches.
git shortlog --author Lowe
should be some indication that this is not a conflict of interest as
such. It may end up a conflict of resources.
--
David Kastrup
t; of providing modules to a version of Python it is written for.
>>
>
> Sorry, my fault. PYTHONPATH is set by my .login to the values used for
> python2.
While "python" calls python3. Does not sound like the best scheme to be
doing things.
--
David Kastrup
ould be mixed.
That does not hold water. You write "At the start of the script
PYTHONPATH is unset" so there is nothing that would mix dirs for py2 and
py3. PYTHONPATH will be empty unless some script sets it for the sake
of providing modules to a version of Python it is written for.
--
David Kastrup
/usr/bin/python3.7.
If it is a "small shell script", you should be able to post it here. It
is quite possible that it is not functionally compatible with the normal
utility regarding the interpretation of commandline options and/or will
not function perfectly when used as a #! interpreter.
--
David Kastrup
n: In a file included before `updating.texi`, you are
> missing either `@endmorerefs` or `@endpredefined`.
Or it means that @chapter sets its argument in @raggedright (possibly in
a table-of-contents diversion) and does not allow @command to be used
inside of its argument.
--
David Kastrup
Jonas Hahnfeld writes:
> Am Montag, dem 10.01.2022 um 15:57 +0100 schrieb David Kastrup:
>> Jonas Hahnfeld via Discussions on LilyPond development
>> writes:
>>
>> > Am Mittwoch, dem 15.12.2021 um 23:44 +0100 schrieb David Kastrup:
>> > > Hi,
>
Jonas Hahnfeld via Discussions on LilyPond development
writes:
> Am Mittwoch, dem 15.12.2021 um 23:44 +0100 schrieb David Kastrup:
>> Hi,
>>
>> after the "big" Linuxtag event folded, the Chemnitzer Linuxtage are the
>> largest such event in Germany, typicall
Processing `/tmp/bab.ly'
Parsing.../usr/local/share/lilypond/2.23.5/scm/lily/lily.scm:978:21: In
procedure ly:parse-file in expression (ly:parse-file file-name):
/usr/local/share/lilypond/2.23.5/scm/lily/lily.scm:978:21: Wrong type
(expecting pair): 0
And frankly, I don't see something wrong with that. Could use a better
error locator, sure. But it's not the same as a core dump.
--
David Kastrup
save the cost
> of detecting them, as it does not seem to be a code path used heavily
> at all.
Overrides of subproperties are used pretty extensively in some newer
code.
Maybe it would make sense to check where code is being used before
trying to change it?
--
David Kastrup
s search for a matching pair, it could well set the
> last cdr to add the new pair at the end.
An empty list does not have a last cdr.
--
David Kastrup
personal idea would be to use relative links anyway, but that might
possibly not work with the kind of "URL helper" setup that typically
ends up calling lilypond-invoke-editor .
--
David Kastrup
David Kastrup writes:
> For stuff like
>
>
> midiDrumPitches.ridecymbal = fis,,
> midiDrumPitches.ridecymbala = b
> midiDrumPitches.ridecymbalb = a
> midiDrumPitches.crashcymbal = g
>
>
> \midi
> {
> \context {
> \Score
> drumPitchT
is,,
midiDrumPitches.ridecymbala = b
midiDrumPitches.ridecymbalb = a
midiDrumPitches.crashcymbal = g
\midi
{
\context {
\Score
drumPitchTable = #(alist->hash-table midiDrumPitches)
}
}
you'll get across-session bleed of assignments when making them
destructive. Another option is, of course, to do what amounts to an
in-place modification of a structural copy.
--
David Kastrup
was really kept working by the efforts of
informal Ubermeister Graham and slowly decayed after his departure from
the project.
--
David Kastrup
nts, one will
likely still meet up afterwards in the virtual space at the lecture hall
and walk the usual tables looking for the usual participants, from the
space of one's private computer.
Anyone interested in promoting LilyPond there?
--
David Kastrup
ou might have mistakenly used % as a comment character in
Scheme mode (in Scheme, the comment character rather is ; ).
--
David Kastrup
ing it directly from the command line, with the "-dgui" switch
> added.
Why would you add -dgui when running from the command line?
--
David Kastrup
rwin and it's conceivable that a command line
application like LilyPond could be delivered in that manner without
involving Apple's proprietary build environments. Likely without
offering platform-specific font integration.
--
David Kastrup
Flaming Hakama by Elaine writes:
> On Mon, Nov 15, 2021 at 11:11 AM David Kastrup wrote:
>>
>> Where "convert this into a reasonable time signature" would imply the
>> ability to convert this into the two separate components, a functional
>> and a visu
a page when they are non-empty as well as a given
fraction of their content size to make it possible to account for, say,
two-column footnotes).
The page _breaker_ can then still continue being lowlevel.
--
David Kastrup
Jonas Hahnfeld writes:
> Am Donnerstag, dem 25.11.2021 um 16:18 +0100 schrieb David Kastrup:
>> > System::init_elements has
>> >
>> > set_object (this, "all-elements", scm_arr);
>> >
>> > So *all_elements_ is protected as
David Kastrup writes:
> David Kastrup writes:
>
>> David Kastrup writes:
>>
>>> Jonas Hahnfeld via Discussions on LilyPond development
>>> writes:
>>>
>>>> Am Donnerstag, dem 25.11.2021 um 08:40 +0100 schrieb Jonas Hahnfeld via
>>
David Kastrup writes:
> David Kastrup writes:
>
>> Jonas Hahnfeld via Discussions on LilyPond development
>> writes:
>>
>>> Am Donnerstag, dem 25.11.2021 um 08:40 +0100 schrieb Jonas Hahnfeld via
>>> Discussions on LilyPond development:
>>>&
David Kastrup writes:
> Jonas Hahnfeld via Discussions on LilyPond development
> writes:
>
>> Am Donnerstag, dem 25.11.2021 um 08:40 +0100 schrieb Jonas Hahnfeld via
>> Discussions on LilyPond development:
>>> Am Mittwoch, dem 24.11.2021 um 23:01 +0100 schrieb
t use it.
Note also that all_elements_ is initialised to nullptr only _after_
garbage collection has already been activated: the in-class
initialisation syntax makes it easier to gloss over initialisation order
(which is not changed).
I'll try GC-proofing System. Only time will tell whether this makes a
difference and/or whether other problems remain.
--
David Kastrup
characters or commands that should not be interpreted, such as
computer input or output ('@example' interprets its text as regular
Texinfo commands). This is especially useful for including
automatically generated files in a Texinfo manual.
--
David Kastrup
David Kastrup writes:
> I have no idea what my arrangers would display then (maybe they even are
> smart enough to fall back to the filename on their own)
Turns out they are. Problem is how to convey to Performance::output the
difference between "" and no name at all. It i
on their own) and the code
appears sort of icky regarding how to implement that behavior so it's
possible that it would entail some work without best payoff for my
particular hardware.
Though I should be easily able to test that case by hardcoding no title
at all in the MIDI and then seeing what happens when I try playing the
file.
Maybe I'll check that first.
--
David Kastrup
Aaron Hill writes:
> On 2021-11-19 11:28 am, David Kastrup wrote:
>> What are other people's feelings here? Should we allow an explicit
>> specification of the title as "" to override such a fallback?
>
> Could it work to add a midiTitle property/field to allow
mance::output as far as I can see and
a placeholder is set up in Control_track_performer::initialize .
The standard does not appear to consider this mandatory; it may require
a bit of refactoring to be able to leave it off in LilyPond.
What do people think we should be doing ideally?
--
David Kastrup
f music were only allowed to express Gould-correct
notation, we would not be having this discussion in the first place.
--
David Kastrup
r 3 times { 8 8 8 } for a different
representation of 9/8 meter.
With regard to meters, obviously there are also numeric variations like
writing 3+2 in the numerator. The amount of visual possibilities is
large enough that forcing visual and functional components to be
interchangeable seems like a bad idea.
--
David Kastrup
Aaron Hill writes:
> On 2021-11-15 3:30 am, David Kastrup wrote:
>> Not everyone picking 6/8 unambigulously wants to see this
>> interpreted as
>> 2 notes of 4. duration. So forcing a particular duration expressing a
>> length not inherently specified is putting words
Flaming Hakama by Elaine writes:
> From: David Kastrup
>> Kieren MacMillan writes:
>> > The time signature “9/8” does *not* (as you imply) actually convey
>> > *any* information about the number of “beats” — the *convention* does
>> > that.
>>
&
d has
> *never* handled time signatures correctly (where “correct” means
> “according to the accepted definition of 'time signature'”).
Nor has his ever handled durations correctly according to your
definition of "duration". Which means you should get a grip on what
LilyPond calls a duration before proposing to use it.
--
David Kastrup
Carl Sorensen writes:
> On 11/14/21, 9:33 AM, "David Kastrup" wrote:
>
> Kieren MacMillan writes:
>
> > Hi David,
> >
> >> How is that uniquely identified? Why couldn't it be
> > subscripted with 10 instead of 5?
press previously valid
semantics but also lacks the ability to distinguish between cases it is
supposed to newly be able to express, the design needs fixing rather
than a vigorous defense.
Of course pointing that out makes me the bad guy standing in the way of
progress.
--
David Kastrup
ed or
expressed, in opposition to your and Carl's statements about what
meaning the parts of a time signature are supposed to inherently have,
leading to a proposal of generally changing the current representation
by involving musical durations for the denominator.
--
David Kastrup
al times, there is.
>
> Here’s a screenshot for anyone who can’t envision the uniquely identified
> print form of 8/20 using a
> note in the denominator:
> *
How is that uniquely identified? Why couldn't it be subscripted with 10
instead of 5?
--
David Kastrup
Kieren MacMillan writes:
> Hi David,
>
>> There just is no uniquely identified print form using a note in the
>> denominator for that time signature representation.
>
> As I’ve explained several times, there is.
Give it for 8/20 then.
--
David Kastrup
t time signature representation. That makes that
representation unable to adequately reflect existing music while at the
same time being considerably more complex. You consider both the added
complexity as well as ditching the ability of others to represent
_their_ music an adequate sacrifice for gaining -- what exactly?
--
David Kastrup
Carl Sorensen writes:
> On 11/13/21, 4:05 PM, "David Kastrup" wrote:
>
> Kieren MacMillan writes:
>
> > Hi David,
> >
> >> It doesn't answer the question.
> >
> > Did my explicit answer in the other email (i.e
or
> Lilypond’s internal representation of durations to give a more
> specific or nuanced or helpful answer than that. ;)
The problem is that handwaving looks great in discussions but does not
deliver a definition useful for implementation.
--
David Kastrup
Aaron Hill writes:
> On 2021-11-13 1:22 pm, David Kastrup wrote:
>> Aaron Hill writes:
>>> David, do you know any reasons why FRACTION is a token and not a
>>> parser rule?
>> Wagonloads of lookahead?
>
> I think the only practical action is for me to
4 0 4/5) but that has no
unique printed representation different from (ly:make-duration 4), and
(ly:make-duration 4 0 4/5) and (ly:make-duration 4 0 8/10) are
absolutely indistinguishable.
--
David Kastrup
> \tuplet 5/4 { c''16 16 16 16 16 }
> }
>
> The denominator of a #'note-denom time signature would look like this:
> *
> Hope that helps!
> Kieren.
It doesn't answer the question.
--
David Kastrup
perfectly to “8 events per measure, each
> event having a duration equal to 1/20th of a whole note”.
What duration is equal to 1/20th of a whole note in LilyPond?
--
David Kastrup
Carl Sorensen writes:
> On 11/13/21, 1:09 PM, "David Kastrup" wrote:
>
> Carl Sorensen writes:
>
> > I have not been a strong contributor to this thread. And I have not
> > been a strong advocate for the time signatures with a notehead in
he parser could enable more generalized fraction-like
> constructs such as number/duration, but I am unsure the cost.
>
> David, do you know any reasons why FRACTION is a token and not a
> parser rule?
Wagonloads of lookahead?
--
David Kastrup
e that it's worth changing the
> internals since they work so well for the lilypond core functionality
> (traditional western music), but I noticed the semantic error as I
> read this thread.
What do you want to change? Entry or internals? And how so?
--
David Kastrup
t;
> Agreed.
>
> I hope nobody inferred from my lighthearted response to Aaron’s post
> that I’d *actually* want any function to literally bear my name!? =)
In which case \macMillan would be the better choice anyway.
--
David Kastrup
here a feature is not generally associated with a
particular name, it's not really helpful to use a name in that manner.
So I'd rather use something like \musicFraction or so to indicate this
kind of construct.
--
David Kastrup
t *);
lily/time-signature-engraver.cc:Time_signature_engraver::listen_time_signature
(Stream_event *ev)
lily/time-signature-performer.cc: void listen_time_signature (Stream_event *);
lily/time-signature-performer.cc:Time_signature_performer::listen_time_signature
(Stream_event *ev)
--
David Kastrup
ncluding you would likely cause the list server to
not deliver a copy to you, turning the purpose of including you in the
list of recipients on its head.
--
David Kastrup
e conclusion
that it is possible to have one work but not the other.
--
David Kastrup
y again later:
retry timeout exceeded
Reporting-MTA: dns; eggs.gnu.org
Action: failed
Final-Recipient: rfc822;kieren_macmil...@sympatico.ca
Status: 5.0.0
Remote-MTA: dns; mxmta.owm.bell.net
Diagnostic-Code: smtp; 421 Connection limit reached. Please try again later:
retry timeout exceeded
uot;) does not consult the LilyPond parser
beyond the # and there is absolutely nothing that would magically turn
"4." into a duration. Nor should there be in my book.
--
David Kastrup
t of a myriad of variants in meaning is intended makes it
reasonable for the user to see what is intended.
It's not like I haven't voiced that opinion before, so I have no idea
how I could contribute towards you considering this question resolved.
--
David Kastrup
it becomes impossible to see what the author
actually wants because there is so much overlap in how the arguments
could be interpreted, where is the advantage?
This is just "I want the computer to typeset what I mean, not what I
say". But that's not just confusing to computers.
--
David Kastrup
duration for the “denom” *without breaking existing code or
> requiring a convert-ly rule*, then that would be home run!
I have no idea what you are even imagining here because the denominator
for \time is not written as a separate number in the first place.
--
David Kastrup
ing the user enter a dotted duration in the first place if that is
what you want to see.
> 3. Is there an ly:string->duration [or similar] function, that will
> take "4." and turn it into a duration that I can use to generate the
> right glyph(s)?
Just don't use a string to start with.
--
David Kastrup
ff. It's actually architecture-level
stuff, diluting the Voice separation that turns ad-hoc polyphony (in
contrast to fixed polyphony determined by player separation or at least
instrument part separation) like that common in piano and other keyboard
music into a nuisance for typesetting with LilyPond.
--
David Kastrup
core C++ parts, he also has done quite a bit of fixing.
There are also a number of other people (like David Nalesnik) who have
contributed large pieces of magic mostly in the Scheme domain, partly as
off-the-cuff contributions to discussions on the list.
--
David Kastrup
David Kastrup writes:
> David Kastrup writes:
>
>> Dan Eble writes:
>>>
>>> Using \tuplet 1/1 instead of \volta 1 causes the same problem.
>>>
>>> Nesting the \set within <<>> or {} makes the problem go away. Does
>>> that
David Kastrup writes:
> Dan Eble writes:
>>
>> Using \tuplet 1/1 instead of \volta 1 causes the same problem.
>>
>> Nesting the \set within <<>> or {} makes the problem go away. Does
>> that serve as a work-around in your use case?
>
> There
Dan Eble writes:
>> On Nov 3, 2021, at 19:20, David Kastrup wrote:
>>
>> Dan Eble writes:
>>
>>> On Nov 3, 2021, at 18:40, David Kastrup wrote:
>>>>
>>>>
>>>> My use case is something different entirely and it does
Dan Eble writes:
> On Nov 3, 2021, at 18:40, David Kastrup wrote:
>>
>>
>> My use case is something different entirely and it does not work as
>> expected. This may or may not be a relevant minimal example for my use
>> case (no idea) but is weird
)
e'1
}
}
--
David Kastrup
DrumStaff"
> \alias "Staff"
>
> % (etc.)
>
> }
>
> That's the only instance of a context definition that contains _both_
> a parent context type (\Staff) _and_ \type "Engraver_group".
>
> Is that correct? I don't know enough about the inner workings to j
involvement are sort of given the kind of consideration that a CI script
gets.
Not that I am guilty of that here myself: the average LilyPond
developer's experience and opinion about the topic may differ from
Jean's exactly because we've seen and discussed the difference this
makes to LilyPond, but part of the reason it does of course is that
there actually are/is people/someone who care/s.
--
David Kastrup
Jean Abou Samra writes:
> Le 16/10/2021 à 13:09, David Kastrup a écrit :
>> Jean Abou Samra writes:
>>> Hi James, Werner, all,
>>>> I would say that 'most' emails to the bug list do NOT need an
>>>> issue, they are either replies to emails or pointer
really mention the list I think) but at least
gets stuff into the system (where it sometimes is left to rot without
further feedback).
That's still preferable to what you propose, but quite worse than having
an actual bug reporting list like we have now.
--
David Kastrup
entation being "executed", and source files are interpreted rather
than compiled, with no file-level representation ever being explicit.
That's not an academic difference since it is a non-trivial question
just what the structure of a MusicXML file is supposed to represent from
a given LilyPond input file.
--
David Kastrup
g some drum parts for our accordion orchestra into MIDI, and
multi-measure drum rolls become completely incoherent (or rather
completely coherent) without this. Try leaving off the performer...
--
David Kastrup
; As a reminder, this means the ability to merge
> one's patches as well as change merge request
> labels (which is useful often). Thoughts?
I'd ask him first.
--
David Kastrup
Dan Eble writes:
> I have created a grob. Later, perhaps in another timestep, I want to
> discard that grob so that it has no bearing on the final score. Is
> there a way to do that? Is there a good example? How late is too
> late, etc.?
ly:grob-suicide! ?
--
David Kastrup
David Kastrup writes:
> make info
>
> Oops, half of the images in Documentation/out-www/lilypond-changes.info
> are just [Image of music] text tags.
>
> make doc
>
> 45 minutes later:
>
> make info
>
> Still half of the images in Documentation/out-www/lil
the English version is not exactly rewarding either.
--
David Kastrup
Han-Wen Nienhuys writes:
> On Thu, Sep 30, 2021 at 12:24 AM David Kastrup wrote:
>>
>> Well, this is not as much supporting the MIDI layer as it is
>> employing the translator level for messing with music during
>> iteration. It's sort of annoying that
ons or so.
> 2. times = \repeat unfold \etc
When I was just occasionally using LilyPond, at some time when \tuplet
did not exist, I tended to be fuzzy about \time, \times, \tempo . I am
familiar enough these days that this is a mere anecdotal data point: I
have no idea how it would affect newcomers.
--
David Kastrup
John Wheeler writes:
> On 9/29/2021 3:35 PM, David Kastrup wrote:
>> John Wheeler writes:
>>
>>> Hello,
>>>
>>> Would someone please help me understand the reasoning behind removing
>>> the grammar from the Contributor's Guide? Was ther
Jean Abou Samra writes:
> Le 30/09/2021 à 00:13, David Kastrup a écrit :
>> commit a1a418468e5cf481340667d433676dc00adf00fb
>> Author: Jean Abou Samra
>> Date: Wed Sep 1 18:54:24 2021 +0200
>>
>> Markup commands for conditionals
>>
>> has
Aaron Hill writes:
> On 2021-09-29 12:39 pm, David Kastrup wrote:
>> The question is whether we should do something like this as default,
>> possibly conditioned on whether any acknowledgers are present? Because
>> even if we cannot react to Midi data structures (since t
ile:576: out/lilypond-notation.info] Error 1
make: *** [/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:6:
all] Error 2
Why does nobody else get this?
--
David Kastrup
out what music
constructs may or may not end up being valid.
So it was more of a point of "nobody uses this anyway" in connection
with "and good luck if they tried" I think.
--
David Kastrup
David Kastrup writes:
> So I tried the following
>
> Stress_performer =
> #(define-scheme-function (strong weak) (index? index?)
>(lambda (ctx)
> (define fired #f)
> (define (emit weight)
>(ly:broadcast (ly:event-source ctx)
>
opy scheme-engraver.{cc,hh} to
scheme-performer.{cc,hh}, throw out everything Engraver-specific
(basically acknowledgers and possibly the associated processing phases)
and get something pretty much the same for now.
Does anybody have a better proposal?
--
David Kastrup
en need one quote level more. Alternatively you
could call eval only when given a list or a symbol and just retain what
you got otherwise. That may lead to somewhat inconsistent behavior.
--
David Kastrup
> as a note name is already not supported.
They are perfectly fine as lyrics though. Entering the alphabet song
with durations would become a nightmare
> To me, the addition of this shorthand is worth a new element on this
> list.
R and r do not intermingle with the lexical categories of numbers.
--
David Kastrup
r layout module,
with the paper module having mm as 1 but the layout module working in
staff spaces or something like that).
--
David Kastrup
David Kastrup writes:
> Werner LEMBERG writes:
>
>> Using it with
>>
>> ```
>> #(set-default-paper-size (cons 100 50)))
>> ```
>>
>> works like a charm. However, code like
>>
>> ```
>> #(set-default-paper-size (cons (* 100
you not use it in the paper block? mm is not a constant, it
depends on the output scale.
--
David Kastrup
201 - 300 of 6030 matches
Mail list logo
