On 30.06.2018 14:14, Urs Liska wrote:
# Encourage people to use the new system and "deprecate" the old syntax
(but leave it alone and working). The downside is that the *names* of
the old commands are very much what one would want, so I wouldn't want
to discard them completely.
# Make the old
I'm slowly getting a handle on edition-engraver, largely thanks to this[1]
guide, which very clearly explains basic usage for a single edition. However,
neither the guide nor the usage examples in the repo demonstrate the use of
multiple editions, and I'm confused as to how that would be done
Hi All,
I'm looking for a solution for printing a C Delta 7 chord name (so that 7
prints clearly after the delta symbol). I started off wth the failed
attempt below and haven't had much success anyway else:
\version "2.18.2"
\score {
<<
\relative c' {
c4 c c c |
}
\chords {
c1:maj7.7
}
>>
- Original Message -
From: "David Wright"
To: "Lilypond-User"
Sent: Saturday, June 30, 2018 4:13 AM
Subject: 2.19.82 manuals are very small!
The new 2.19.82 manuals make interesting reading, but the diagrams
leave something to be desired, namely most of the musical fonts:
This
On 6/30/2018 7:20 AM, Torsten Hämmerle wrote:
SoundsFromSound wrote
I've tried to fix this collision but I don't understand how I can avoid
it. I believe it has to do with either my Score.BarNumber stencil or
offsets of measure numbers, but I can't get the right combo with the
system padding.
Hi All,
Is there a simple way of modifying chord names in the \chords field with
markup text? More specifically, I'm looking for a way to print C7alt as a
chord name (with alt printing clearly after the 7), and I'm having some
trouble figuring out the syntax.
\version "2.18.2"
\score {
<<
Hello Reilly,
chExceptions is you friend, look for « Customizing chord names » in the LP
Notation Reference.
JM
> Le 30 juin 2018 à 08:37, Reilly Farrell a écrit :
>
> Hi All,
>
> I'm looking for a solution for printing a C Delta 7 chord name (so that 7
> prints clearly after the delta
Same part of the doc as for your previous post.
A nice day!
JM
> Le 30 juin 2018 à 08:42, Reilly Farrell a écrit :
>
> Hi All,
>
> Is there a simple way of modifying chord names in the \chords field with
> markup text? More specifically, I'm looking for a way to print C7alt as a
> chord
SoundsFromSound wrote
> I've tried to fix this collision but I don't understand how I can avoid
> it. I believe it has to do with either my Score.BarNumber stencil or
> offsets of measure numbers, but I can't get the right combo with the
> system padding.
Hi Ben,
I think this shouldn't
2018-06-30 8:37 GMT+02:00 Reilly Farrell :
> Hi All,
>
> I'm looking for a solution for printing a C Delta 7 chord name (so that 7
> prints clearly after the delta symbol). I started off wth the failed
> attempt below and haven't had much success anyway else:
>
> \version "2.18.2"
>
> \score {
>
Hi,
as you know I'm working on a number of features around the scholarLY
package, and now I'm facing the need to deal with the existing interface.
The openLilyLIb module scholarly.annotate provides commands like
\criticalRemark, \musicalIssue and a few more that attach an annotation
to a
I'm happy to go with the consensus. Breaking any of my old documents won't
be an issue for me, and I'm happy to defer to your expertise.
Craig
On Sat, 30 Jun 2018 at 23:13, Simon Albrecht wrote:
> On 30.06.2018 14:14, Urs Liska wrote:
> > # Encourage people to use the new system and
Hi Simon and Craig,
I think it's a good point. And since maybe I'll have to suffer more than
anyone else ;-) I shouldn't wring my hands too much and just go for that.
There will be a Git tag referencing the latest state of the "old"
interface, and it should be possible to use that for
Thank you Thomas! Works like a charm. :)
On Sat, Jun 30, 2018 at 1:08 AM, Thomas Morley
wrote:
> 2018-06-30 8:37 GMT+02:00 Reilly Farrell :
> > Hi All,
> >
> > I'm looking for a solution for printing a C Delta 7 chord name (so that 7
> > prints clearly after the delta symbol). I started off
>
> Message: 2
> Date: Fri, 29 Jun 2018 13:18:18 -0500
> From: Karlin High
> To: lilypond-user@gnu.org, David Wright ,
> crimsonsunr...@protonmail.com
> Cc: torsten.haemme...@web.de, David Kastrup
> Subject: Re: \bookparts and scaling
> Message-ID:
> Content-Type: text/plain;
Unfortunately, for my use case, \once\set and \once\unset aren't enough.
On Sat, Jun 30, 2018 at 8:31 PM Aaron Hill wrote:
> On 2018-06-30 17:50, Saul Tobin wrote:
> > In both 2.18 and 2.19, \unset appears to set a context property to the
> > built-in default, rather than the default set in the
On 2018-06-30 19:54, Freeman Gilmore wrote:
How do I restore Frescobaldi to the default window layout?
Thank you, ƒg
Probably silly for me to even attempt to field this question as I have
never used Frescobaldi before. Doing a quick search did not turn up
anything about options for
In both 2.18 and 2.19, \unset appears to set a context property to the
built-in default, rather than the default set in the \with {} block:
music = \relative c' {
\tuplet 3/2 {
c8 c c d d d e e e f f f |
}
\set Staff.tupletSpannerDuration = #(ly:make-moment 1/2)
\tuplet 3/2 {
c8 c
How do I restore Frescobaldi to the default window layout?
Thank you, ƒg
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On 2018-06-30 17:50, Saul Tobin wrote:
In both 2.18 and 2.19, \unset appears to set a context property to the
built-in default, rather than the default set in the \with {} block:
[ . . . ]
In cases like this, I would find it useful to reset the property to the
custom default value without
20 matches
Mail list logo
