On 2020-01-15 6:41 pm, Paolo Prete wrote:
Sorry Aaron, I was not precise in my question.
I need to override a property of StaffSymbol, for every staff, outside
any
music expression/block context. Probably I'm not using the right words
even
now.
But what I need is a sort of a "global" variable
On Thu, Jan 16, 2020 at 3:15 AM Aaron Hill wrote:
> On 2020-01-15 5:15 pm, Paolo Prete wrote:
> > Hello,
> >
> > is it possible to override a property of StaffSymbol outside a
> > \new Staff \with { ... }
> > context?
> >
> > I would like to obtain something like:
> >
> > %%%
> >
On 2020-01-15 5:15 pm, Paolo Prete wrote:
Hello,
is it possible to override a property of StaffSymbol outside a
\new Staff \with { ... }
context?
I would like to obtain something like:
%%%
#scheme-code-for-overriding-staffsymbol-for-all-the-staves-in-the-score
{
c' c' c' c'
Hello,
is it possible to override a property of StaffSymbol outside a
\new Staff \with { ... }
context?
I would like to obtain something like:
%%%
#scheme-code-for-overriding-staffsymbol-for-all-the-staves-in-the-score
{
c' c' c' c'
}
%%%
Thanks
On Thu, Jan 16, 2020 at 1:16 AM Aaron Hill wrote:
> On 2020-01-15 3:59 pm, Paolo Prete wrote
>
> If you are pushing things by small amounts akin to font kerning, then
> collisions are unlikely and extra-offset is often the right tool for the
> job.
>
"If you are pushing things by small amounts a
On Thu, Jan 16, 2020 at 1:31 AM Carl Sorensen wrote:
>
>
> It may be desirable, but it’s not **necessary** to add a warning. At
> this point, I don’t think we have the infrastructure to add the warning.
>
I did not know that. I thought that such a modification was a one-line
change.
Paolo,
Please don’t top-post on this list. Users are expected to interleave their
responses. Please see how other users do it.
From: Paolo Prete
Date: Wednesday, January 15, 2020 at 5:15 PM
To: Carl Sorensen
Cc: Lilypond-User Mailing List
Subject: Re: Distance of a grob from its reference po
On 2020-01-15 3:59 pm, Paolo Prete wrote:
Hi Aaron.
It's not Y-offset that has not to be used. It's the combination \offset
+
Y-offset.
\override SomeGrob.Y-offset can be used (with a ruler, in an
uncomfortably way)
\offset Y-offset is nonsense.
See my reply to Carl, and his reply to me.
Yes, but, it's necessary too to add a *warning* on the Lilypond output.
This is much more clear for the user than the documentation.
On Thu, Jan 16, 2020 at 1:12 AM Carl Sorensen wrote:
>
>
>
>
> *From: *Paolo Prete
> *Date: *Wednesday, January 15, 2020 at 4:45 PM
> *To: *Carl Sorensen
> *Cc:
From: Paolo Prete
Date: Wednesday, January 15, 2020 at 4:45 PM
To: Carl Sorensen
Cc: Lilypond-User Mailing List
Subject: Re: Distance of a grob from its reference point
Thanks to you Carl.
Now, given that it's nonsense to offset an unknown value, I would remove this
property from the offset
Hi Aaron.
It's not Y-offset that has not to be used. It's the combination \offset +
Y-offset.
\override SomeGrob.Y-offset can be used (with a ruler, in an
uncomfortably way)
\offset Y-offset is nonsense.
See my reply to Carl, and his reply to me.
HTH
Paolo
On Thu, Jan 16, 2020 at 12:46 AM Aa
So I figured out how to make and adjust a slur on my own. I am really
wondering though if there is a more elegant way like how simple it is to do
\repeatTie.
\version "2.18.2"
\language "english"
\relative c'' {
\key d \major
\time 4/4
\repeat volta 2 {
d4 d8 d8~ d8 a4 d8(
}
On 2020-01-15 1:57 pm, Paolo Prete wrote:
I quote Carl's words:
"So offset applies to the *estimated* position, and then the spacing
engine
works on the offset+estimated postion and ends up putting things where
it
thinks they belong"
I checked that with the examples made before and it seems
Thanks to you Carl.
Now, given that it's nonsense to offset an unknown value, I would remove
this property from the offset command of Lilypond.
Or at least, if that remove is not easily doable in the internal API, raise
a *heavy* warning that you are using a random/deprecable command.
Please do no
From: Paolo Prete
Date: Wednesday, January 15, 2020 at 4:16 PM
To: Carl Sorensen
Cc: Lilypond-User Mailing List
Subject: Re: Distance of a grob from its reference point
I don't mean that with *broken*. I mean that it's unusable, given that the
values you put inside this function don't corres
I don't mean that with *broken*. I mean that it's unusable, given that the
values you put inside this function don't correspond to anything that you
can measure. Then, pretty random values.
Please note that this doesn't happen with \override SomeGrob.X/Y-offset. In
that case, you can measure the o
From: Paolo Prete
Date: Wednesday, January 15, 2020 at 2:30 PM
To: Carl Sorensen
Cc: Lilypond-User Mailing List
Subject: Re: Distance of a grob from its reference point
Then, do you agree that this causes that the \offset command is broken at least
for the X/Y-offset properties of any grob?
In other words, this means: "if you are lucky enough that the position
estimated by Lilypond is the same that you have in mind, offset will offset
to the quantity that you want. Otherwise it will led to improper placement
(because it will mix the value that it has in mind, with the value that you
h
On 2020-01-15 11:19 am, Pastor Jim Neubauer wrote:
I have an alternative ending that includes a slur. I know there is a
\repeatTie command for ties across alternate endings, but is there
anything
as simple for slurs?
Do you have a MWE you can provide along with possibly a picture or
descript
I quote Carl's words:
"So offset applies to the *estimated* position, and then the spacing engine
works on the offset+estimated postion and ends up putting things where it
thinks they belong"
I checked that with the examples made before and it seems absolutely true.
Then: you have to offset an e
On 2020-01-15 1:21 pm, Paolo Prete wrote:
Without a proper behavior of the "\offset" command you cannot do nor
the
automatic 2) placement, nor a fine tuning.
What is "proper behavior" for \offset to you? It is my understanding
\offset works precisely as documented, but that is a worthless me
Then, do you agree that this causes that the \offset command is broken at
least for the X/Y-offset properties of any grob?
Please correct me if I'm wrong. I would be very happy to see a solution or
an alternative for making *fine tuning* while preserving the
avoid-collisions algo.
In addition, I wo
I have an alternative ending that includes a slur. I know there is a
\repeatTie command for ties across alternate endings, but is there anything
as simple for slurs?
Hi Aaron,
I apologize too if I'm going to use words that can appear a bit rude. This
is only for making the goal clearer, and I state again that without your
great help I could not do my editor.
Now: there's a misunderstanding in your reply too.
I'm not focusing on the *manual* tweaking. The oppos
Do you have "gettext" installed? If not, please install and retry.
Am 15.01.2020 um 18:38 schrieb Knute Snortum:
I didn't get past autogen:
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
configure.ac:905: warning: macro
I didn't get past autogen:
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
configure.ac:905: warning: macro 'AM_GNU_GETTEXT' not found in library
autoreconf: configure.ac: tracing
autoreconf: configure.ac: adding subdirector
Ok, seems that guile-2.2-libs does not provide libguilereadline...
I think the remaining option is to build guile-1.8 from scratch.
First make sure that you have libreadline-dev installed, then, in your
home directory, do:
git clone -b branch_release-1-8 --single-branch
https://git.savannah.gnu.
27 matches
Mail list logo
