Re: Double backslash typos in the german documentation

Il giorno mar 29 gen 2019 alle 12:40, Pierre Perol-Schneider ha scritto: Hi BugSquad, At least those paragraphs have backslashes typos: - -

Re: \parenthesize is not affected by \tweak

Le mar. 29 janv. 2019 à 21:26, David Kastrup a écrit : > You are free to invent your own terminology but you cannot expect the > manual to give authoritive answers according to what you choose to call > things. Ouch! But thanks anyway for the clarification. Le mar. 29 janv. 2019 à 21:29,

Re: \parenthesize is not affected by \tweak

I'm an outside party here, but I think you would find some answers by investigating LilyPond's definition of "music object" further; it sounds like you're being tripped up by that. - Nikolai On Tue, Jan 29, 2019, 15:07 Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com wrote: > What I

Re: \parenthesize is not affected by \tweak

Pierre Perol-Schneider writes: > What I mean is that the manual does not says "music object". What I > mean is that "\tweak color #red \parenthesize c' " has the same output > than "\parenthesize \tweak color #red c'" -- weired to me. What I > mean is that in "c'-\tweak color #red -1", #1 is

Re: \parenthesize is not affected by \tweak

What I mean is that the manual does not says "music object". What I mean is that "\tweak color #red \parenthesize c' " has the same output than "\parenthesize \tweak color #red c'" -- weired to me. What I mean is that in "c'-\tweak color #red -1", #1 is not a musical object according to my eyes,

Re: \parenthesize is not affected by \tweak

Pierre Perol-Schneider writes: >> Le mar. 29 janv. 2019 à 17:57, David Kastrup a écrit: >> >>> Pierre Perol-Schneider writes: >>> >>> > Hi Bug Squad, >>> > >>> > %% Snippet: >>> > \version "2.19.82" >>> > { >>> > \tweak color #red \parenthesize c' >>> > %vs: >>> > \tweak

Re: \parenthesize is not affected by \tweak

So? Basically the manual says: " The \tweak command applies to the music object that immediately follows value in the music stream." Considering your answer, do you mean that " \tweak color #red \parenthesize" does not follow the value? Do you mean that parenthizes are no object? I've already

Re: \parenthesize is not affected by \tweak

Pierre Perol-Schneider writes: > Hi Bug Squad, > > %% Snippet: > \version "2.19.82" > { > \tweak color #red \parenthesize c' > %vs: > \tweak ParenthesesItem.color #red \parenthesize c' > } > %% So? The color also does not affect Stem, LedgerLine or Flag by default. Why should it affect

New lilypond 2.21.0 installers

I tried an install into /opt/lilypond. I do not have access to /opt but the folder /opt/lilypond is completely mine. The help says it will install into PREFIX/lilypond, but it also tries to install scripts outside this directory in PREFIX/bin. It refuses to install into an existing (even empty)

Double backslash typos in the german documentation

Hi BugSquad, At least those paragraphs have backslashes typos: - http://lilypond.org/doc/v2.19/Documentation/notation/the-tweak-command.de.html - http://lilypond.org/doc/v2.19/Documentation/notation/set-versus-override.de.html -

\parenthesize is not affected by \tweak

Hi Bug Squad, %% Snippet: \version "2.19.82" { \tweak color #red \parenthesize c' %vs: \tweak ParenthesesItem.color #red \parenthesize c' } %% Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: The Stem of Longa notes is short when Baroque Notehead style is used

On 28.01.19 23:57, Pothárn Imre wrote: %% The stem length of the longa is very short when Baroque NoteHead style is used. That’s because it’s not technically a stem, but part of the notehead glyph. It’s supposed to be like that. Best, Simon ___