his is handled by
the Note_performer .
--
David Kastrup
f f z }
and should be perfectly equivalent.
> See
> http://lilypond.org/doc/v2.23/Documentation/notation/formatting-text.html
>
> Best,
> Jean
>
>
>
--
David Kastrup
el exists for that, it does not make
sense to export an interface.
> How can I adjust the extents at this stage to fit the dimensions of
> the stencil (even if LilyPond no longer needs and/or uses the values
> for positioning)?
Create a new stencil with different dimensions and use that.
--
David Kastrup
;
> \oneVoice
> a8. g16 g4 r8 g8 |
> \bar "|."
> }
> }
>
> \score {
> \new Staff { \melody }
> }
> %%%
WHY would you merge the B quarter-note with the B eighth-note? They are
not even in the same time-step.
--
David Kastrup
ide Score.MetronomeMark.X-offset=#10
c4
_"marc."
^"arco"
\f
c
c
c
}
--
David Kastrup
Paul Scott writes:
> On 4/7/22 15:08, David Kastrup wrote:
>> Paul Scott writes:
>>
>>> On 4/7/22 14:15, David Kastrup wrote:
>>>> Paul Scott writes:
>>>>
>>>>> On 4/7/22 13:02, David Kastrup wrote:
>>>>>> Paul
Paul Scott writes:
> On 4/7/22 14:15, David Kastrup wrote:
>> Paul Scott writes:
>>
>>> On 4/7/22 13:02, David Kastrup wrote:
>>>> Paul Scott writes:
>>>>
>>>>> Greetings,
>>>>>
>>>>> I've forgotte
Paul Scott writes:
> On 4/7/22 13:02, David Kastrup wrote:
>> Paul Scott writes:
>>
>>> Greetings,
>>>
>>> I've forgotten too much. I see the instructions for activating
>>> lilypond-mode and am not remembering enough to get it to work.
&g
Paul Scott writes:
> Greetings,
>
> I've forgotten too much. I see the instructions for activating
> lilypond-mode and am not remembering enough to get it to work.
>
> TIA for any help,
cd elisp
make
sudo make install
probably.
--
David Kastrup
Omer Katzir writes:
>> On 7 Apr 2022, at 18:03, David Kastrup wrote:
>>
>> Omer Katzir writes:
>>
>>> Using on macOS Monterey, compiled from macports
>>>
>>> Taken the snippet from
>>> https://lilypond.org/doc/v2.23/Documentati
le I don’t believe that this is common in Germany, I really would
> like to get German chords (i.e. H instead of B) with uppercase bass
> notes – as I know it from all my (German) songbooks.
Any accordion music uses uppercase for bass notes and lowercase for
chords.
--
David Kastrup
> Starting lilypond 2.22.2 [Untitled]...
There is no guarantee that future extensions of LilyPond will be
undocumented, so if you use documentation for future versions of
LilyPond (compared to the version you use), you might run into problems
occasionally.
--
David Kastrup
t one has to wonder
what they need the Wayback Archive for.
--
David Kastrup
t 31, 2019.
<https://github.com/MutopiaProject/MutopiaProject>
The last activity of Chris Sawer on GitHub overall was in 2020. His
Twitter account at https://twitter.com/cjsawer however appears still
active.
Maybe try contacting him via GitHub?
--
David Kastrup
Kenneth Wolcott writes:
> Hi;
>
> I'm obviously missing something trivially simple.
>
> I see how to display dynamics above the staff, but I do not see how
> to display hairpins above the staff.
Same way?
{
c'1^\< c'1\!
}
works just fine here.
--
David Kastrup
citly cranking out stuff with thin individual
user-convenience layers on top. We don't have the equivalence of
document classes, and no coherent system of what amounts to LaTeX's
package system.
--
David Kastrup
eady delegates the typesetting until after the
whole input file has been parsed.
--
David Kastrup
n up by more waste in programming"
is a universal phenomenon.
--
David Kastrup
ror log off sequentially these days
rather than just restarting compilation after fixing a limited set of
problems.
--
David Kastrup
Jean Abou Samra writes:
> Le 27/03/2022 à 16:23, David Kastrup a écrit :
>> It doesn't share the same music objects for different notes since $(...)
>> makes a ly:music-deep-copy anyway that will deduplicate the elements of
>> SequentialMusic while copying them. The in
intermediate expression is
indeed not fit for every use, but the final deep copy fixes that.
--
David Kastrup
the syntax changed?
>
> This example works completely fine for me (on Linux). Where are you
> testing this, on Linux, macOS, or Windows?
This is very likely also quite locale-dependent.
--
David Kastrup
mes apparently try to
tell LilyPond how the notes are to be _printed_ rather than how they are
to _sound_.
This is not how LilyPond's pitch entry works. Please read the Learning
Manual section about pitches in
<https://lilypond.org/doc/v2.22/Documentation/learning/pitches-and-key-signatures#warni
o write bes ~ bes here. You might want to read
the LilyPond tutorial: it is intended to be comparatively compact
sequential reading introducing the main LilyPond concepts and get you
started.
--
David Kastrup
st beat moments other than 4 or possibly 8. Which means that
you have to juggle with \scaleDurations and its ilk when generating
MIDI.
If we don't get to see actual compilable code and/or the generated MIDI
files, I doubt we will be able to help him.
--
David Kastrup
not really on-board with the
same regarding \partial/\pickup : the overlap in semantics is different
in character.
--
David Kastrup
Wols Lists writes:
> On 19/03/2022 20:01, David Kastrup wrote:
>> Sam Roberts writes:
>>
>>> I tried so hard to be accurate, but I missed something:
>>>
>>> On Sat, Mar 19, 2022 at 12:38 PM Sam Roberts wrote:
>>>> After experimentation,
be issued whenever a user applies the older syntax;
> this would inform the user of the impending breaking change while
> still allowing existing code to compile. When it is convenient, a
> future release would only support music as the argument.
4. _is_ valid music.
--
David Kastrup
nce_ a full bar but how long it is _to_ a full bar.
As such, you'd usually see
... \time 3/4 \partial 4 c4 | ...
in typical contexts.
--
David Kastrup
ities, but not really fundamentally defining
what they actually are, and if you have need for both, their utterly
different naming and manual location essentially doubles the search work
to figure out how to use them.
--
David Kastrup
measure. What am I missing?
>
> Or is there a better way to obtain what I want?
\override MultiMeasureRest.usable-duration-logs = #'(0)
--
David Kastrup
default)
(let ((scale (magstep (- 2
(ly:duration-log
(ly:event-property
(event-cause grob) 'duration))
(ly:stencil-scale default scale scale)
\relative c' {
\temporary \override NoteHead.stencil = #resized-stencil
c1 | c2 d4 e8 f16 g32 a64 b128 c
}
--
David Kastrup
))
("violin" . (0.2 . 1.0))
("viola" . (0.1 . 0.7))
("cello" . (0.2 . 0.8))
("contrabass" . (0.2 . 0.8))
)
I don't know what MIDI-expander those values were intended for, to be honest.
--
David Kastrup
ure to line up with the
> half notes.
Maybe something like this?
\new Voice = "main"
{
\key d \major
fis8 g b e'
fis g b b'~ |
4.
8
\voices 1,"main"
<< { a' a' g' fis'~ | 4. } \\
{ \voiceTwo 2 \oneVoice }
>>
}
--
David Kastrup
wo } >>
\new Staff << { \lh_one } \\ { \lh_two } >>
>>
>>
\layout {}
}
\score {
\unfoldRepeats {
<<
\new Staff {
\set Staff.midiInstrument = "trumpet"
\trumpet
}
\new Staff {
\set Staff.midiInstrument = "acoustic grand"
<< { \rh_one } \\ { \rh_two } >>
}
\new Staff {
\set Staff.midiInstrument = "acoustic grand"
<< { \lh_one } \\ { \lh_two } >>
}
>>
}
\midi {}
}
--
David Kastrup
th { instrumentName = ... } ...
in order to have instrumentName exist from the beginning of the
context's life-time rather than from its first beat (which may be later
in the case of grace notes).
--
David Kastrup
is also very insecure
> by now. If you cannot, the only solution I can imagine
> will be to run an outdated version of LilyPond like 2.18.
Well, wouldn't it be reasonable then if our download page ceased
declaring Windows 2000 and Windows XP as supported by our installers?
--
David Kastrup
this task.
Though it can be the first step of getting it there.
--
David Kastrup
"TeXGyre Schola"
#:factor (/ staff-height pt 20)
))
top-margin = 2 \cm
left-margin = 2 \cm
bottom-margin = 2\cm
right-margin = 2\cm
}
and yes, that's a stupid interface for achieving that purpose.
--
David Kastrup
xt {
> \Staff
>\RemoveEmptyStaves
> }
> }
> \midi { }
> }
> Please point to my stupid errors.
> thanks
> J
File: lilypond-internals.info, Node: PianoStaff, Next: RhythmicStaff, Prev:
PetrucciVoice, Up: Contexts
2.1.24 ‘PianoStaff’
---
Just like ‘GrandStaff’, but the staves are only removed together, never
separately.
--
David Kastrup
tiple installed versions of LilyPond.
--
David Kastrup
vement2_part2 \movement3_part2 }
I find that a pretty bad idea since changes in \movement1_part1 can
shift the octave of movement2_part1 around. I think it makes more sense
to do octave shifts via \transpose rather than tieing the internals of
one passage to the next passage at a completely different place in the
source.
--
David Kastrup
Jean Abou Samra writes:
>> Le 09/02/2022 14:43, David Kastrup a écrit :
>>
>> > Though this might not be considered very clean.
>> The word "atrocity" readily suggests itself.
>>
>> I don't think I have thought of using #{ ... \etc #} as k
before and/or connecting this to
toplevel-music-functions now that the functions in there don't need a
"parser" argument anymore. So that is a quite appealing piece of code,
just that one would wanted to see its power applied for good.
--
David Kastrup
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
her
awkward, making something like shelf{}full omit the ff ligature only
somewhat reliably: if there is a hyphenation pass over the paragraph in
question, TeX will create the ff ligature in the "reconstitution pass".
> Thus my "no" means to say that there is in fact not such a direct way
> to adjust letter spacing in Lilypond.
--
David Kastrup
it will get removed), and \hspace can
take flexible glue specifications. And I am not sure but \kern may be
transparent to hyphenation.
LilyPond's \hspace takes no flexible glue specifications and cannot
become a breakpoint either, and hyphenation is not a thing. So I have
no idea what your "No." is supposed to mean.
--
David Kastrup
Francesco Napoleoni writes:
> In data lunedì 7 febbraio 2022 21:40:05 CET, David Kastrup ha scritto:
>> Have you tried negative \hspace ?
>
> Yes, that’s what Valentin suggested, and indeed it does the trick.
So how would you characterise this being any different from \kern ?
--
David Kastrup
Francesco Napoleoni writes:
> Thanks to all for your answers. The trick suggested by Valentin works for me.
>
> Anyway it looks like there’s no option to directly adjust letter spacing,
> something like \kern macro in LaTeX, right?
Have you tried negative \hspace ?
--
David Kastrup
ons property of the a~ in
the chord.
Members of 'articulations are broadcast from non-chord notes
(from which they are then removed) iff there is a listener for them,
otherwise they just stay put on the broadcast notes.
Members of 'articulations from chord notes are never broadcast. They
always stay on the notes.
--
David Kastrup
been similar with either the mailing
list servers and/or the mail transport server itself for gnu.org.
--
David Kastrup
]
>
> (my emphasis)
>
> So it's not going to work, because you can't "call" it.
> It just inserts the contents of the file at that point.
The point of calling \include was between #{ ... #} and nothing in there
inherently gets "called". But you cannot place assignments in there.
--
David Kastrup
ion. That will apparently be easier
than to prove viability to me.
--
David Kastrup
ing like
>
> fileA = \include "fileA.ly"
> \fileA.score
>
> or something, whatever.
Indeed, whatever all over.
--
David Kastrup
s, actions that have
immediate consequences _while_ still reading ahead.
--
David Kastrup
tponing assignment.
Since you removed every single bit of context, it's not even possible to
say anymore what you want to be talking about.
--
David Kastrup
d make using stuff in a different file much
> more clean than the current include method.
That's not possible because things like assignments aren't structure but
action, and the subsequent interpretation of the file may well depend on
those assignments being executed.
--
David Kastrup
uot;2.23.3"
>
> includeFunction = #(define-void-function (filename) (string?)
> #{ \include #filename #} )
>
> \include "includetest.ily"
>
> % \includeFunction "includetest.ily"
>
> \score { \music }
>
>
--
David Kastrup
e should in most mail
readers set up a message that, if sent, will unsubscribe the sending
mailing address from the list.
--
David Kastrup
eping.
I'll take a look, hopefully not affecting too many scores.
--
David Kastrup
David Kastrup writes:
> Simon Albrecht writes:
>
>> Dear list,
>>
>> I have encountered some unexpected behaviour with tags and
>> tagGroups. In the following example, I thought the two staffs should
>> look the same, even without the \remo
and b belong to different tag
groups: that would point to even my expectations being more in line with
yours than with what the implementation does.
--
David Kastrup
ositions to apply them to?
I just have problems figuring out the rationale behind that constraint.
--
David Kastrup
, I would not think of paying them for the additional effort
taken by hobbling themselves in that manner.
--
David Kastrup
output with the new score.
What version control system are you using for your score? It will
probably easiest to look at the source code diffs and do a manual
summary from those.
--
David Kastrup
kup ...), respectively, in scheme.
>
>
> Yes, and not only make-CMD-markup, but more importantly
> CMD-markup
CMD-markup-function
> which is the function into which your definition gets turned into, in
> charge of doing the markup interpretation.
--
David Kastrup
as f gets printed as c .
\transpose f c' means what you write as f gets printed as c' .
> 2) Is VLC GM compatible.
VLC does not play MIDI. You probably have some plugin active that
diverts to another synth. Pretty much all of them, given suitable sound
fonts, are GM2 compatible since we are talking about a standard more
than 20 years old.
--
David Kastrup
ative c'' {
% not strictly necessary, but a good reminder
\transposition c'
\key c \major
g4( c8) r c r c4
}
\new Staff = "clarinet" \with {
instrumentName = \markup { Cl (B\flat) }
midiInstrument = "clarinet"
}
\relative c'' {
\transposition bes
\key d \major
a4( d8) r d r d4
}
>>
--
David Kastrup
Alasdair McAndrew writes:
>> On Thursday 13 January 2022 01:02:17 (+11:00), David Kastrup wrote:
>>
>>> Emacs' LilyPond-mode is an abomination in desperate need of
>>> maintenance or possibly rewriting from scratch. There is no reason
>>> to use it unl
Paul Scott writes:
> On 1/12/22 11:59, David Kastrup wrote:
>> Paul Scott writes:
>>
>>> On 1/12/22 11:00, David Kastrup wrote:
>>>> Paul Scott writes:
>>>>
>>>>> On 1/12/22 08:33, David Kastrup wrote:
>>>
Paul Scott writes:
> On 1/12/22 11:00, David Kastrup wrote:
>> Paul Scott writes:
>>
>>> On 1/12/22 08:33, David Kastrup wrote:
> (snip)
>>> Even with the infrequent alignment problem I am quite happy with
>>> lilypond-mode.
>> Well, I use i
Paul Scott writes:
> On 1/12/22 08:33, David Kastrup wrote:
>> Paul Scott writes:
>>
>>>> On 1/12/22 07:02, David Kastrup wrote:
>>>>> Alasdair McAndrew writes:
>>>>>
>>>>> Emacs' LilyPond-mode is an abomination i
to bring them all and in the darkness bind them.
--
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
gt;> horizontal alignment was something handled by the system not the
>> programmer. Though I do concede this was probably a novelty, seeing
>> as
>> these days terminals and editors still rely on fixed pitch.
>>
>> [1]: http://www.literateprogramming.com/knuthweb.pdf
>>
>>
>> -- Aaron Hill
--
David Kastrup
r r 4. 8 }
where the 4. is sucked into the second r likely unintentionally.
Highlighting this is helpful. When there is a general "angry fruit
salad" flavor pervading the highlighting with lots of colors everywhere,
there just is not a lot of attention one can draw to actually important
things.
--
David Kastrup
haphazard, being neither
systematically related to the actual category of the tokens nor to their
function in user input.
There does not appear to be a coherent payback for the inherent lowering
of readability (and printability) from the lower contrast of colored
passages.
What is the information you want to convey better?
--
David Kastrup
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
; Thanks,
> Kieren.
Sort of butt-ugly:
\version "2.21"
\layout {
\context { \Score
\override Script.stencil =
#(grob-transformer 'stencil
(lambda (grob default)
(and (not (string=?
(ly:event-property (event-cause grob)'articulation-type)
"fermata"))
default)))
}
}
{ c''1^\fermata_\espressivo }
--
David Kastrup
(seems like a Lisp rather than
Scheme idea to me) but shouldn't be used by users for stuff not formally
fitting the predicate.
In my handwavy impression of trying to sort-of guess unwritten coding
conventions.
--
David Kastrup
Valentin Petzel writes:
> Hello Jean, hello David, hello Kieren,
>
> you should even be able to write (if sten (ly:stencil-extent sten)),
> as the stencil should always be a stencil or #f.
The return value will still be neither #f nor a dimension unless you
replace "if"
(let* ((xex (ly:stencil-extent sten X))
> (width (interval-length xex)))
> (max -2 (* -0.5 (max 0 (- width 2
> }
> }
> }
>
Your "if" has no else path. Maybe replace it with "and", assuming that
ChordName knows how to deal with an X-offset of #f (which tends to be a
valid setting for any predicate in grob properties).
--
David Kastrup
position 1 (expecting Stencil): #f
>
> Any thoughts about what might be going wrong?
It is applied to a grob that has been given the \omit treatment?
--
David Kastrup
rs will automatically figure out just by repeatedly
hearing in essence "no, that's wrong". You will need to more actively
participate in defining what will and what will not be a manner of
arriving at a page layout that you deem acceptable.
--
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
Paolo Prete writes:
> Hello,
>
> on the very first page of a score, is there a way to place a string at the
> bottom (minus the bottom margin), possibly without using the footer markup?
Isn't that more or less what the copyright header field is for?
--
David Kastrup
bers (because my titling is based on
> bookpart-page-number).
>
> Thanks,
> Kieren.
>
>
--
David Kastrup
ve a dim view towards this approach,
too. Just want to mention this, recently having disassembled a
Laserjet2300DTN in order to replace decomposed solenoid padding with
felt pads so that it's good for longer runs of double-sided printing
again. It's actually a nice music printer, doing black double-sided
printing on a remarkably margin-less area. And the network interface
makes it pretty fast, too.
--
David Kastrup
p pass collecting loose pieces in
sequential expressions but it does not come in time for assembling the
arguments of music functions.
> In fact, the warning applies to 2.19.83, but not to 2.20, which
> surprises me (as I had thought that commits to 2.20 were a subset of
> those to 2.19.83.)
--
David Kastrup
Aaron Hill writes:
> On 2021-12-12 3:19 pm, David Kastrup wrote:
>> and one could instead define it as
>> make-dynamic-script =
>> #(define-event-function (str) (ly:markup?)
>>(make-music 'AbsoluteDynamicEvent 'text str))
>
> Did you mean just markup? or
)
(make-music 'AbsoluteDynamicEvent
'text str))
and one could instead define it as
make-dynamic-script =
#(define-event-function (str) (ly:markup?)
(make-music 'AbsoluteDynamicEvent 'text str))
which would retain the old functionality while also providing
\make-dynamic-script
which of course does not follow naming conventions. Sigh. At any rate,
it should be defined using define-event-function rather than
define-music-function .
--
David Kastrup
rser-include-string "\\include \"oll-core/internal/init.ily\"")))
This will include oll-core/internal/init.ily if it hasn't yet been
loaded, and that will likely be responsible for messing with the
language.
In short, what you quoted likely doesn't contain the culprit.
--
David Kastrup
the bass clef at the end of the first line here:
[code]
>
> Dear David,
> thanks for Your reply.
> Can it also be done with \once \override?
a) why not ask LilyPond instead of me?
b) why would you want to have an inconsistent style of changing clefs in
your music?
--
David Kastrup
{
>\column {
> \fromproperty #'header:piece
> \justify-field #'header:instruction
>}
> }
> }
Well, \justify-field just takes a string, like \justify-string does.
Maybe it should check for markup lists and pass them through \justify .
--
David Kastrup
401 - 500 of 7439 matches
Mail list logo
