Kieren MacMillan writes:
> Hi Jean,
>
> As someone who has used an HP-15C as my only calculator since 1982, I
> want a POSTFIX version of Scheme, not an INFIX version! LOL
I actually prefer Lisp dialects to FORTH. A bit of lambda calculus
makes for a more structured view.
--
David Kastrup
g some chimera. The computer can no longer
easily process it, so there is little point in making something only
somewhat closer to human-readable.
--
David Kastrup
notes) is of course a different problem.
c/g could be entered as alternatively: basically anything with :
in it would continue stacking at a pitch not lower than the previous
one.
I _think_ that syntax should be workable. No warranties, though.
--
David Kastrup
with the samples
Lukas discussed.
--
David Kastrup
n 2.18.2, c1:5
> generated a c major chord; now it only generates a power chord fifth. My guess
> would be that Valentin V.'s chord name cleanup in 78225bc1b386e12dc was the
> point when this changed.
convert-ly exists.
Sounds more like issue 4614 to me.
--
David Kastrup
or the overture, as I
> had promised the player. So I went into the theatre office, borrowed
> their computer, logged on to lilybin, and generated a piccolo part
> which I handed to the player just a few minutes before the downbeat.
Hooray for sightreaders.
--
David Kastrup
a \vspace in an (implicit) \line does
not do a whole lot. It's essentially a "strut" but it does not affect
the skyline, just dimensions.
--
David Kastrup
side voice rather
> than the whole chord, so I was trying to make that more clear.
> thanks--jim
The solution to that, of course, is to just refrain from merging the
note heads.
--
David Kastrup
d}\\{ g,8._\tweak extra-offset #'(0.5 . 3) ->
dis16 a2}>>|
}
but frankly, it quite evades me why you would consider this desirable
over the default output.
--
David Kastrup
e without the immediately following item, just like
"immediately following" is not complete without "item" in this sentence.
If you write
\markup { text \with-color #red }
you'll get an error, not because of "ordering" but because \with-color
#red is an incomplete construct.
--
David Kastrup
han the 3rd movement of BWV1041 has in its 9/8. Partly
it may be the syllabic rendition, partly the simple melodic structure.
--
David Kastrup
rong. I'm just interested understanding some of
> the new conventions.
--
David Kastrup
Hans Åberg writes:
>> On 28 Jul 2022, at 22:43, Jean Abou Samra wrote:
>>
>> Also here:
>>
>> https://myrealbook.vintherine.org/mesures-composees.html
>
> One also write I think:
> \time #'(4 4 3) 11/8
Slightly more human-readable:
\time 4,4,3 11/8
--
David Kastrup
ted in any manner, so giving the user interface to them another
hoop does not seem to give any return to the user.
--
David Kastrup
Paul Hodges writes:
> From: David Kastrup
> There is also \startTrillSpan/\stopTrillSpan, \startGroup/\stopGroup,
> \startGraceSlur/\stopGraceSlur, \startTextSpan/\stopTextSpan,
> \startMeasureCount/\stopMeasureCount,
> \startMeasureSpanner/\stopMeasureSpanner .
>
>
Simon Albrecht writes:
> On 28/07/2022 16:25, David Kastrup wrote:
>> There is also \startTrillSpan/\stopTrillSpan, \startGroup/\stopGroup,
>> \startGraceSlur/\stopGraceSlur, \startTextSpan/\stopTextSpan,
>> \startMeasureCount/\stopMeasureCount,
>> \startMeasure
Carl Sorensen writes:
> On Thu, Jul 28, 2022 at 7:30 AM David Kastrup wrote:
>
>>
>> The current naming is a drag.
>>
>> "\repeatTie" and "\laissezvibrer" are a stupid combination of terms for
>> the two different half ties you need to de
he respective bar line.
Possibly \startSlur and \stopSlur in
order to get sensible/matching curvature.
--
David Kastrup
lready had a discussion about how to make the default
\notemode a unified note/chord mode, long long ago. Tremolo input
notation is what is the main detraction here.
--
David Kastrup
Jean Abou Samra writes:
> Le 25 juil. 2022 à 14:51, David Kastrup a écrit :
>>
>> syntax-rules/syntax-case introduce a completely new and arbitrary syntax
>> intended to be human-readable. That's sort of a counterthesis to the
>> LISP philosophy of repres
t list. What did I get
> wrong? Is it just me or should that be made more predictable, if
> possible?
You probably meant
\markup spanish = \markup \italic \etc
which defines a markup command. The way you wrote it, \spanish is just
a scheme function that happens to return the internals of a markup
command definition.
--
David Kastrup
l tweak. More complex, indeed, is the quasiquote mechanism
that operates to a good degree in the LISP reader and makes it
comparatively easy to handle the creation of material suitable as macro
body.
In contrast to syntax-rules/syntax-case this reflects more a philosophy
rather than a religion since it isn't arbitrary. Using it is more a
matter of understanding rather than learning it.
--
David Kastrup
c/v2.22/Documentation/extending/lilypond-code-blocks>
--
David Kastrup
y, Emacs Info makes it rather easy to find something like this
in the index by "URL" or "link". I'll readily agree that "inserting"
would not have been where I'd have thought looking in a printed (or
HTML) index.
--
David Kastrup
LilyPond ... \italic {
music notation for everyone
}
}
}
--
David Kastrup
from your answer this hasn't been implemented.
Well, that's more or less what
#(begin
...
)
does.
--
David Kastrup
Jean Abou Samra writes:
> Le 20/07/2022 à 14:57, David Kastrup a écrit :
>> The rule was used for converting all the old stuff in the repo, so it
>> wasn't broken at one point of time. This would suggest either a Python
>> update effect or some editing. Or for some reason
Thomas Morley writes:
> Am Mi., 20. Juli 2022 um 14:29 Uhr schrieb David Kastrup :
>>
>> David Kastrup writes:
>>
>> > Jean Abou Samra writes:
>> >
>> >> Le 20/07/2022 à 05:57, David F. a écrit :
>> >>> In 2.23, the rest markup
David Kastrup writes:
> Jean Abou Samra writes:
>
>> Le 20/07/2022 à 05:57, David F. a écrit :
>>> In 2.23, the rest markup command changed from taking a string to taking a
>>> duration.
>>>
>>> \version "2.22"
>>>
date
> input files automatically.
>
> Well, in this case there is no convert-ly rule ... I'll fix that soon.
I was "what?!?!?" about this but then the convert-ly rule I did was for
\note in a quite earlier version. It's probably reasonably easy to just
copy and adapt that rule.
--
David Kastrup
elease the next stable version anyway.
What was the news regarding this issue on the current stable
(!#$#%!$%$#%!$) 3.0 release of Guile? What were the roadblockers there?
Anybody who has had enough involvement here to give a quick refresher?
--
David Kastrup
stly with reaping the drawbacks because the benefits
require more rewriting of LilyPond.
Yes, getting the debugging into saner shape would appear important.
--
David Kastrup
ll example showing the
problem. The above is not useful and most certainly does not show
anything related to the actual problem.
--
David Kastrup
Jean Abou Samra writes:
> Le 18/07/2022 à 00:59, David Kastrup a écrit :
>> Harm is not a C programmer either. Scheme is his only language and he
>> learnt it because of LilyPond. So he has no exposure to the low-level
>> nature of C++, nor to the basics of imperative
Jean Abou Samra writes:
> Le 18/07/2022 à 00:44, David Kastrup a écrit :
>> Jean Abou Samra writes:
>>
>> [Harm:]
>>
>> You are aware that you are not talking to a C++ programmer? Not exactly
>> a motivating message under the circumstances...
ro"
and
\tempo "Allegro" 4 = 90
are valid commands.
--
David Kastrup
atch?
>From 7e4ff15a40158db8fc065623fbb0f0549ba75f0c Mon Sep 17 00:00:00 2001
From: David Kastrup
Date: Mon, 18 Jul 2022 00:38:54 +0200
Subject: [PATCH] Include "dead" in name of grobs without reflection
Nothing to do with (undead) vampires: reflection means containing a
type desc
the volume
> in the event so you could implement a function used like
>
> subPP = \dynamic #0.5 \markup { sub. \dynamic pp }
Agreed. Incidentally, my approach doesn't care just how the MIDI volume
is derived and would continue to work even after such a change of
implementation.
--
David Kastrup
David Kastrup writes:
> Jean Abou Samra writes:
>
>> Le 17/07/2022 à 10:11, Benjamin Tordoff a écrit :
>>> Hi all,
>>>
>>> I'm typesetting a score that uses "subito p" and "subito pp" in a couple of
>>> places. I've found snip
#(ly:grob-property g 'text) }
#}))
#fun #})
subPP = \subx \pp
\score {
{
c'8\\< d'8 e'8 f'8 g'8 a'8 b'8 c''8 |
c''8\f b'8 a'8 g'8 f'8\subPP e'8 d'8 c'8 }
\layout { }
\midi { }
}
Note that I put in some effort to stop "sub." from changing the
alignment. If that's undesired, removing
\with-dimension #'(0 . 0) #'(0 . 0)
should do the trick.
--
David Kastrup
g a new
> context, but in my case all I want is a tweaked version of a current
> context.
\layout {
\context {
\Staff
\name "myStaff"
< lots of lines of definition >
}
\inherit-acceptability myStaff Staff
}
--
David Kastrup
Paolo Prete writes:
>> On Sunday, July 10, 2022, David Kastrup wrote:
>>
>>> Jean Abou Samra writes:
>>>
>>> > Le 10/07/2022 à 17:38, Paolo Prete a écrit :
>>> >> I just used -dno-print-pages as an alternative, and it works.
>>
@item null
Do not output a printed score. This has the same effect as
@code{-dno-print-pages}.
--
David Kastrup
h to have the second invocation find it still existent.
And the answer appears to be that the Auto_beam_engraver keeps it alive
for some reason: if you write { a'8\noBeam \stopStaff } instead of
{ a'8 \stopStaff } as the body of the first ossia Staff, it gets
detached from the second ossia staff just like in your second example.
Whether this constitutes a bug, I am not really sure. It definitely
constitutes a curiosity.
--
David Kastrup
st for an alternative.
It would probably be better if the default resolution was in direction
of the new syntax, but I don't think that this is trivial.
--
David Kastrup
Y-offset #0.25
> -\tweak X-offset #1.5
> ^\markup "text" }
If the only variable here is "text", you may use
mtw =
-\tweak outside-staff-priority #'()
-\tweak whiteout ##t
-\tweak Y-offset #0.25
-\tweak X-offset #1.5
^ \etc
{
c\mtw "text"
}
--
David Kastrup
↳ 190: simple_music
↳ 40: embedded_scm_bare
↳ 201: event_chord
↳ 23: SCM_IDENTIFIER
↳ 408: tempo_event
↳ 174:
"\\tempo" text •
Which actually does not look all that different from your analysis.
--
David Kastrup
David Kastrup writes:
> Jean Abou Samra writes:
>
>> Le 27/06/2022 à 20:10, Simon Albrecht a écrit :
>>> Hello everyone,
>>>
>>> I’m trying to encode a piece such that I can switch whether or not
>>> durations will be shifted (note values
>>
a possible following `=`
LilyPond has to have made a decision what type the token/expression
coming before that has. It cannot look at the type of a #... expression
before deciding to look for `=` but it can (and will) look at the type
of a $... expression.
Now syntax errors are comparatively unhelpful, so one could try to
tentatively accept an #... = ... expression anyway and then barf if the
expression type does not support it. The result would likely not be
worse for the user.
--
David Kastrup
e recent upgrade to 2.22.
Does anybody remember the rationale why the snippets don't contain
\version statements?
--
David Kastrup
David Kastrup writes:
> Stephan Schöll writes:
>
>> Hi all
>>
>> How can I force a hyphen in a word to be printed as in the example with
>> the word "washed-out":
>>
>> \version "2.20.0"
>>
>> \score {
>>
n unconditional, you
could try something like
\version "2.20.0"
hy =
\tweak minimum-length #0
\tweak minimum-distance #1
\etc
\score {
<<
\new Staff {
\new Voice = melody \relative c'{
d4 d d r
}
}
\new Lyrics \lyricsto "melody" {
% washed-out dreams
\lyricmode { Washed \hy -- out dreams }
}
>>
}
--
David Kastrup
can also be started as a daemon.
You'll need to either start fluidsynth as a daemon to have it provide
MIDI devices, or install the timidity-daemon package (which does the
same but using timidity). I don't think Ubuntu has some package that
would run fluidsynth as a daemon.
--
David Kastrup
orted, which it isn't. Text replacements are purely
string-to-string at the moment. Logically that should not be required
since the replacements happen in the course of creating a stencil from a
string in ly:text-interface::interpret-string which has all the
information it needs to also properly interpret markups.
But it would make for quite trickier code paths.
--
David Kastrup
ows in that respect are, however, much more specific to
Rosegarden than they are to LilyPond.
So you haven't really missed anything that isn't also missed by a whole
lot of other people.
--
David Kastrup
the ensuing
discussion.
There's been some corners of LilyPond where I've been able to make
progress in that respect. The backend certainly is not one of them.
--
David Kastrup
arkup { aht }
> }
I have problems believing we did not have this particular discussion
already since there is a documented setting for it.
{
\override TextScript.staff-padding = #1.5
g'1^\markup { agt }
g'1^\markup { aht }
}
--
David Kastrup
David Kastrup writes:
> Jean Abou Samra writes:
>
>> Le 10/06/2022 à 23:37, Carl Sorensen a écrit :
>>>
>>>
>>> On Fri, Jun 10, 2022 at 2:23 PM Jean Abou Samra
>>> wrote:
>>>
>>>
>>>
>>>
>>> Th
r simple ...
Presumably the solution would be to provide a reliable interface for
selecting chord name language not intermingled with the input language
setting.
--
David Kastrup
Paul Hodges writes:
> From: Paul Hodges
>
> From: David Kastrup
> Try deleting
>
> C:/Program Files/lilypond-2.23.6/lib/guile/2.2/ccache/ice-9/eval.go
>
> which sounds like an outdated compilation cache (though I have no idea
> why).
>
> That
gt; value less than the full value of the note beginning the hairpin.
>
> \version "2.23.9"
> { % default output
> \after 2 \! c'2\> 4 4 |
> %desired output
> 2\> 4\hide\p 4 |
> %alternatively, this works:
> \after 4. \! 2\> 4 4 |
> }
Slightly weird: c'2\> \grace { s4\! } 4 4 |
--
David Kastrup
go
which sounds like an outdated compilation cache (though I have no idea
why).
--
David Kastrup
n any
meaning from a slur.
--
David Kastrup
of resetRelativeOctave appears to be
2.9.8.
You probably were thinking about a different problem.
--
David Kastrup
Thomas Morley writes:
> Am So., 5. Juni 2022 um 17:32 Uhr schrieb David Kastrup :
>
>> Alternatively it may make sense to work through the "Learning Manual" of
>> LilyPond once (or at least its first chapters) to get a first grasp of
>> how things are supposed
through the "Learning Manual" of
LilyPond once (or at least its first chapters) to get a first grasp of
how things are supposed to fit together.
--
David Kastrup
bly want a straight
slur, gotten with `(` and `)`. A beam is a straight line substituting
for flags on a note stem and connecting several notes of length 1/8 or
shorter.
--
David Kastrup
l noteheads at the same pitch) and slurs (which indicate a smooth
connection of notes of typically different pitch).
--
David Kastrup
ecome
non-overlapping by decree.
There are two different commands since there are syntactically identical
cases that warrant different resolution depending on the purpose of
commands one may assemble from either version.
--
David Kastrup
ot how
most people are doing this, so the discussion may be more limited in
application than it appears at first sight.
And for music-timed lyrics, one has to admit that the idea is tempting
that you'll only ever need to enter the lyrics for the Latin Common Mass
once and then not touch them ever again, regardless of composition.
Though optimistic.
--
David Kastrup
csto skip-of-length would not do anything useful in
the lyrics.
--
David Kastrup
first
> clef.
So much for my uneducated guess. Sorry for the confusion.
--
David Kastrup
ot;lilypond/77/lily-fe6a65cd.png" alt="[image of music]"]
Please make sure that you use the ‘\grace’ command for the spacer
part, even if the visual part uses ‘\acciaccatura’ or ‘\appoggiatura’
because otherwise an ugly slur fragment will be printed, connecting the
invisible grace note with the following note.
--
David Kastrup
or: bad grob property path (wonderful color)
}
In general, tweaks that have some chance to be applied to lyrics may
become awkward with \propertyTweak .
--
David Kastrup
ttempt where I just thought I'd
shrink stuff (which did not work).
So while the technique for diddling with a stencil is programmed in a
straightforward manner, I have no clue about the underlying core action.
--
David Kastrup
"John Schlomann" writes:
> Thank you, Jean. I'm not sure where I got tripped up. Perhaps I need a
> brain transplant.
I hear that the Wizard of Oz does things like that.
--
David Kastrup
n it and
then I put some \bold bold in there as well and filled it up with a lot
of nonsense words so that one can see it wraps. }
That seems pretty straightforward to me. Can you show an example of
what you tried to do instead?
--
David Kastrup
}
>>
}
}
>>
[image src="lilypond/96/lily-c52c7f83.png" alt="[image of music]"]
It's not a half-bracket but it's the closest in the manual I can find at
a glance.
--
David Kastrup
David Kastrup writes:
> Ralph Palmer writes:
>
>> Greetings -
>>
>> I appreciate the work everyone on this list does to help others.
>>
>> I'm trying to insert a paragraph of text below a score. I thought I used to
>> be able to do that, but when
ere are no
actual spaces in there? Like, your text editor made every space
unbreakable by using Unicode code point 0A0h instead of 20h ?
Do you have a more relevant example of your problem?
--
David Kastrup
ly: I believe there’s no point in
> cluttering performers’ parts with fingerings (ever) or bowing
> directions (almost ever). ;)
It's a matter of efficiency for sections expected to sightread large
parts of their material to work with performance-ready information even
if it results from arbitrary choices.
--
David Kastrup
the
latter, there seems little point in giving the conductor the information
necessary to enforce the editor's rather than the composer's vision of
execution.
--
David Kastrup
revert to
var = ##{ 4 #}
when you really really want a duration in those contexts.
In short: this seems like a can of worms that is hard to open without
the tab tearing off.
--
David Kastrup
David Kastrup writes:
> Lukas-Fabian Moser writes:
>
>> meaning: A scale? can be
>> - a fraction?
>> - an non-negative exact rational number
>> - a LilyPond moment whose main part is in turn a scale?.
>>
>> This is fulfilled by 4, hence in your c
after this, compilation fails
> completely).
>
> I'm not sure about David Kastrup's rationale for allowing a scale? as
> an afterGraceFraction, but if anybody is aware about the implications
> his changes might have for LilyPond's syntax, it's him.
> https://gitlab.com/lilypond/lil
o old X RIGHT)))
\etc
{ 1 \breathe | }
{ 1 \breathe \squashed Staff.Clef \clef alto | }
--
David Kastrup
bs out with
python/convertrules.py:stderr_write(_("If independent mark sequences
are desired, use multiple Mark_tracking_translators."))
which is a bit disappointing for functionality that is rather commonly
used. I see no documentation apart from the Changes entry that would
address this change in interface. I think fixing at least the
documentation situation would be critical before a stable release.
--
David Kastrup
\new Staff { f'1 \tweak X-offset #-5 \pp }
>>
\new StaffGroup \with \dynamicLengthOff <<
\new Staff { f'1 }
\new Staff { f'1 \tweak X-offset #-5 \pp }
>>
However, this will also stop the dynamics from avoiding interstaff
barlines, the reason for this setting. The setting is already different
in ChoirStaff which does not have interstaff barlines.
--
David Kastrup
noise in the list to direct
administrative requests to it.
--
David Kastrup
_CTYPE="en_US.UTF-8"
LC_NUMERIC=POSIX
LC_TIME=de_DE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=
and has few localisation problems. Other settings, however, may exhibit
more problems under some circumstances. Particularly non-US settings of
LC_NUMERIC can mess up number formatting (like when generating
PostScript) and localised settings of LC_CTYPE are what tends to mess
with file name recognition and other console communication.
--
David Kastrup
above. Is that possible?
Not easily. What would you do if it's on a different page?
--
David Kastrup
Jonas Hahnfeld via LilyPond user discussion
writes:
> On Tue, 2022-05-17 at 23:28 +0200, David Kastrup wrote:
>> Jonas Hahnfeld via LilyPond user discussion
>> writes:
>>
>> > On Tue, 2022-05-17 at 09:57 +0200, Jean Abou Samra wrote:
>> > >
editing other than
backspacing (and deleting) previously entered content is possible.
While of course it is important to try different variations of commands
without typing them all over (particularly when typos may be involved),
not even being able to correct a typo before hitting RET is a real
nuisance.
--
David Kastrup
Jean Abou Samra writes:
> Le 19/05/2022 à 00:56, David Kastrup a écrit :
>> Jean Abou Samra writes:
>>
>>> Le 18/05/2022 à 23:58, Jean Abou Samra a écrit :
>>>> (say)
>>>> \overrideMidBrokenSpanner Context.Grob.property = ...
>>&g
hat_ information column-dependent as well in some manner. So
it's not clear that this leads to something wonderful.
--
David Kastrup
How expensive would that be? Frankly, I am
fuzzy about either. Could it be used as a basis for something like
line-break dependent accident rules?
Could it provide a more user-accessible way of doing things than
\alterBroken ?
--
David Kastrup
ddlyrics { \verse }
pianoPart = \new PianoStaff <<
\new Staff = "right" \right
\new Staff = "left" { \clef bass \left }
>>
\score {
<<
\sopranoVoicePart
\pianoPart
>>
}
--
David Kastrup
ssible to fudge a version of readline into the precompiled
binaries after the fact.
Yes, it is an additional nuisance for building. I think the strategic
value of it would offset that.
--
David Kastrup
ce
level, though, for similar reasons).
Another such setting is InstrumentName which a number of contexts
explicitly erase in order not to inherit it from a possibly surrounding
named StaffGroup. It's not as much a matter of right/wrong but of most
convenience and/or predictability.
--
David Kastrup
t has no effect.
> Maybe there's a good reason for this, but maybe not: engraver-init.ly
> deserves some cleanup anyway (I did a bit of this in a local branch
> which I never got around to polishing).
I certainly hope you don't plan on a "cleanup" by relocating default
settings to the innermost level where they behave least predictably to
the user.
--
David Kastrup
301 - 400 of 7459 matches
Mail list logo
