On 2016-12-18 6:57 PM, Simon Albrecht wrote:
#(if (not (defined? 'aster))
(define aster #{ \set stanza = \markup "*" #}))
Thanks Simon, that works perfectly.
--
✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
__
On 18.12.2016 23:30, Br. Samuel Springuel wrote:
Some Googling led me to this idea:
#(if (not (defined? aster)) (aster = { \set stanza = \markup{"*"} }))
but this mixes scheme and lilypond syntax in a way I suspect is not
allowed
Yes :-)
Here’s how:
#(if (not (defined? 'aster))
(define as
Building on the idea, I could reduce the number of needed files from 3
to 2 if I could test whether aster has been defined or not. In this
instance the source file would check to see if aster is defined, and if
not define it. The second file would would first define aster and then
load the fi
Good point, shall we say, to match what is commonly done in this style ;)
No point in calling the same over and over again. How about:
halve-half-stems =
\override Stem.before-line-breaking =
#(lambda (grob)
(if (= 1 (ly:grob-property grob 'duration-log))
(let ((half-orig-lngth (/ (ly:grob-p
Question on tags: Is there a way to have a tag set, of which one (and
only one) can be kept on a given compilation? For instance, in Kieren's
code, when compiling only one of male, female, and malefemale should be
kept. Ideally I'd like a staff which neglects to specify which one is
to be kep
On 2016-12-18 1:12 PM, David Kastrup wrote:
I beg to differ. Have you actually tried compiling the result or just
glanced over it?
I just glanced it over and didn't see any changes in the code. Doing it
again now that I know what to look for, I do indeed spot the change.
Guess that's what I
"Br. Samuel Springuel" writes:
> On 2016-12-18 12:24 PM, Malte Meyn wrote:
>> Try an additional \with:
>>
>> \new Staff \with \timeless { c' }
>
> That does indeed work, but isn't that redundant programming?
timeless = \with { }
\new StaffGroup { \new Staff \timeless { c' } }
timeless = { g' }
"Br. Samuel Springuel" writes:
> When I compile the following snippet I get an error under 2.19.53 that
> wasn't there under 2.18.2:
>
> \version "2.19.53"
>
> timeless = \with {
> \remove "Time_signature_engraver" }
>
> \new Staff \with {
> \remove "Time_signature_engraver" }
> { c'
On 2016-12-18 12:24 PM, Malte Meyn wrote:
Try an additional \with:
\new Staff \with \timeless { c' }
That does indeed work, but isn't that redundant programming?
--
✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_
Am 18.12.2016 um 18:03 schrieb Br. Samuel Springuel:
When I compile the following snippet I get an error under 2.19.53 that
wasn't there under 2.18.2:
\version "2.19.53"
timeless = \with {
\remove "Time_signature_engraver" }
\new Staff \with {
\remove "Time_signature_engraver" }
{ c'
When I compile the following snippet I get an error under 2.19.53 that
wasn't there under 2.18.2:
\version "2.19.53"
timeless = \with {
\remove "Time_signature_engraver" }
\new Staff \with {
\remove "Time_signature_engraver" }
{ c' }
\new Staff \timeless
{ c' }
Running the sn
Hello all,
I would like to be able to control “at runtime” the SpanBar immediately below a
given Staff, regardless of whether it is inside a StaffGroup [with its own
SpanBar settings], etc. All of the solutions I’ve found for controlling
SpanBars are more global (e.g.,
http://lists.gnu.org/arc
Thanks Harm, based on what you did I was able to develop the following
which got me what I was looking for:
\version "2.19.52"
#(define ((make-custom-tick-bar-line x y) grob extent)
"Draw a tick bar line."
(let* ((staff (ly:staff-symbol-staff-space grob))
(staff-line-thickness (ly:
Hello,
> I have some hymns which are sung on the occasion of saint's days which have
> pronouns which refers to the saint. Obviously, these pronouns should be
> either "he", "his", "him" or "she", "her" depending on the gender of the
> saint. When producing scores which are unattached to a sp
I have some hymns which are sung on the occasion of saint's days which
have pronouns which refers to the saint. Obviously, these pronouns
should be either "he", "his", "him" or "she", "her" depending on the
gender of the saint. When producing scores which are unattached to a
specific liturgy,
Andrew,
Sorry:
\version "2.19.52"
\language "english"
{
\time 3/4
\key gs \minor
\clef bass
\relative c'
% \override DynamicLineSpanner.rotation = #'(45 0 0)
{
% Andrew Bernard's solution
\override PhrasingSlur.outside-staff-priority = 1000
8\( b,\) \( ds^\< fs ds'\)\! |
%
2016-12-18 15:08 GMT+01:00 Peter Toye :
> Thomas,
>
> Thanks. It just looks odd that the convert.ly issued with .52 only updates
> to .49
This is a misunderstanding.
convert-ly from lilypond-2.19.52 _does_ update to 2.19.52.
Or more precisely: all syntax-changes for which a convert-rule exist
are
Thomas,
Thanks. It just looks odd that the convert.ly issued with .52 only updates to
.49 - I'm not an experienced LilyPonder you know :-)
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Sunday, December 18, 2016, 12:28:57 PM, you wrote:
> 2016-12-18 12:
Thomas,
Sorry, clicked "send" before copying the snippet in. Now posted.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Sunday, December 18, 2016, 1:11:45 PM, you wrote:
Hi Peter,
2016-12-18 13:04 GMT+01:00 Peter Toye :
Andrew, Jacques,
I tried rotatin
On 2016-12-18 12:54, Peter Toye wrote:
convert-ly oddities I've just installed 2.19.52 and put it into
Frescobaldi. On converting two of my files I got 2 oddities:
2) (annoying) It inserted a blank line between each of the original
lines in the file. Could this be because I'm using Windo
Il giorno dom 18 dic 2016 alle 13:28, Thomas Morley
ha scritto:
2) (annoying) It inserted a blank line between each of the original
lines in
the file. Could this be because I'm using Windows and the CR-LF
newline is
confusing it? This would appear to be a bug.
Maybe related to Frescobaldi
Hi Peter,
2016-12-18 13:04 GMT+01:00 Peter Toye :
> Andrew, Jacques,
>
> I tried rotating the hairpin to get closer to the original and got an odd
> result. In the snippet below, removing the comment on the rotation does not
> rotate the hairpin, which I thought it would, but instead moves the
>
2016-12-18 12:54 GMT+01:00 Peter Toye :
> I've just installed 2.19.52 and put it into Frescobaldi. On converting two
> of my files I got 2 oddities:
>
> 1) (fairly serious) It converted to 2.19.49, not .52
There are no converting-rules for versions higher than 2.19.49 (no need for it)
So convert-l
On 2016-12-18 12:54, Peter Toye wrote:
convert-ly oddities I've just installed 2.19.52 and put it into
Frescobaldi. On converting two of my files I got 2 oddities:
1) (fairly serious) It converted to 2.19.49, not .52 - I changed the
version number by hand, but I'd have thought that this shoul
Andrew, Jacques,
I tried rotating the hairpin to get closer to the original and got an odd
result. In the snippet below, removing the comment on the rotation does not
rotate the hairpin, which I thought it would, but instead moves the right-hand
end of the slur.
I've now downloaded 2.19.52,
I've just installed 2.19.52 and put it into Frescobaldi. On converting two of
my files I got 2 oddities:
1) (fairly serious) It converted to 2.19.49, not .52 - I changed the version
number by hand, but I'd have thought that this should be automatic. The message
at the bottom of the file is:
%{
Hi Carl,
2016-12-18 6:20 GMT+01:00 Carl Williams :
> For those interested,
>
> I made some improvements to the solution for this. It now accounts for
> whether the stems are up or down, so as to match what is commonly done in
> modern tablature.
I really doubt about "commonly" ;)
I've seen so man
Kaspersky seem to have updated their database. 2.19.52 installed OK this
morning (UK time)
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Friday, December 16, 2016, 3:45:05 PM, you wrote:
David,
Kaspersky have told me that it's a false positive and it will be correcte
On 17/12/16 17:04, David Sumbler wrote:
Further to my earllier message, I have realized that the problem I am
getting has nothing to do with variable scope (at least, I don't think
it does), so I was asking the wrong question.
But the problem still exists.
I can't say I understand what is
2016-12-18 2:15 GMT+01:00 Br. Samuel Springuel :
> How would I define a bar line such that the top is in the middle of the top
> staff space and the bottom in the middle of the bottom staff space (i.e.
> what would be called a divisio minor if I was typesetting Gregorian chant,
> except on a modern
30 matches
Mail list logo