Hi Mark,
Am Sa., 19. Jan. 2019 um 02:32 Uhr schrieb Mark Probert :
> However, being a newbie to this package, when I
> have a problem, or a perceived problem, I can either ask
> on this forum or not.
Nothing wrong with asking on this list.
Pretty often some weaknesses or eaven bugs become known
little off. The R1 is not really centered:
{
R1
\appoggiatura { \bar "" d''8 \bar "|" } c''4 r2.
}
That's what I remember directly, not sure whether there is more.
Cheers,
Harm
>
> Andrew
>
>
> On Sat, 19 Jan 2019 at 07:15, Thomas Morley
Am Fr., 18. Jan. 2019 um 11:01 Uhr schrieb Werner Arnhold
:
>
> Dear list,
>
> I often need to have Midi output with different volume or instruments in
> some voices. Here an example:
>
> \version "2.18.2"
>
> global = {
> \key c \major
> \time 4/4
> }
>
> soprannoten = \relative c'' {
> g e
Am Fr., 18. Jan. 2019 um 19:14 Uhr schrieb Urs Liska :
>
> Is there any convenient and semantically acceptable way of engraving an
> appoggiatura (or other grace notes) *before* the barline? I know that
> usually one is pointed to \afterGrace to achieve something like that but
> that seems
Am Mi., 16. Jan. 2019 um 00:14 Uhr schrieb David Kastrup :
>
> Lukas-Fabian Moser writes:
>
> > Hi David,
> >> \test apparently expects a string argument.
> >
> > Aaargh, sorry, stupid me, and stupid copy'n'paste error. So, another try:
> >
> > \version "2.19.82"
> >
> > test =
Well, I'm still confused what you're after...
Am So., 13. Jan. 2019 um 13:43 Uhr schrieb Gloops :
> Hello Harm!
> Sorry, I did not express myself well!
> I want to go through "Ez_numbers_engraver_harm"
> to convert NoteHead to a number and display AmbitusNoteHead directly.
> I do not want (if
Am So., 13. Jan. 2019 um 17:48 Uhr schrieb Klaus Ethgen
:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi Thomas,
>
> Am So den 13. Jan 2019 um 16:10 schrieb Thomas Morley:
> > Please enter in terminal:
> > lilypond scheme-sandbox
> >
Sending this again, because google or firefox or whatever buggy
program messed up the mail-adress
Am So., 13. Jan. 2019 um 16:10 Uhr schrieb Thomas Morley
:
>
> Am So., 13. Jan. 2019 um 15:41 Uhr schrieb Klaus Ethgen
see:
> :
> >
> > -BEGIN PGP SIGNED MESSAGE-
Am So., 13. Jan. 2019 um 15:41 Uhr schrieb Klaus Ethgen
:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi Lukas,
>
> Am So den 13. Jan 2019 um 15:01 schrieb Lukas-Fabian Moser:
> [Charset problem]
> > This is strange, because I can't reproduce the problem here. On my (Linux
> > Mint)
Am Sa., 12. Jan. 2019 um 20:44 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> > You could go for:
> >
> > #(define-markup-command (bookpart-page-number layout props) ()
> >(let ((first-page-number (ly:output-def-lookup layout
> > 'first-page-number))
> > (page-number
Am Sa., 12. Jan. 2019 um 19:37 Uhr schrieb Kieren MacMillan
:
> %%% SNIPPET BEGINS
> \version "2.19.80"
>
> #(define-markup-command (bookpart-page-number layout props) ()
> (let ((first-page-number (ly:output-def-lookup layout 'first-page-number))
> (page-number (chain-assoc-get
Am Fr., 11. Jan. 2019 um 10:04 Uhr schrieb Gloops :
>
> Hello Harm
> Thank you for this correction ...
> Is there any way to engrave the ambitus directly without going through
> "note-head :: brew-ez-stencil" in order to avoid the head of the note?
> Gilles
Not sure what you mean.
Probably, set
Am Mi., 9. Jan. 2019 um 23:38 Uhr schrieb Gloops :
>
> Thank you very much Harm, it works very well now!!!
> Musically
> Gilles
Hi Gilles,
glad you like it.
Though, here one improvement: Settings for 'font-series and
'font-family need to be done _before_ 'stencil. I.e.:
#(define
Am Do., 10. Jan. 2019 um 15:56 Uhr schrieb Andrew Bernard
:
>
> Hmm. Adding extra-spacing-width seems to work.
>
> ppecrescText = \markup {
> \normal-text \italic "pp e cresc ..."
> }
> ppecresc = \tweak DynamicText.self-alignment-X #LEFT
> \tweak DynamicText.extra-spacing-width #'(0 . -20)
>
ug. According to
> https://sourceforge.net/p/testlilyissues/issues/5179/ the second dot
> should be killed.
Fixed with
commit 0d0f3d641939843316bd199ef62de261ce89335f
Author: Thomas Morley
Date: Tue Aug 29 10:44:28 2017 +0200
Issue 5179 Let Merge_rests_engraver deal with dotted r
Am Di., 8. Jan. 2019 um 14:51 Uhr schrieb Gloops :
>
> Hello!
> Ambitus by voice and Ez_numbers_engraver can not work together?
The problem: Ez_numbers_engraver works on every grob with a
note-head-interface. NoteHeads and AmbitusNoteHead both have this.
Though, at the time this engraver works
Am Fr., 4. Jan. 2019 um 13:07 Uhr schrieb Gianmaria Lari
:
>
>
>
> On Fri, 4 Jan 2019 at 11:56, Thomas Morley wrote:
>>
>> Am Fr., 4. Jan. 2019 um 11:17 Uhr schrieb Gianmaria Lari
>> :
>> >
>> > My apologies, I didn't specify the fact that it is 3/
Am Fr., 4. Jan. 2019 um 11:56 Uhr schrieb Andrew Bernard
:
>
> I think I have asked this before in the past, but I don't recall any answers.
> I know that articulations come from the lilypond font but is there any way to
> make them bolder, or more emphatic?
>
> There's an LSR for bold tenuto,
Am Fr., 4. Jan. 2019 um 11:17 Uhr schrieb Gianmaria Lari
:
>
> My apologies, I didn't specify the fact that it is 3/4 time.
>
> Thomas solution is graphically perfect
Well, my suggestion meets the image. Actually, the composers notation
is simply wrong, strictly speaking.
I've seen it many
Am Fr., 4. Jan. 2019 um 10:20 Uhr schrieb Gianmaria Lari
:
>
> The attached image shows a measure of a accordion piece from Bogdan Precz.
>
> I tried to engrave it writing:
>
> <>
>
>
> and it looks fine except for the slur. How can I add the slur?
> Thank you, g.
I'd rather use one voice with
Am Fr., 4. Jan. 2019 um 01:20 Uhr schrieb Yakir Arbib :
> Would anyone here -- especially those of you who are composers and use
> Lily for contemporary music be willing to give me a few paid private
> lessons over Skype or What'sapp so that we can cover some of the
> features I need to get
Am Do., 3. Jan. 2019 um 11:00 Uhr schrieb Vaughan McAlley
:
>
> On Thu, 3 Jan 2019 at 20:26, Andrew Bernard wrote:
>>
>> Hi Christopher,
>>
>> I can't quite nut this one out, but you can't just have ##f sitting in the
>> open between scores - it's a bad expression. You can't place in that
>>
Am Mi., 2. Jan. 2019 um 23:21 Uhr schrieb Thomas Morley
:
> \layout {
> \override Hairpin.stencil = #flat-flared-hairpin
> \override Hairpin.details.flare-height = 2 %% default is 1
> \override Hairpin.details.flare-width = 2 %% default is 1
> \override Hairpin.thickn
Am Mi., 2. Jan. 2019 um 01:26 Uhr schrieb Andrew Bernard
:
>
> Hi Thomas,
>
> The correction works and all is good. Thanks so much.
>
> An interesting point I discovered. If you use \< for the hairpins, the LEFT,
> RIGHT settings are correct. but if you use /< they are reversed - but still
>
Am Mi., 2. Jan. 2019 um 22:41 Uhr schrieb Sam Bivens :
>
> Happy New Year to everyone reading!
>
> Please see the attached MWE; how can I specify the radius of the circled
> text? Using `\circle 2` results in differently sized circles based on
> the circled text, but when I specify the radius with
Am Di., 1. Jan. 2019 um 18:04 Uhr schrieb Christian Zollner
:
>
> Hello list!
>
> I need to write tabulatures for me and my girlfriend. I am playing
> violin and she is playing Shamisen. I am new to Lilypond but generally
> programming language affine, so I learned everything quickly up until now.
Am Di., 1. Jan. 2019 um 04:05 Uhr schrieb Andrew Bernard
:
>
> Hi Harm,
>
> I am greatly in your debt. This is really excellent, and you have picked up
> exactly what I need. Using it, I have found that when having a hairpin that
> crosses a line break (my main original question) the flare
Am Mo., 31. Dez. 2018 um 06:01 Uhr schrieb Andrew Bernard
:
>
> Line break continuation code in lilypond has always been outside my grasp and
> skill level.
Can you describe what exactly is the problem?
Maybe we can improve the Extending Manual.
Cheers,
Harm
Am Mo., 31. Dez. 2018 um 06:01 Uhr schrieb Andrew Bernard
:
>
> I need some special flat, flared ended hairpins to indicate pulsing in a
> string quartet I am setting for a friend. So far, I managed to adapt a
> textspanner to do the job. It's fiddly but OK. However, because I use a
> custom
Am Mo., 31. Dez. 2018 um 10:43 Uhr schrieb Malte Meyn :
>
>
>
> Am 31.12.18 um 09:58 schrieb Andrew Bernard:
> >
> > Why do you have to use cadr and not cdr on the ly:grob-set-property
> > line? Isn't the broken part the second item in a list of two items? How
> > to understand this?
>
> In
Am Sa., 29. Dez. 2018 um 00:58 Uhr schrieb Thomas Morley
:
>
> Am Fr., 28. Dez. 2018 um 22:28 Uhr schrieb Philip Bergwerf
> :
> >
> > When working with Lilypond I want Lilypond to print the empty measures from
> > every instrument, like how Denemo is doing by default. Fo
Am Fr., 28. Dez. 2018 um 22:28 Uhr schrieb Philip Bergwerf
:
>
> When working with Lilypond I want Lilypond to print the empty measures from
> every instrument, like how Denemo is doing by default. For example: instr. 1
> has 10 measures of music. I want lilypond to print the empty measures of all
Am Do., 27. Dez. 2018 um 21:03 Uhr schrieb MING TSANG :
> Dear Paul and David
>
> I don't know the code. Appreciate if either one of you can help to resolve
> the tie problem for jianpu.
>
Hi,
my knowledge about Jianpu is zero.
Though, how _should_ it look? Like the attached png?
If so why not
Am Di., 25. Dez. 2018 um 21:19 Uhr schrieb Jacques Menu :
>
> Hello folks,
>
> I don’t succeed in using ‘#:concat’ to compute the second argument to
> ‘#(:note’ in the following Scheme code, where HERE occurs.
>
> What should I use instead? The aim is to use half the value of ‘den’ instead
> of
Am Di., 25. Dez. 2018 um 11:35 Uhr schrieb Mario Moles
:
>
> Hi lilyponders!
>
> I need to make a transcription from italian lute tablature (Francesco
> Spinacino).
>
> It is the reverse of the lilypond tabstaff: the first string is the sixth and
> the sixth is the first.
>
> How to?
>
> Thanks
Am Fr., 21. Dez. 2018 um 17:54 Uhr schrieb Jogchum Reitsma
:
>
> Hi list,
>
> I use lilypond 2.18 on OpenSuse Tumbleweed (the rolling distro from Suse). On
> that combination, displaying chord names in .pdf-form gives error messages
> grom ghostscript (gs) in the transition from a .ps-file to a
Am Sa., 22. Dez. 2018 um 12:10 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Sa., 22. Dez. 2018 um 02:46 Uhr schrieb Ben :
> >> Did you experience the same wait times?
> >
> > It lasted ~40minutes (I didn't observed the time exactly)
> >
Am Sa., 22. Dez. 2018 um 02:46 Uhr schrieb Ben :
> What are your system specs? I can compile the file on my Linux Mint x64
> laptop with 16GB of RAM, rockin' an 8th gen i7 but it took about 10 minutes
> almost. That seems very very slow.
Well, I have a weak laptop. In the past I had some fast
Am Sa., 22. Dez. 2018 um 00:48 Uhr schrieb Reggie :
>
> I am trying to understand theoretically why this is failing. It's only 16
> pages. I am a minimalist composer so as a test I tried this extreme
> situation. But yet I don't quite agree rather that it's that extreme. It's
> only 16 pages and
Am Fr., 21. Dez. 2018 um 23:18 Uhr schrieb Reggie :
>
> Is there a way in LilyPond to simply add a beam line without changing the
> time or anything else behind the elements? I mean, visually say I had a c16
> feather beam measure that had all the math and checks OK. But I wanted 3
> lines for my
Am Fr., 21. Dez. 2018 um 19:26 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > \featherDurations changes durations, nothing more!! It does not change
> > spacing on it's own.
> > The changed spacing is more a side-effect. Doing note-spacing is a
> > very involved p
Am Fr., 21. Dez. 2018 um 20:10 Uhr schrieb Reggie :
>
> Aaron Hill wrote
> > Given the current implementation, it would be necessary to use an
> > approximate rational like 50/63 as the moment in order to get 'f' to be
> > half of 'c'. Why that number? Well, it's a close approximation to the
> >
Am Fr., 21. Dez. 2018 um 17:51 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > Meanwhile I think you didn't understand that feathered beams, done with
> > \override Beam.grow-direction = #RIGHT
> > and
> > \featherDurations
> > are _independant_ from each o
Am Fr., 21. Dez. 2018 um 17:18 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie
>
> > reegistoop@
>
> > :
> >
> >> It's impossible to have feather
> >> beams cross barlines and look
Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie :
> It's impossible to have feather
> beams cross barlines and look correect why is this?
??
What's wrong with:
\version "2.19.82"
{
r2..
\override Beam.grow-direction = #RIGHT
c'32[ \repeat unfold 6 c'' c'] r2..
}
Cheers,
Harm
Am Mo., 17. Dez. 2018 um 21:36 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Mo., 17. Dez. 2018 um 21:20 Uhr schrieb David Kastrup :
> >>
> >> Thomas Morley writes:
> >
> >> > The idea:
> >> >
> >> > #(
Am Mo., 17. Dez. 2018 um 22:13 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > Am Mo., 17. Dez. 2018 um 14:52 Uhr schrieb Reggie
> > Scale durations:
> >
> > \relative d {
> > \clef bass
> > \override Beam.grow-direction = #RIGHT
> > \feat
Am Mo., 17. Dez. 2018 um 14:52 Uhr schrieb Reggie :
> How do you change the amount of "beams" you feather when
> the amount of notes is example 3. You need to just forget it? 3 beams are
> not possible?
>
> \relative d {
> \clef bass
> \time 4/4
> d2 e4
> \override Beam.grow-direction =
Am Mo., 17. Dez. 2018 um 21:20 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
> > The idea:
> >
> > #(define-markup-command (wordwrap-field layout props symbol)
> > (symbol?)
[doc-string dropped]
> > (let* ((m (chain-assoc-get symbo
Am Mo., 17. Dez. 2018 um 19:21 Uhr schrieb Br. Samuel Springuel
:
>
> On 2018-12-17 12:08 PM, David Kastrup wrote:
> > Uh, anything wrong with the obvious
> >
> >custom = \markup { PRAELUDIUM I \italic { italicized text } Back to
> > normal }
> >
> > ?
> It works in the MWE I posted, but
Am Fr., 14. Dez. 2018 um 17:12 Uhr schrieb Luca Danieli :
>
> Hi Thomas,
>
> your analysis has been very good.
> I have almost solved the issue.
> I just don't know what's the glyph name for the SEMI-SHARP and SEMI-FLAT
>
> In the following code, I should add the ones for SEMI-SHARP and SEMI-FLAT.
Am Fr., 14. Dez. 2018 um 17:57 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> > Any idea how to tackle:
> > (1) ligatures
> > \lyricmode { f -- i }
>
> Can you give me a real world situation — in a "regular" score (i.e., with
> notes) — in which you would want both a ligature *and* chords on
Am Fr., 14. Dez. 2018 um 04:09 Uhr schrieb Kieren MacMillan
:
>
> Hello all,
>
> I’m trying to develop a Lilypond lyrics+chords [only] framework, and am
> trying to understand the "cleanest" possible starting point.
>
> The final goal: Given a set of lyrics (either with “inline” durations, or
>
Am Do., 13. Dez. 2018 um 23:11 Uhr schrieb Luca Danieli :
> What it did was to replace the line #(ly:parser-set-note-names parser
> pitchnames)
> with #(ly:parser-set-note-names pitchnames)
convert-ly, correctly applied, would have done it for you ;)
> So I have got the same problem of before.
Am Do., 13. Dez. 2018 um 21:59 Uhr schrieb Luca Danieli :
>
> Thank you David.
> I tried to you convert-ly, but I got the following error:
>
> >convert-ly: error: accidentals.ly: Unable to determine version. Skipping
>
> what can I do?
Then there is no \version-statement in the file.
Insert the
Am Mi., 12. Dez. 2018 um 09:53 Uhr schrieb David Kastrup :
>
> David Kastrup writes:
>
> > Thomas Morley writes:
> >
> >> Hi all,
> >>
> >> this works:
> >>
> >> \version "2.19.82"
> >>
> >>
Am Di., 11. Dez. 2018 um 13:56 Uhr schrieb David Sumbler :
> This may well be the answer I need for my full score. But now that you
> have introduced me to "strict-note-spacing" etc., I am again wondering
> whether there might perhaps be a way of getting Lilypond to make 2
> separate
Hi all,
this works:
\version "2.19.82"
tst = \markuplist \italic #(make-list 2 "buzz")
<<
\new Staff { R1 \break R1 }
\new Lyrics \lyricmode { $@tst }
>>
This doesn't work:
tstA =
\markuplist \score-lines { \repeat unfold 80 a'16 }
<<
\new Staff { R1 \break R1 }
\new Lyrics
Am Mo., 10. Dez. 2018 um 18:25 Uhr schrieb David Sumbler :
>
> To recap:
>
>3 days ago I wrote (with this subject line) that I have a passage to
>set where one instrument (harpsichord) plays 8 bars in 4/4 time,
>consisting mainly of semiquavers (sixteenths). It has to be played
>
Am Mo., 10. Dez. 2018 um 11:37 Uhr schrieb Thomas Morley
:
>
> Am Mo., 10. Dez. 2018 um 06:18 Uhr schrieb Flaming Hakama by Elaine
> :
>
> > I'm basically unsure about every step here:
> >
> > Is there such a thing as "the default measure number markup fun
Am Mo., 10. Dez. 2018 um 18:30 Uhr schrieb Veronika Neumann
:
>
> Hello,
>
>
> please have a look at the attached pdf file. I want the circled bar to
> be a single bar. I also included the lilypond file.
>
>
> Many thanks in advance!
>
>
> Veronika Neuman
Hi Veronika,
several possibilities:
%%
Am Mo., 10. Dez. 2018 um 06:18 Uhr schrieb Flaming Hakama by Elaine
:
> I'm basically unsure about every step here:
>
> Is there such a thing as "the default measure number markup function"?
Yes, look into engraver-init.ly, there you'll find for "Score":
barNumberFormatter =
Am So., 9. Dez. 2018 um 17:18 Uhr schrieb Emilio Millan :
>
> I'm using fingerings for some above-the-staff harmonica notation. They are
> working well for this purpose but there is one bit of fine tuning I'd like
> to do if possible. In the example below, the fingerings are well-placed but
> the
To the author of the LSR-snippet "Add wings to all repeat barlines
(simple version)"
http://lsr.di.unimi.it/LSR/Item?u=1=1055
Many thanks for your snippet.
Though, I think it duplicates "Changing the default bar lines"
http://lsr.di.unimi.it/LSR/Item?id=964
which is in our snippets-manual as
Am Sa., 8. Dez. 2018 um 10:08 Uhr schrieb Johan Vromans :
>
> On Thu, 6 Dec 2018 21:15:43 +0100, Annette Kusma
> wrote:
>
> > The output should look something like this:
> >
> > C F C
> > Mary had a little lamb
> > F G C
> > Its fleece was white as
Am Fr., 7. Dez. 2018 um 06:08 Uhr schrieb Peter Crighton
:
>
> On Fri, 7 Dec 2018 at 03:00, Ben wrote:
>>
>> On 12/6/2018 7:49 PM, Peter Crighton wrote:
>>
>> Hello all,
>>
>> I have the following (reduced) scenario where one voice has a chord with a
>> glissando in it and I want to tweak both
Am Do., 6. Dez. 2018 um 19:05 Uhr schrieb Kieren MacMillan
:
>
> Hi all,
>
> If I want to "layer" markups, is there a better way than \combine?
>
> If not, does \combine have a magic way to combine three or more markups that
> doesn’t require chaining it like
>
> \markup \combine \markupA
Am Mi., 5. Dez. 2018 um 11:28 Uhr schrieb Pierre Perol-Schneider
:
>
> Thank you Harm, that works fine (no beam/flag at that point).
> Cheers,
> Pierre
Ok, then I put not more work on it.
Glad I could help,
Harm
___
lilypond-user mailing list
Am Mi., 5. Dez. 2018 um 10:56 Uhr schrieb Pierre Perol-Schneider
:
>
> Thank you Harm,
> In this particular case, there is no chord.
> Cheers,
> Pierre
So why use event-chords and a context-property then?
Wouldn't below work already?
#(define (forced-dir-II grob)
(let* ((x-parent
Am Mi., 5. Dez. 2018 um 10:26 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi All,
>
> I'm looking for a function that'll do:
>
> {
> \clef "G_8"
> \override Fingering.staff-padding = #'()
> 4
>
> }
>
> As a first step, I've tried to adapt Harm's function found here:
>
And I have absolutely no idea why your image is in my reply :(((
I didn't see it, I didn't attach it. Wtf
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Am So., 2. Dez. 2018 um 19:47 Uhr schrieb Sandro Santilli :
>
> On Sun, Dec 02, 2018 at 04:53:58PM +0100, Thomas Morley wrote:
> >
> > The proposed _ly-syntax_ is
> > \parenthesize
> > \parenthesize #'left
> > \parenthesize #'right
> > No parens.
>
Am So., 2. Dez. 2018 um 16:34 Uhr schrieb Sandro Santilli :
>
> On Sun, Dec 02, 2018 at 03:26:44PM +0100, Thomas Morley wrote:
> > Am So., 2. Dez. 2018 um 14:01 Uhr schrieb Sandro Santilli :
> > >
> > > Very obscure way to put chords
> > > in parenth
Am So., 2. Dez. 2018 um 14:01 Uhr schrieb Sandro Santilli :
>
> On Sun, Dec 02, 2018 at 11:01:36AM +, J Martin Rushton wrote:
>
> > "LilyPond source files appear to be written in a custom programming
> > language whose grammar is never discussed."
> > - I'm afraid this one is bang on target.
>
Am Fr., 30. Nov. 2018 um 12:02 Uhr schrieb Tyler Mitchell :
>
> On Fri, Nov 30, 2018 at 11:09:52AM +0100, Thomas Morley wrote:
> > Probably it's enough to use the music-function-default-arguments,
> > which can be omitted with newer versions, i.e.:
> >
> > alter
Am Fr., 30. Nov. 2018 um 09:19 Uhr schrieb Tyler Mitchell :
>
> On Thu, Nov 29, 2018 at 10:10:16PM +0100, Thomas Morley wrote:
> > Hi,
> >
> > I once made below (here a little lifted up):
> >
> [...snip...]
> >
> > HTH,
> > Harm
>
> Than
Am Do., 29. Nov. 2018 um 23:22 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Do., 29. Nov. 2018 um 11:04 Uhr schrieb Richard Shann
> > :
> >
> >>
> >> As a further point is the term "standard markup objects" well-
> >&g
Hi Richard,
please bear in mind I'm not a native speaker.
Thus work on the docs is pretty difficult for me.
That said:
Am Do., 29. Nov. 2018 um 11:04 Uhr schrieb Richard Shann
:
> On Thu, 2018-11-29 at 09:50 +0100, Thomas Morley wrote:
> > Well, in NR 1.8.1 Writing text one can r
Am Do., 29. Nov. 2018 um 11:57 Uhr schrieb Tyler Mitchell :
>
> I'm trying to figure out how to add a "parenthesized" second key
> signature to my music, something like this:
>
> https://www.ldx.ca/tmp/paren-key-1.png
>
> I experimented with adding two \key commands one after the other,
>
Am Do., 29. Nov. 2018 um 09:34 Uhr schrieb Jeff Olson :
>
> I have a complex Mutopia submission that requires different formatting
> for A4 and Letter sized paper (it's too tight on the page to trust
> lilypond's spacing algorithms on the same source without paper specific
> tweaks).
>
> So I'd
Am Do., 29. Nov. 2018 um 09:33 Uhr schrieb Richard Shann
:
>
> On Wed, 2018-11-28 at 15:45 +0100, Lukas-Fabian Moser wrote:
> > > Sorry, I should have made it clearer that this index is being
> > > automatically generated. Now you point out that there is an
> > > \autoOageBreaksOff, which is what
Am Di., 27. Nov. 2018 um 16:22 Uhr schrieb Richard Shann
:
>
> I'm creating an index to my scores, in the form of a sequence of
> LilyPond markups (for title, composer, first few bars etc).
What exactly are you doing? An example would be nice.
> It is working well apart from page breaking which
Am Di., 27. Nov. 2018 um 00:16 Uhr schrieb Malte Meyn :
> „Notes, forked stems“ (l. 109)
> → should be „yes (fake: rotated stems or custom lines)“
>
Or like attached pdf.
Most recent code here (if someone's interested)
https://archiv.lilypondforum.de/index.php/topic,1176.msg6932.html#msg6932
Am So., 25. Nov. 2018 um 16:09 Uhr schrieb Phil Holmes :
>
> - Original Message -
> From: "David Sumbler"
>
> > The parameters NonMusicalPaperColumn and suchlike have long been a
> > mystery to me. If it can be done reasonably succinctly, could you
> > perhaps explain what
'
Am Sa., 24. Nov. 2018 um 22:28 Uhr schrieb Thomas Morley
:
>
> Am Fr., 23. Nov. 2018 um 15:28 Uhr schrieb David Sumbler :
> >
> > -Original Message-
> > From: David Sumbler
> > Reply
> > -To: da...@aeolia.co.uk
> > To: lilypond-user@gnu
Am Fr., 23. Nov. 2018 um 15:28 Uhr schrieb David Sumbler :
>
> -Original Message-
> From: David Sumbler
> Reply
> -To: da...@aeolia.co.uk
> To: lilypond-user@gnu.org
> Subject: Spacing issue after Mark and TextScript
> Date: Wed, 21 Nov 2018 12:24:29 +
>
> %%%
>
Am Do., 22. Nov. 2018 um 23:49 Uhr schrieb Patrick Karl :
>
> I have lately been trying to move from v2.19.81 to 2.19.82. The biggest
> problem I see at this early stage is that
> v2.19.82 documentation is apparently dependent upon a new font,
> Emmentaler-20. Or at least I
> get an error
Am So., 18. Nov. 2018 um 22:16 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > As a side-effect of this thread I learned that doing
> > whatever = \context Staff \applyContext #(lambda (ctx) ...)
> > will affect Staff _and_ all it's alias
Am So., 18. Nov. 2018 um 21:15 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am So., 18. Nov. 2018 um 20:40 Uhr schrieb David Kastrup :
> >
> >> Just do
> >>
> >> (eq? ctx (ly:context-find ctx 'Staff))
> >>
> >> --
&g
Am So., 18. Nov. 2018 um 20:40 Uhr schrieb David Kastrup :
> Just do
>
> (eq? ctx (ly:context-find ctx 'Staff))
>
> --
> David Kastrup
I did not even consider to use ly:context-find. The description says:
Find a _parent_ of context that has name or alias name. Return #f if not found.
So I
Am So., 18. Nov. 2018 um 19:19 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Hi,
> >
> > consider the code below. I'd like to restrict usage to Staff-like
> > contexts, i.e. Staff, Tab- and DrumStaff, etc would be ok, but
> > container-co
Am So., 18. Nov. 2018 um 18:23 Uhr schrieb Thomas Morley
:
>
> Hi,
>
> consider the code below. I'd like to restrict usage to Staff-like
> contexts, i.e. Staff, Tab- and DrumStaff, etc would be ok, but
> container-contexts like StaffGroup, etc should lead to return '().
>
&g
Hi,
consider the code below. I'd like to restrict usage to Staff-like
contexts, i.e. Staff, Tab- and DrumStaff, etc would be ok, but
container-contexts like StaffGroup, etc should lead to return '().
Pseudo-code:
\new Staff(Group)
\with {
\applyContext
#(lambda (context)
(if
Am So., 18. Nov. 2018 um 08:36 Uhr schrieb Andrew Bernard
:
>
> What is the approved and recommend way to attach images for small examples to
> posts in this list?
>
> In the past I have just made an attachment to the post,
Please continue to do so.
Speaking only for myself, frequently I don't
Am Sa., 17. Nov. 2018 um 12:03 Uhr schrieb Thomas Morley
:
> Default \center-column does not adjust baseline-skip according to the
> grobs font-size.
> Below I wrote 'center-column-fontsize-adjusted-baseline-skip' (you
> should probably rename it, lol), which does so. Model
Hi Kieren,
Am Sa., 17. Nov. 2018 um 02:36 Uhr schrieb Kieren MacMillan
:
>
> Hi all,
>
> In the snippet below, you’ll see that I’m attempting to override Fingering in
> a custom context to add a caret (^) on top of the [formatted] finger number
> to make it into a scale degree.
>
> The
Am Mi., 14. Nov. 2018 um 18:07 Uhr schrieb Pierre Perol-Schneider
:
>
> Here's where I am so far:
>
> \version "2.19.82"
> \fixed c' {
> <<
> { \voiceOne
> c16-\offset positions #-1 [ c c c c c c c c c c c c ] }
> \\
> { \voiceOne s4
>\once\override Beam.positions =
Am Mi., 14. Nov. 2018 um 11:04 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > I'm not convinced about below, but for the record:
> >
> > One could give the key-function a string-argument, or probably a symbol
> > And react on the input, like
>
Am Mi., 14. Nov. 2018 um 10:28 Uhr schrieb David Kastrup :
>
> David Kastrup writes:
>
> > Davide Liessi writes:
> >
> >> Il giorno mer 14 nov 2018 alle ore 08:25 Keizen Li Qian
> >> ha scritto:
> >>> Parsing.../usr/share/lilypond/2.18.2/ly/music-functions-init.ly:564:11:
> >>> In procedure
Am Mo., 12. Nov. 2018 um 19:02 Uhr schrieb Torsten Hämmerle
:
> It really starts getting funny if you change the c' into a d' (the c' just
> didn't show up somewhere because it did not change the C major chord):
>
> %%
> <<
> \chords { c }
> \relative { \clef bass d' }
> >>
>
801 - 900 of 3885 matches
Mail list logo
