Le 14/06/2021 à 08:53, 6d8fd379d7b54...@posteo.net a écrit :
Hi,
I got confused by the Octave Checks documentation:
https://lilypond.org/doc/v2.22/Documentation/notation-big-page#octave-checks
https://gitlab.com/lilypond/lilypond/-/blob/d408cdc68629ef6df72de0d0ace9c460016565f8/Documentation/en/
Hi,
I got confused by the Octave Checks documentation:
https://lilypond.org/doc/v2.22/Documentation/notation-big-page#octave-checks
https://gitlab.com/lilypond/lilypond/-/blob/d408cdc68629ef6df72de0d0ace9c460016565f8/Documentation/en/notation/pitches.itely#L706
I thought the ='4 was some special
efore-line-breaking")
}
}
{
\override NoteHead.color = "red"
\override NoteHead.X-offset = 3.14159
c
\tweak color "blue"
\tweak X-offset -1
e
}
This makes two overrides to NoteHead properties, one
to color and one to X-offset, and shows their values
at
> On Tue, Jan 29, 2019, 15:07 Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com wrote:
>
>> 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 "\paren
.@gmail.com wrote:
> 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 &
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
&
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&
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
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
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, Le
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
https://l
"Simon Albrecht" wrote in message
news:56536880.1060...@mail.de...
\version "2.19.31"
{
a'8
\once\override Staff.Clef.X-extent = #'(0 . .8)
\clef bass a, b, c
\clef treble a'8
\once\override Staff.Clef.X-extent = #'(0 . 0)
\clef bass a, b, c
}
%%
Yours, Simon
I presume t
\version "2.19.31"
{
a'8
\once\override Staff.Clef.X-extent = #'(0 . .8)
\clef bass a, b, c
\clef treble a'8
\once\override Staff.Clef.X-extent = #'(0 . 0)
\clef bass a, b, c
}
%%
Yours, Simon
___
bug-lilypond mailing list
bug-lilyp
Hello,
in the following example, the tweak on one clef spills over to the next:
%
\version "2.19.31"
{
\clef treble a'8
\tweak Clef.X-extent #'(0 . 0)
\clef bass a, b, c
\clef treble a'4
}
%
Yours, Simon
__
<https://sourceforge.net/p/testlilyissues/issues/4657/>
On 30.10.2015 14:28, Simon Albrecht wrote:
Hello,
if a beam is present, tweaking rest.staff-position remains without
effect:
%%%
\version "2.19.28"
{
\voiceTwo
f'16[ \tweak sta
On 30.10.2015 14:28, Simon Albrecht wrote:
Hello,
if a beam is present, tweaking rest.staff-position remains without effect:
Should’ve added that \once\override works fine.
%%%
\version "2.19.28"
{
\voiceTwo
f'16[ \tweak staff-position 10 r16 16]
}
%%%
Hello,
if a beam is present, tweaking rest.staff-position remains without effect:
%%%
\version "2.19.28"
{
\voiceTwo
f'16[ \tweak staff-position 10 r16 16]
}
%%%
Output attached.
Yours, Simon
___
bug-lilypo
On 18/02/15 17:27, Simon Albrecht wrote:
Hello list,
it seems that the \tweak command does not have any effect on multi
measure rests, neither with nor without specifying the grob:
\version "2.19.8"
{ \tweak MultiMeasureRest.color #red R1 \tweak color #red R1 }
I couldn'
Hello list,
it seems that the \tweak command does not have any effect on multi
measure rests, neither with nor without specifying the grob:
\version "2.19.8"
{ \tweak MultiMeasureRest.color #red R1 \tweak color #red R1 }
I couldn't find an entry in the issue tracker, nor
David Kastrup writes:
> Nick Payne writes:
>
>> I was trying to allocate a tweak command to a variable and eventually
>> managed to get it to work after finding what I needed by a search of
>> the lilypond-user archives (
>> http://lists.gnu.org/archive/html/lilyp
Nick Payne writes:
> I was trying to allocate a tweak command to a variable and eventually
> managed to get it to work after finding what I needed by a search of
> the lilypond-user archives (
> http://lists.gnu.org/archive/html/lilypond-user/2011-09/msg00279.html).
>
> Howeve
I was trying to allocate a tweak command to a variable and eventually
managed to get it to work after finding what I needed by a search of the
lilypond-user archives (
http://lists.gnu.org/archive/html/lilypond-user/2011-09/msg00279.html).
However, I was initially misled by the NR having a
Updates:
Status: Verified
Comment #7 on issue 2164 by elu...@gmail.com: Learning Manual: Better
explanation with updated example for \once tweak
http://code.google.com/p/lilypond/issues/detail?id=2164
(No comment was entered for this change
Updates:
Status: Fixed
Labels: -Patch-push
Comment #6 on issue 2164 by pkx1...@gmail.com: Learning Manual: Better
explanation with updated example for \once tweak
http://code.google.com/p/lilypond/issues/detail?id=2164
Wed, 4 Jan 2012 08:00:45 + (08:00 +
Updates:
Labels: -Patch-countdown Patch-push
Comment #5 on issue 2164 by colinpkc...@gmail.com: Learning Manual: Better
explanation with updated example for \once tweak
http://code.google.com/p/lilypond/issues/detail?id=2164
Counted down to 20120103, please push
Updates:
Labels: Patch-review
Comment #3 on issue 2164 by lilypond...@gmail.com: Learning Manual: Better
explanation with updated example for \once tweak
http://code.google.com/p/lilypond/issues/detail?id=2164#c3
Patchy the autobot says: LGTM
Comment #2 on issue 2164 by pkx1...@gmail.com: Learning Manual: Better
explanation with updated example for \once tweak
http://code.google.com/p/lilypond/issues/detail?id=2164#c2
Doc: LM adjusted explanation for \once
This is for Tracker issue 2164
As suggested by email on lilypond-user
Updates:
Labels: Patch-new
Comment #1 on issue 2164 by pkx1...@gmail.com: Learning Manual: Better
explanation with updated example for \once tweak
http://code.google.com/p/lilypond/issues/detail?id=2164#c1
Doc: LM adjusted explanation for \once
This is for Tracker issue 2164
As
Status: Started
Owner: pkx1...@gmail.com
Labels: Type-Documentation
New issue 2164 by pkx1...@gmail.com: Learning Manual: Better explanation
with updated example for \once tweak
http://code.google.com/p/lilypond/issues/detail?id=2164
Submitted by
drippingtone+lilyp...@gmail.com
The
Updates:
Status: Accepted
Comment #6 on issue 1789 by philehol...@googlemail.com: \tweak does not
work for changing control-points of any but the first tie in chorded notes
http://code.google.com/p/lilypond/issues/detail?id=1789
(No comment was entered for this change
Updates:
Status: Verified
Comment #3 on issue 1751 by philehol...@googlemail.com: Most analysis
brackets get incorrect event-cause info, breaking point-and-click & \tweak
http://code.google.com/p/lilypond/issues/detail?id=1751
(No comment was entered for this ch
Comment #5 on issue 1789 by k-ohara5...@oco.net: \tweak does not work for
changing control-points of any but the first tie in chorded notes
http://code.google.com/p/lilypond/issues/detail?id=1789
Could you explain what you are trying to tell us?
That the control points looked good enough
Comment #4 on issue 1789 by d...@gnu.org: \tweak does not work for changing
control-points of any but the first tie in chorded notes
http://code.google.com/p/lilypond/issues/detail?id=1789
Could you explain what you are trying to tell us? Tie directions are not
the same as control points
Comment #3 on issue 1789 by k-ohara5...@oco.net: \tweak does not work for
changing control-points of any but the first tie in chorded notes
http://code.google.com/p/lilypond/issues/detail?id=1789
Where is the bug?
{ < c'~ g'~ > q
< c'^~ g'_~ > q }
Attac
Updates:
Summary: \tweak does not work for changing control-points of any but the
first tie in chorded notes
Comment #2 on issue 1789 by d...@gnu.org: \tweak does not work for changing
control-points of any but the first tie in chorded notes
http://code.google.com/p/lilypond/issues/detail
Comment #1 on issue 1789 by reinhold...@gmail.com: \tweak is 'broken' when
trying to tie chorded notes (other than the first note in the chord)
http://code.google.com/p/lilypond/issues/detail?id=1789
This is really a bug with control-points, because changing the color of the
Status: New
Owner:
Labels: Type-Defect Priority-Low
New issue 1789 by pkx1...@gmail.com: \tweak is 'broken' when trying to tie
chorded notes (other than the first note in the chord)
http://code.google.com/p/lilypond/issues/detail?id=1789
Here is the main threa
On 7/24/11 4:12 AM, "-Eluze" wrote:
>>
>> If I run the command above with 2.15.5, I get the output at the bottom.
>> I'm not convinced that's correct.
>>
>> Unbound variable: t
>> < \tweak #'transparent ## c e >
>>
Updates:
Status: Verified
Comment #7 on issue 1733 by philehol...@googlemail.com: \displayLilyMusic
ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
(No comment was entered for this change.)
___
bug-lilypond mailing
lilypond-4 wrote:
>
> If I run the command above with 2.15.5, I get the output at the bottom.
> I'm not convinced that's correct.
>
> Unbound variable: t
> < \tweak #'transparent ## c e >
>
an old question: should it be ##t or just #t?
a small e
Comment #6 on issue 1733 by d...@gnu.org: \displayLilyMusic ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
I don't see anything wrong with the reaction for this input. The input
itself is nonsensical and should use ##t rather than #t.
So I think the probl
Comment #5 on issue 1733 by philehol...@googlemail.com: \displayLilyMusic
ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
If I run the command above with 2.15.5, I get the output at the bottom.
I'm not convinced that's correct.
Processing `1733.ly'
Updates:
Labels: -backport backported fixed_2_14_2
Comment #2 on issue 1751 by carl.d.s...@gmail.com: Most analysis brackets
get incorrect event-cause info, breaking point-and-click & \tweak
http://code.google.com/p/lilypond/issues/detail?id=1751
Backported, with com
Updates:
Status: Fixed
Labels: fixed_2_15_5 backport
Comment #1 on issue 1751 by n.putt...@gmail.com: Most analysis brackets get
incorrect event-cause info, breaking point-and-click & \tweak
http://code.google.com/p/lilypond/issues/detail?id=
Updates:
Labels: -backport fixed_2_15_4
Comment #4 on issue 1733 by carl.d.s...@gmail.com: \displayLilyMusic
ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
Backported
___
bug-lilypond mailing list
bug-lilypond
Status: Started
Owner: n.putt...@gmail.com
Labels: Type-Defect Priority-Medium
New issue 1751 by n.putt...@gmail.com: Most analysis brackets get incorrect
event-cause info, breaking point-and-click & \tweak
http://code.google.com/p/lilypond/issues/detail?id=1751
Since
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_5 backport
Comment #3 on issue 1733 by n.putt...@gmail.com: \displayLilyMusic ignores
\tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
d5766025a1573c709dfa3c9663c1c6b903abec24
Updates:
Labels: -Patch-new Patch-review
Comment #2 on issue 1733 by pkx1...@gmail.com: \displayLilyMusic ignores
\tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
Reg tests pass and no make problems.
___
bug-lilypond mailing
Updates:
Labels: Patch-new
Comment #1 on issue 1733 by n.putt...@gmail.com: \displayLilyMusic ignores
\tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
http://codereview.appspot.com/4645077/
___
bug-lilypond mailing list
bug
Status: Started
Owner: n.putt...@gmail.com
Labels: Type-Enhancement Priority-Medium
New issue 1733 by n.putt...@gmail.com: \displayLilyMusic ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
\displayLilyMusic has no display method to accommodate \tweak; all \tweak
Updates:
Status: Verified
Comment #16 on issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
(No comment was entered for this change
Comment #15 on issue 1180 by percival.music.ca: LM 4.5.3 Real music example
needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Don't consider translations. If the English page is fixed, mark this
verified.
After 2.14, if there's
Comment #14 on issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Sorry, this isn't fixed - at least on the translated versions of the page.
I don't know if
Comment #13 on issue 1180 by percival.music.ca: LM 4.5.3 Real music example
needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Urs: you're not supposed to look at git stuff. Always wait until the next
devel release.
Trevor: I've
Updates:
Status: Fixed
Labels: fixed_2_13_29
Comment #12 on issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Having now seen the pdf output of the newest
OK, then please change the status to fixed.
I can't - I don't have sufficient permissions.
Or is this impossible because of the 1015 issue?
Maybe .. I don't know.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/m
Am 15.07.2010 00:08, schrieb Trevor Daniels:
When (and where) can I see these changes.
So far I am only working with the binary releases, and I don't see
this will be changing shortly ...
The changes are in git for anyone who can build the
docs and will appear in the documentation to 2.13.2
When (and where) can I see these changes.
So far I am only working with the binary releases, and I don't see
this will be changing shortly ...
The changes are in git for anyone who can build the
docs and will appear in the documentation to 2.13.29
when that is released. I guess verification
Comment #11 on issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Sorry, I don't see how I can use these links.
Probably it's sufficient to wait for a release to ev
Comment #10 on issue 1180 by pkx1...@hotmail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=e3ae33d7fc91b79043ced4514a8670ce4d9ed2d0
for the
Comment #9 on issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
When (and where) can I see these changes.
So far I am only working with the binary releases, and I don'
Comment #8 on issue 1180 by tdanielsmusic: LM 4.5.3 Real music example
needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
I've just pushed two commits as fixes for this issue.
The first commit changes the example to use explicitly instant
Comment #7 on issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Hi Trevor,
good point. If I'll see something I'll have a new look at it
Comment #6 on issue 1180 by tdanielsmusic: LM 4.5.3 Real music example
needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Thanks for the hint, Neil.
This example would greatly benefit from being re-written to use explicitly
instantiated
Comment #5 on issue 1180 by n.puttock: LM 4.5.3 Real music example needs
additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
If anybody still wants to work on this, it's a voicing issue: the example
starts off in the main voice, creates severa
Updates:
Blockedon: 1015
Comment #4 on issue 1180 by percival.music.ca: LM 4.5.3 Real music example
needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
A link would help:
http://lilypond.org/doc/v2.13/Documentation/learning/real-music
Updates:
Status: Accepted
Comment #3 on issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
(No comment was entered for this change
Comment #2 on issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Your tweak looks fine at first glance.
But: As I mentioned here
http://lists.gnu.org/archive/html/lilypond
Comment #1 on issue 1180 by pkx1...@hotmail.com: LM 4.5.3 Real music
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
This is the tweak needed after the first 'r2' but before the 'c4.\( '
\once \override PhrasingS
Status: New
Owner:
Labels: Type-Documentation Priority-Low
New issue 1180 by lilyli...@googlemail.com: LM 4.5.3 Real music example
needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180
Chapter 4.5.3 of the LM demonstrates how to tweak a
The next time you send follow-ups to emails on the mailing list, please
keep the same
subject line. It takes some effort to figure out what problem you refer to.
Great that you have figured out the solution yourself and thanks for
sharing it to
others on the mailing list.
/Mats
Alex Shanin
> I'm not top posting.
Things look much better after issuing "\override Beam #'concaveness = #0"
(or some mild value near zero - I use it \once). So the problem is gone.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/l
72 matches
Mail list logo
