Le dimanche 02 juillet 2023 à 23:25 -0700, Curt McDowell a écrit :
>
> I don't think it's tenable to expect anyone to keep a separate version of
> LilyPond for each unique \version called for by all the scores in their
> library. In the current system, that would be the only way to guarantee
> co
I don't think it's tenable to expect anyone to keep a separate version
of LilyPond for each unique \version called for by all the scores in
their library. In the current system, that would be the only way to
guarantee correct and consistent output.
I'd hesitate to call the LilyPond version sys
Le samedi 01 juillet 2023 à 11:30 -0700, Curt McDowell a écrit :
> I tend not to use convert-ly because I feel upgrading a file version
> would unfairly force anyone who wants to compile my music to upgrade
> their LilyPond installation. Upgrading might not be straightforward when
> using a stan
how to submit a feature request issue.
I'd like to request the following change to the LilyPond parser:
One feature that would be useful is for the LilyPond parser to output
the following version numbers:
The LilyPond version, e.g. 2.24.1;
The source file "\version", e.g. 2.22.0.
If
Le samedi 01 juillet 2023 à 12:46 +0200, Valentin Petzel a écrit :
> Maybe Lilypond should also give a warning if it on a lower language version.
> The assumption here is that lower language versions are generally compatible
> with higher program versions, but this is not true. So basically we on
Maybe Lilypond should also give a warning if it on a lower language version.
The assumption here is that lower language versions are generally compatible
with higher program versions, but this is not true. So basically we only
guarantee that a specific language version will be working with the s
Le vendredi 30 juin 2023 à 15:36 -0700, Stu McKenzie a écrit :
>
> I'm not sure how to submit a feature request issue.
>
> I'd like to request the following change to the LilyPond parser:
>
> One feature that would be useful is for the LilyPond parser to output
>
I'm not sure how to submit a feature request issue.
I'd like to request the following change to the LilyPond parser:
One feature that would be useful is for the LilyPond parser to output
the following version numbers:
The LilyPond version, e.g. 2.24.1;
The source file "
Le mardi 09 mai 2023 à 08:14 +, Werner LEMBERG a écrit :
> Yes, evaluated, sorry.
It is evaluated when baz is executed.
```
(define (foo bar)
(define (baz)
(if bar "yes" "no"))
(set! bar #t)
(baz))
(foo #f) ⇒ "yes"
```
signature.asc
Description: This is a digitally signed mess
>>
>> D'oh, this should be
>>
>> ```
>> (define (foo bar)
>> (define (baz)
>> ...
>> (if bar) ; Is 'bar' visible here? If yes, when is
>> ... ; 'bar' expanded? At the time 'baz' is
>> ; defined? At the time 'baz' is executed?
>> ```
>
> I do
On 5/9/23 03:22, Jean Abou Samra wrote:
Le lundi 08 mai 2023 à 22:55 -0400, dfro a écrit :
Jean,
I think \translate-scaled will work for me! This is a wonderful
tool. In the following example, \concat allows me to get the symbols
closer together. The -.2 values for x in /translate-scaled o
On 5/9/23 03:22, Jean Abou Samra wrote:
Le lundi 08 mai 2023 à 22:55 -0400, dfro a écrit :
Jean,
I think \translate-scaled will work for me! This is a wonderful
tool. In the following example, \concat allows me to get the symbols
closer together. The -.2 values for x in /translate-scaled o
Le lundi 08 mai 2023 à 22:55 -0400, dfro a écrit :
>
> Jean,
>
> I think \translate-scaled will work for me! This is a wonderful tool. In the
> following example, \concat allows me to get the symbols closer together. The
> -.2 values for x in /translate-scaled on the third \markup example d
Le mardi 09 mai 2023 à 04:26 +, Werner LEMBERG a écrit :
>
> D'oh, this should be
>
> ```
> (define (foo bar)
> (define (baz)
> ...
> (if bar) ; Is 'bar' visible here? If yes, when is
> ... ; 'bar' expanded? At the time 'baz' is
> ; defin
> BTW, I suggest to cover one more issue with local variables, namely
> whether arguments to a function are seen in sub-functions, which are
> IMHO a very good addition to `let` and `let*` to write clean and
> readable code – often much more readable than anonymous lambda
> expressions.
>
> Examp
> Second, you need to use `let` here, not `define`. See
>
> https://extending-lilypond.gitlab.io/en/scheme/local-variables.html
BTW, I suggest to cover one more issue with local variables, namely
whether arguments to a function are seen in sub-functions, which are
IMHO a very good addition to `l
On 5/8/23 21:06, Jean Abou Samra wrote:
Le lundi 08 mai 2023 à 20:55 -0400, dfro a écrit :
Fellow music engravers,
I have a feature request. Perhaps, this has been discussed already.
Sometimes, I would like the spacial formatting in a \markup command
to respond to changes in fontsize, so
Le lundi 08 mai 2023 à 20:55 -0400, dfro a écrit :
> Fellow music engravers,
>
> I have a feature request. Perhaps, this has been discussed already.
>
> Sometimes, I would like the spacial formatting in a \markup command to
> respond to changes in fontsize, so that all of t
Fellow music engravers,
I have a feature request. Perhaps, this has been discussed already.
Sometimes, I would like the spacial formatting in a \markup command to
respond to changes in fontsize, so that all of the \markup spacing will
change proportional to the change in fontsize. I think
Hi all,
Just want to let everyone know, auto-transpose in OpenLilyLib now has
automatically inserted key signatures.
https://github.com/openlilylib/oll-misc/tree/master/pitch/auto-transpose
Please let me know if you run into any bugs using it.
Saul
lcott a écrit :
>>>
>>> Hi;
>>>
>>> I tried to engrave a simple Tuba Duet that has a Fine+D.C. construct
>>> using Lilypond 2.23.9
>>>
>>> I don't think I used the Al_Fine repeat feature correctly, as the
>>> "Fine"
should precede the note it applies to.
>
> JM
>
>
>
>
>
> > Le 29 mai 2022 à 01:59, Kenneth Wolcott a écrit :
> >
> > Hi;
> >
> > I tried to engrave a simple Tuba Duet that has a Fine+D.C. construct
> > using Lilypond 2.23.9
> >
> &
+D.C. construct
> using Lilypond 2.23.9
>
> I don't think I used the Al_Fine repeat feature correctly, as the
> "Fine" is displayed one bar later than I expected it to be.
>
> Could someone be so kind as to explain what I did wrong or what I
> could do better?
>> This sounds sensible; maybe this suppression of processing `\score`
>> blocks can be implemented in Scheme so that LilyPond with a special
>> command line option acts as a syntax checker.
>
> Have you actually tried? Apart from scores placed in explicit books
> and bookparts, LilyPond alread
Le 29/03/2022 à 09:31, Werner LEMBERG a écrit :
In this context I could imagine a paramater that kind of highlights
the first few error messages (or only shows the first N error
messages) being very forthcoming to some people without a dev
background. Or maybe at the end of the compilation output
>
> This sounds sensible; maybe this suppression of processing `\score`
>
> blocks can be implemented in Scheme so that LilyPond with a special
>
> command line option acts as a syntax checker.
>
That would be an improvement. It's still however not what the OP's
Ah, mea culpa.
www.martinrinconbotero.com
>
> On Mar 29, 2022 at 12:58 PM, mailto:d...@gnu.org)> wrote:
>
>
>
> Martín Rincón Boterowrites: > >> Since
> TeX is predominantly employed for compiling LaTeX sources, that >> speaks
> more
Martín Rincón Botero writes:
>
>> Since TeX is predominantly employed for compiling LaTeX sources, that
>> speaks more about the LaTeX implementation than TeX itself.
>
> Because I'm under the impression that Lilypond is more similar to
> LaTeX than to TeX,
It totally isn't, neither in
Werner LEMBERG writes:
>> Why make the user wait so long to make him fix a misspelled word or
>> make him put a curly brace? A first pass should be done without
>> \score blocks and abort (or at least ask if you want to continue!)
>> if this first pass produces errors.
>
> This sounds sensible; m
>
>
> Since TeX is predominantly employed for compiling LaTeX sources, that
>
>
>
> speaks more about the LaTeX implementation than TeX itself.
>
>
>
Because I'm under the impression that Lilypond is more similar to L
> Why make the user wait so long to make him fix a misspelled word or
> make him put a curly brace? A first pass should be done without
> \score blocks and abort (or at least ask if you want to continue!)
> if this first pass produces errors.
This sounds sensible; maybe this suppression of proce
Martín Rincón Botero writes:
> I'm lucky to be able to work using Lilypond through Python. I never
> compile the whole score I'm working on, but only the current "segment"
> (around 2 pages) and the corresponding pages get updated in the
> PDF. Compiling the whole thing is something I do only at
*I'll implement it.
On mar. 29 2022, at 12:06 pm, Martín Rincón Botero
wrote:
> > Sometimes I want to see the output inspite of errors. Aborting
> > immediately if there is a syntax problem is definitely not always the
> > best solution. I fully agree with other people that it should be
> > Fres
> Sometimes I want to see the output inspite of errors. Aborting
> immediately if there is a syntax problem is definitely not always the
> best solution. I fully agree with other people that it should be
> Frescobaldi's job to jump to the first error message (in case it
> doesn't do this already).
> But shouldn't Lilypond check first if the syntax is correct instead
> of spending several seconds/minutes compiling a code that's doomed
> to visually fail?
Sometimes I want to see the output inspite of errors. Aborting
immediately if there is a syntax problem is definitely not always the
bes
> I strongly disagree :-)
> When there is an error, the default should be to continue as long as
> possible. For large projects where the compilation takes time, you want
> to have some viewable output even if there is a glitch somewhere. I also
> think you are overestimating the "developing effort
> In this context I could imagine a paramater that kind of highlights
> the first few error messages (or only shows the first N error
> messages) being very forthcoming to some people without a dev
> background. Or maybe at the end of the compilation output a clearly
> marked: "First (few?) Error(
I think most developers are used to having a full error log - which is
definitely the right default behaviour for lilypond. On the other hand I
can fully understand that especially for users that aren't used to software
development a full error log can be quite a mess to the (untrained) eye.
In th
Le 29/03/2022 à 08:46, Martín Rincón Botero a écrit :
+1. I think making it customizable (with a --cascade-level parameter)
wouldn't add much value considering developing effort, though.
Lilypond, like Python f. ex., should simply report the first error
(and ideally immediately abort compilatio
+1. I think making it customizable (with a --cascade-level parameter)
wouldn't add much value considering developing effort, though. Lilypond, like
Python f. ex., should simply report the first error (and ideally immediately
abort compilation).
—Martín.
www.marti
On Mon, Mar 28, 2022 at 4:58 PM David Kastrup wrote:
>
> Christopher Heckman writes:
>
> > I have a request concerning Lilypond that has bothered me for a while,
> > but which I haven't seen any one else complain about. It is the
> > cascade of error messages you get when you leave out a right-br
Christopher Heckman writes:
> I have a request concerning Lilypond that has bothered me for a while,
> but which I haven't seen any one else complain about. It is the
> cascade of error messages you get when you leave out a right-brace or
> some other symbol.
>
> Maybe this could be added as an o
+1
From: lilypond-user
on behalf of Christopher Heckman
Date: Monday, March 28, 2022 at 7:11 PM
To: lilypond-user@gnu.org
Subject: Feature request: Fix cascading error messages
I have a request concerning Lilypond that has bothered me for a while,
but which I haven't seen any one
I have a request concerning Lilypond that has bothered me for a while,
but which I haven't seen any one else complain about. It is the
cascade of error messages you get when you leave out a right-brace or
some other symbol.
Maybe this could be added as an option to lilypond?
lilypond --cascade-le
Hello,
I just added a new useful feature to Spontini-Editor; It is now possible to
automatically add customizable templates to the score, using the
autocomplete tool provided by CodeMirror.
See:
https://github.com/paopre/Spontini/blob/master/documentation/miscellaneous.md
...at the paragraph
Hi Jean,
thank you for that font showcase! I’ll take a closer look at Profondo. However,
its overly long bass clef looks quite unappealing to me. I wouldn’t use any of
the others, as far as I can tell.
About what pairs with what is certainly more of a matter of taste. I find
Emmentaler’s trill
Le 24/10/2020 à 11:47, Martín Rincón Botero a écrit :
Hello all,
a few months ago in some forum I found the following snippet of a
beautiful G clef (I think by Pierre Perol-Schneider) that I've been
extensively using since then. Right now in the NR we have \clef G,
\clef treble, \clef "G2" a
Thank you Simon for your answer. As much as I applaud the efforts for making
Lilypond work with other fonts, I find it a pity that more glyphs can’t be
included in the core. It’s not rare to find alternative or “extra” glyphs in
other fonts either (Maestro, Opus, etc.), so this wouldn’t be the f
Hi Martín,
On 24.10.20 11:47, Martín Rincón Botero wrote:
I wish Perol-Schneider's clef could be considered for inclusion into
standard Lilypond, possibly named as "G2" (which would actually
produce a "second" G clef) or as \clef varG.
two things here: there has been a lot of work to making
Hello all,
a few months ago in some forum I found the following snippet of a beautiful
G clef (I think by Pierre Perol-Schneider) that I've been extensively using
since then. Right now in the NR we have \clef G, \clef treble, \clef "G2"
and \clef violin, all producing what seems to be the exact sa
Hi Andrew,
I'll put up a MR to add the improved \shape to lilypond proper, as
soon as I find the time to do so.
At least it will be an improvement.
Though, I did not look into shapeII, maybe it could be improved similarly?
Cheers,
Harm
Am Mo., 12. Okt. 2020 um 09:55 Uhr schrieb Andrew Bernard
Stay tuned, and will add the improvement to the OLL repository, once I
have it all set up.
Andrew
On Mon, 12 Oct 2020 at 17:44, Martín Rincón Botero
wrote:
>
>
> I have to run more tests, but your \shape-h function is simply excellent.
> Thank you! I wish this could be the default behavior of a
Dear Harm,
I have to run more tests, but your \shape-h function is simply excellent. Thank
you! I wish this could be the default behavior of a new \reshape function.
Perhaps the open issue shouldn’t be fixed for \shape: that way the folks who
carefully used small values for small staves to fix
Dear Thomas,
sorry for not having provided examples myself of what doesn’t scale. I haven’t
had the time for that yet. However, your explanation seems to be right. I
definitely have to use smaller values for smaller font sizes. I was planning to
collect a few examples from the viola concerto I’
Am Mi., 7. Okt. 2020 um 10:35 Uhr schrieb Martín Rincón Botero
:
>
> Now that we’ve been talking about \shape and \shapeII, I would like to ask if
> it’s possible that values put for \shape(II) could scale according to staff
> size. Whenever I have a smaller staff, whatever values work for a 20 p
Le 07/10/2020 à 19:50, Jean Abou Samra a écrit :
Le 07/10/2020 à 18:58, Martín Rincón Botero a écrit :
Hello Jean,
thanks for further exploring the first request. In my experience with
Lilypond 2.20 \shape doesn’t scale with set-global-staff-size either.
I’m already kinda “used” to writing
Le 07/10/2020 à 18:58, Martín Rincón Botero a écrit :
Hello Jean,
thanks for further exploring the first request. In my experience with
Lilypond 2.20 \shape doesn’t scale with set-global-staff-size either.
I’m already kinda “used” to writing smaller values —my primitive math
only cooperated
in
> > piano scores) —this is however my speculation.
> >
> > My second feature request is for \shapeII. I find it great to have a (head)
> > attachment value instead of having to manually calculate how much of an
> > offset it would take to bring the slur closer to the
piano scores) —this is however my speculation.
My second feature request is for \shapeII. I find it great to have a
(head) attachment value instead of having to manually calculate how
much of an offset it would take to bring the slur closer to the head.
Consequently, it would be nice if you could
scores) —this is however my speculation.
My second feature request is for \shapeII. I find it great to have a (head)
attachment value instead of having to manually calculate how much of an offset
it would take to bring the slur closer to the head. Consequently, it would be
nice if you could do
Hi all,
triggered by a new analysis.highlighters module that Klaus Blum shared
with me last week I had a few feature/functionality wishes that I
implemented, especially a kind of stylesheet support and selective
activation of elements. I quickly realized that this should be
generalized and
Right now we have ly:source-files which contains a list of all input files
which have been opened up to the point of it’s call, but there is, so far as I
can tell, no equivalent for output files. How difficult would it be to add
such a scheme function/list?
As I see it, LilyPond obviously know
ted.
IR says:
"
gap-count (integer)
Number of gapped beams for tremolo.
"
Thus at least IR is plain wrong and the question is: bug or feature?
Cheers,
Harm
Il giorno lun 9 set 2019 alle 11:59, Urs Liska
ha scritto:
I've finally managed to do some work on Frescobaldi again, picking up
on a completely new "Document Fonts" dialog I had started some time
ago. I think it is approaching a point where it can be merged, and
therefore I'd be glad about pe
field, plus there's a text sample for every font.
Notation fonts can be listed and (to some extent) managed by "installing" and
"removing" them from a given LilyPond installation. An option to download new
fonts will be added later.
The main feature of the dialog is to gen
Hi Kieren,
Your version did help me enormously. Thank you very much.
The whole score is now what it should be.
I usually work with separate voices to be collected in the score, but with the
extra BC-line I could not get it right. I spent most of this day wondering
what the hell the error messa
Hi Robert,
> Whatever I tried, it stubbornly kept "bass" for both staves. What am I doing
> wrong?
There’s a spurious instrument name setting. But given the structure of your
code, it’s very hard to spot.
Might I suggest putting all of your note code into variables, then building
them togethe
Hello,
I have finally managed to apply your recommendations in my score.
On the whole they work out very well except for one error that I have not been
able to get rid of: to change the staff name of the upper staff in "cantus".
Whatever I tried, it stubbornly kept "bass" for both staves. What
Good morning,
Many thanks for your quick reactions and helpful advice.
Because it will take me a while to try these solutions in my score, and because
at this moment I am in rural France where my internet connection is very buggy
and unstable --- in a few minutes I may be disconnected till lat
On 4/28/2018 4:33 PM, Torsten Hämmerle wrote:
Ahem,
If you want to get rid of the "connecting line", it might helpful to know
that this line is called
SystemStartBar
and it lives in the Score context.
So,
\omit Score.SystemStartBar
will make it disappear without SVG manipulation.
HTH,
Torsten
Ahem,
If you want to get rid of the "connecting line", it might helpful to know
that this line is called
SystemStartBar
and it lives in the Score context.
So,
\omit Score.SystemStartBar
will make it disappear without SVG manipulation.
HTH,
Torsten
--
Sent from: http://lilypond.1069038.n5.na
On 4/28/2018 1:08 PM, Noeck wrote:
Dear Robert,
I don't know this notation. So my advice is probably not the best solution.
Entering FiguredBass1 and FiguredBass2 did not give me anything but
error messages
You mean \new FiguredBass1 ? You cannot just invent context names. But
you can stack s
Robert,
it's easier to help you if you provide a Minimal Working Example,
otherwise it's hard to know what exactly you tried.
Anyway: It's not problem at all to create multiple
FiguredBass-environments. The line between them is a bit more tricky; I
once used a rhythm staff with all bar lines
Dear Robert,
I don't know this notation. So my advice is probably not the best solution.
> Entering FiguredBass1 and FiguredBass2 did not give me anything but
> error messages
You mean \new FiguredBass1 ? You cannot just invent context names. But
you can stack several contexts of the same type.
Dear all,
I am asked to add to psalm-setting two different figured bass lines, separated
by a line and with, at the beginning of the first bar, the words "Pretonal" and
"Tonal", as can be seen in the screenshot:
Entering FiguredBass1 and FiguredBass2 did not give me anything but error
messag
Il giorno ven 17 mar 2017 alle 9:06, Urs Liska ha
scritto:
Hi all,
there's a pull request for Frescobaldi, submitted by a new
contributor (https://github.com/wbsoft/frescobaldi/pull/905), and I
have a problem with it: The contributor states it works for him, I
can't see anything wrong in
Hi all,
there's a pull request for Frescobaldi, submitted by a new contributor
(https://github.com/wbsoft/frescobaldi/pull/905), and I have a problem
with it: The contributor states it works for him, I can't see anything
wrong in the code, but it doesn't work for me. So I'd be happy if others
coul
Thanks David,
>> %%%
>> \version "2.19.57"
>>
>> { <\single \hideNotes b' f'> }
>> %%%
>>
>> As expected the b is not displayed. But why does the stem of f vanish
>> (completely) as well?
>> Is that intended (why?) or is that a bug?
>> And if it's intended how do I get the f's stem back?
>
> The
Michael Gerdau writes:
> Hi list,
>
> I just stumbled about the following:
>
> %%%
> \version "2.19.57"
>
> { <\single \hideNotes b' f'> }
> %%%
>
> As expected the b is not displayed. But why does the stem of f vanish
> (completely) as well?
> Is that intended (why?) or is that a bug?
> And if i
Hi list,
I just stumbled about the following:
%%%
\version "2.19.57"
{ <\single \hideNotes b' f'> }
%%%
As expected the b is not displayed. But why does the stem of f vanish
(completely) as well?
Is that intended (why?) or is that a bug?
And if it's intended how do I get the f's stem back?
Kin
Hi Harm,
> in CueVoice stem length _is_ shortened.
Well, that’s a relief! =)
> But it in your example it has no effect, because 'no-stem-extend is #f
Hmmm… Should that be the default?
> Try it with
Works great. Thanks!
> For reduced sizes in a common Voice we nowadays have `magnifyMusic',
>
2016-02-07 17:11 GMT+01:00 Kieren MacMillan :
> Hello all,
>
> I searched the issue tracker and LSR, but couldn’t find anything related to
> this.
> (Apologies if I missed it.)
>
> Please consider the output of following snippet:
>
> %%% BEGIN SNIPPET
> \version "2.19.35"
>
> cees = { c'8 8 8 8 }
Hello all,
I searched the issue tracker and LSR, but couldn’t find anything related to
this.
(Apologies if I missed it.)
Please consider the output of following snippet:
%%% BEGIN SNIPPET
\version "2.19.35"
cees = { c'8 8 8 8 }
tinyteeny = {
\time 2/4
\cees
\tiny \cees
\teeny \cees
. Februar 2016 23:02:10 MEZ, schrieb Kieren MacMillan
:
>Dear David and Jan-Peter,
>
>It appears that the absFontSize feature I sponsored a few years ago —
>and employ in absolutely [ha!] every score I engrave — has not been
>rolled into the main Lilypond codebase.
>
>Is that
Dear David and Jan-Peter,
It appears that the absFontSize feature I sponsored a few years ago — and
employ in absolutely [ha!] every score I engrave — has not been rolled into the
main Lilypond codebase.
Is that true?
If so, what is stopping it from being added?
I think users could benefit
> I've moved all development of this to a GitHub repository here:
https://github.com/davidnalesnik/lilypond-roman-numeral-tool. There are
significant improvements over what you'll find in the archives. Ability to
do altered figures is one of the things I've added.
It's exactly what I need! Thank y
On Wed, Dec 9, 2015 at 6:21 PM, David Nalesnik
wrote:
>
>
> I've moved all development of this to a GitHub repository here:
> https://github.com/davidnalesnik/lilypond-roman-numeral-tool. There are
> significant improvements over what you'll find in the archives. Ability to
> do altered figures i
Hi Ferdinand,
On Wed, Dec 9, 2015 at 5:23 PM, Ferdinand Grau wrote:
> The problem is that I severely lack the ability to typest chords like the
> ones in the attachment: II6/5/♭, II7/♭5, etc. Interestingly enough,
> arbitrary number of inversion digits was supported by earlier version of
> \rN (
The problem is that I severely lack the ability to typest chords like the
ones in the attachment: II6/5/♭, II7/♭5, etc. Interestingly enough,
arbitrary number of inversion digits was supported by earlier version of
\rN (https://lists.gnu.org/archive/html/lilypond-user/2014-11/msg00470.html).
but it
Hi James,
> I have opened
> https://sourceforge.net/p/testlilyissues/issues/4658/
Thanks. (I’m getting a 404 error at the moment, but I assume that’s temporary.)
Cheers,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenm
On 11/11/15 02:58, Kieren MacMillan wrote:
> Hello all,
>
> Rather than having to \revert an \override (or set of \override-s), might it
> be possible to set an optional duration for which the override would be in
> effect? e.g.
>
> \temporary #’(10 1/8) \override LyricText.extra-offset = #’(0
On 11.11.2015 14:08, Johan Vromans wrote:
On Wed, 11 Nov 2015 13:42:58 +0100
David Kastrup wrote:
But if you have to close the group anyway with a brace, where is the
point in not just doing a music function doing
{ \temporary $xxx ... \undo $xxx }
I do not see how to cope with the $xxx. Cou
Hi Kieren, et.al.,
David came up with a nice solution :)
To get such a function with the edition-engraver, we will have to
integrate some other piece. The proposed solution works horizontal in
time, while the edition-engraver is triggered "vertically" in time. So
there has to be an event, whic
Hi David,
As always, a wonderful solution. Thank you!
%%% SNIPPET BEGINS
\version "2.19.30"
ranged =
#(define-music-function (overrides music) (ly:music? ly:music?)
#{ \temporary $overrides #music \undo $overrides #})
{
c d e f
\ranged \override NoteHead.color = #red { c d e f }
c d e
Kieren MacMillan writes:
> Hi David,
>
>> But if you have to close the group anyway with a brace, where is the
>> point in not just doing a music function doing
>>
>> { \temporary $xxx ... \undo $xxx }
>
> Wouldn’t one have to create a separate music function for each possible tweak?
> If not, t
On Wed, 11 Nov 2015 13:42:58 +0100
David Kastrup wrote:
> But if you have to close the group anyway with a brace, where is the
> point in not just doing a music function doing
>
> { \temporary $xxx ... \undo $xxx }
I do not see how to cope with the $xxx. Could you give an example
imlememtation
Hi David,
> But if you have to close the group anyway with a brace, where is the
> point in not just doing a music function doing
>
> { \temporary $xxx ... \undo $xxx }
Wouldn’t one have to create a separate music function for each possible tweak?
If not, then there is, as you say, no point.
Th
Kieren MacMillan writes:
> Hi Johan,
>
>> I'd hate the counting of measures…
>
> Me, too… but…?
>
>> { \local LyricText.extra-offset = #’(0 . -1) … }
>
> Ah! Even better.
That looks like
\new Lyrics \with { \override LyricText.extra-offset = #'(0 . -1) }
{ ... }
with the main Lyrics packed in
Hi Johan,
> I'd hate the counting of measures…
Me, too… but…?
> { \local LyricText.extra-offset = #’(0 . -1) … }
Ah! Even better.
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
_
On Tue, 10 Nov 2015 21:58:10 -0500
Kieren MacMillan wrote:
> Rather than having to \revert an \override (or set of \override-s), might
> it be possible to set an optional duration for which the override would
> be in effect? e.g.
>
> \temporary #’(10 1/8) \override
>
> would lower the Lyric
1 - 100 of 691 matches
Mail list logo
