Thinner Ledger Lines for Cue Notes?
Hello,
I'm working on a violin part score, and I want to make thinner ledger lines
just for cue notes. I've tried usingledger-line-thickness but it seems
that will affect the whole staff and normal size notes. Are there any other
solutions for this?
Here's the code of working example:
\version "2.24.1"
\score {
\relative c'' {
\time 2/2
<<{
r2
\override Stem.direction = #down
b'4. b8
}
\\
\new CueVoice {
g,8 e b e
}
}
}
Re: How to "guarantee" Lilypond pdf (letter) output with sufficient margins for 3-hole punch?
Hi Knute; Thanks for the tips. I'm in the midst of engraving a one-page sheet of music now using your suggestions, hopefully it will be correct for three-hole-punching or easy for me to fiddle with the values of the settings. Thanks, Ken On Mon, Oct 23, 2023 at 1:30 PM Knute Snortum wrote: > > > On Mon, Oct 23, 2023 at 11:09 AM Kenneth Wolcott > wrote: >> >> Hi; >> >> How to "guarantee" Lilypond pdf (letter) output with sufficient >> margins for 3-hole punch? > > > It's no guarantee, but I put the following in my paper block: > > two-sided = ##t > inner-margin = 12\mm > outer-margin = 8\mm > > -- > Knute Snortum > >
Re: How to "guarantee" Lilypond pdf (letter) output with sufficient margins for 3-hole punch?
On Mon, Oct 23, 2023 at 11:09 AM Kenneth Wolcott wrote: > Hi; > > How to "guarantee" Lilypond pdf (letter) output with sufficient > margins for 3-hole punch? > It's no guarantee, but I put the following in my paper block: two-sided = ##t inner-margin = 12\mm outer-margin = 8\mm -- Knute Snortum
Re: WARNING: SPAM / MALWARE being sent to list members
Thus said Jean Abou Samra on Mon, 23 Oct 2023 19:53:25 +0200: > Let's not get into a debate about this on the list. We can discuss it > privately if you like. Not worth debating. I was hoping that whatever is generating spam in response to list posts would send me something. Andy
Re: WARNING: SPAM / MALWARE being sent to list members
Thus said Jean Abou Samra on Mon, 23 Oct 2023 18:28:12 +0200: > Luckily, we have technologies (SPF and DKIM) that can guarantee an > email is sent from the owner of the sender address, and if an email > doesn't pass SPF/DKIM, it's very likely to be blocked by your spam > filter. Unfortunately SPF and DKIM are terrible hacks and wholly unnecessary. Andy
Re: WARNING: SPAM / MALWARE being sent to list members
> Le 23 oct. 2023 à 19:33, Andy Bradford > a écrit : > > Unfortunately SPF and DKIM are terrible hacks and wholly unnecessary. Let's not get into a debate about this on the list. We can discuss it privately if you like.
Re: WARNING: SPAM / MALWARE being sent to list members
I've just received a similar email, purporting to be from Michael Werner in response to my recent posting on the list, but actually from a bogus email address. It seems that lilypond-user is being targetted by emails of the form: From: Well Known lilypond user To: Your Own address used on lilypond-user Subject: Re: subject-of-some-thread-you-posted-to Check document: Hi > > Your posting to the list quoted here > Note that lilypond-user@gnu.org is **not** included in the addressees. Be careful out there folks.
How to "guarantee" Lilypond pdf (letter) output with sufficient margins for 3-hole punch?
Hi; How to "guarantee" Lilypond pdf (letter) output with sufficient margins for 3-hole punch? I'm looking forward to having a method of "guaranteeing" Lilypond pdf output for letter (not a4) of my engravings such that the resulting printout can be three-hole punched (on both sides potentially) without making adversely affecting the visibility of the pdf. This "procedure" or "process" might be needed retroactively as well as for a new engraving project. I know that this might be a proportionate value so I'd have to adjust it if I specified (or changed) a global font size. I guess what I'm looking for is the equivalent of "indent" but for every system. I'll look again to see if I understand "margin"-related settings... Thanks for hints... Ken Wolcott
Re: WARNING: SPAM / MALWARE being sent to list members
Thanks for the warning. Le lundi 23 octobre 2023 à 17:15 +0100, Richard Shann a écrit : > specifically, if you get an email with a name you recognize check the > email address is the one that person usually uses (mine purported to > come from Jean-Abou but the email address was spurious). And note that *even* if you receive an email that comes from a certain address, it does not guarantee that the email comes from the owner of that address. It is easy to impersonate an email address. For example, there are many scams that look like they are sent from your own address, to make you believe it has been hacked. Luckily, we have technologies (SPF and DKIM) that can guarantee an email is sent from the owner of the sender address, and if an email doesn't pass SPF/DKIM, it's very likely to be blocked by your spam filter. But this is still possible. A fortiori, if you receive an email signed "John Doe" but the sender address isn't John Doe's usual email address, it is very likely a scam. signature.asc Description: This is a digitally signed message part
Re: WARNING: SPAM / MALWARE being sent to list members
specifically, if you get an email with a name you recognize check the
email address is the one that person usually uses (mine purported to
come from Jean-Abou but the email address was spurious).
Richard
On Mon, 2023-10-23 at 12:01 -0400, Rik Kabel wrote:
> The following turd was sent to me this morning. I have removed the
> link so that it is not accidentally activated.
> The email source is full of faked headers.
> Be careful about what you open and click on.
> --
> Rik
>
>
> Forwarded Message
> >
> > Subject:Re: Where did the \header number go?
> > Date: Mon, 23 Oct 2023 08:15:20 -0600
> > From: Panix
> > To: r...@panix.com
> >
> >
> >
> > Check document: SPAM LINK REMOVED
> >
> > On 8/20/2023 11:35 AM, Jean Abou Samra wrote:
> >
> > Le dimanche 20 août 2023 à 10:54 -0400, Rik Kabel a écrit :
> > Hello list,
> > I have a few pieces that have been engraved for my choir with
> > 2.18.10 that include catalog numbers entered as
> >
> > \header {
> > ...
> > number = \markup { \fontsize #4 \sans \ellipse 11B }
> > ...
> > }
> > The number variable seems to be gone with current versions, and I
> > can find no mention of the change.
> > Has another feature taken its place?
> >
> >
> > I could not see any effect of adding number = "foo" to a \header
> > block in 2.18.0, and I did not find any trace of this in the source
> > code of that version either?
> >
> > Maybe you redefined a title using one of the xxxTitleMarkup
> > variables, and you used \fromproperty #'header:number there?
> >
> > Or maybe you're just confusing this with the 'opus' variable?
> >
> > Sorry for the noise.
> > The number was set in a bookTitleMarkup block in the paper
> > definition.
WARNING: SPAM / MALWARE being sent to list members
The following turd was sent to me this morning. I have removed the link
so that it is not accidentally activated.
The email source is full of faked headers.
Be careful about what you open and click on.
--
Rik
Forwarded Message
Subject: Re: Where did the \header number go?
Date:Mon, 23 Oct 2023 08:15:20 -0600
From:Panix
To: r...@panix.com
Check document: SPAM LINK REMOVED
On 8/20/2023 11:35 AM, Jean Abou Samra wrote:
Le dimanche 20 août 2023 à 10:54 -0400, Rik Kabel a écrit :
Hello list,
I have a few pieces that have been engraved for my choir with
2.18.10 that include catalog numbers entered as
\header {
...
number = \markup { \fontsize #4 \sans \ellipse 11B }
...
}
The number variable seems to be gone with current versions, and I
can find no mention of the change.
Has another feature taken its place?
I could not see any effect of adding number = "foo" to a \header
block in 2.18.0, and I did not find any trace of this in the source
code of that version either?
Maybe you redefined a title using one of the xxxTitleMarkup
variables, and you used \fromproperty #'header:number there?
Or maybe you're just confusing this with the 'opus' variable?
Sorry for the noise.
The number was set in a bookTitleMarkup block in the paper definition.
--
RIk
