Hi Phil
There's some of the history here:
https://sourceforge.net/p/testlilyissues/issues/3687/
Trevor
-- Original Message --
From: "Phil Holmes"
To: bug-lilypond@gnu.org
Sent: 15/11/2017 11:04:17
Subject: Re: a contribution
Betreff: a contribution
Datum: Tue, 14 No
ATM only one Issue has this Status,
https://sourceforge.net/p/testlilyissues/issues/5244/ but there are lots
of other existing issues that could be assigned to it, when someone has
a few spare moments to go through the Issues to find them.
Trevor
---
This email has been checked for viruses by
"Davide Bonetti" wrote 05/01/2018 23:04:01
My sourceforge account is dadebonetti
I ask to be given appropriate permissions to either create, edit and
comment on tracker issues.
I've added you to the Developer list with permission to create, read and
update issues.
W
://sourceforge.net/p/testlilyissues/issues/3687/
I never did get around to finishing this off :( Maybe this is a time to
do it.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi Jean-Marie
This fails : \times 2/3 {c8 d e} ~e8 d16 c16
It is not a bug.
Ties must immediately follow the note. Try
{ \times 2/3 {c8 d e~ } e8 d16 c16 }
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org
ide, here is my sourceforge username :
vicrou
Don't hesitate to get in touch if you need further information.
Hi Victor
Added as a developer, as requested. You should now be able to edit and
create issues. Double-check your issues are not already in the tracker
before a
ny to search through. Also, I rather doubt that there are 1996
issues involving layout-set-staff-size :)
So I still don't know if it's worth while reporting the bug :(
Putting it in quotes brings up just nine:
https://sourceforge.net/p/testlilyissues/issues/search/?q=%22layout-set-staff-s
d to introduce the concepts one at a time, and
deliberately avoided mentioning accidentals in Section 1.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
he migration to Allura…)
As a special encouragement to Jean I've added it :)
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
My first reply, identifying this bug as a regression ...
- Original Message -
From: "Trevor Daniels"
To: "David Stocker" ;
Sent: Sunday, July 08, 2012 12:48 PM
Subject: Re: Repeat Dots and Staff Size in 2.15.41
> Damn! Another regression. (Sorry, David, I&#
My second reply, identifying a possible source of the bug.
Trevor
- Original Message -
From: "Trevor Daniels"
To: "Trevor Daniels" ; "David Stocker"
;
Sent: Sunday, July 08, 2012 12:52 PM
Subject: Re: Repeat Dots and Staff Size in 2.15.41
>
>
id change "\bigger" to "\larger". Is it
this you are thinking of?
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Eluze, you wrote Monday, July 30, 2012 9:19 PM
> Reinhold Kainhofer wrote:
>>
>> On 2012-07-30 19:43, Trevor Daniels wrote:
>>>
>>> Eluze wrote Monday, July 30, 2012 4:01 PM
>>>
>>>> to me both \larger and \smaller are obsolete. or is the
explanation. Have a look at
http://codereview.appspot.com/6453137/
and see what you think of this.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
#x27; {
a'4 b8
\once \override Staff.FootnoteItem #'annotation-line = ##f
\footnote #'(0.0001 . 0.0001) #'TextScript \markup { "Prout has rall." }
\default
e^\markup { "rit." } c4 d4
}
}
It would be better if #'(0 . 0)
David Kastrup wrote Tuesday, August 28, 2012 5:10 PM
> "Trevor Daniels" writes:
>
>> While considering how to add a footnotes to TextScript I came across
>> this, which could be intended or a bug. If the positioning number pair
>> is set to #'(0 . 0)
nds of this piece aren't breakable' programming errors.
Move the terminating slur one note earlier or add a further note at the
end and it works fine.
Why?
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ightly different wording in the Notation
Reference, where there is an example:
http://www.lilypond.org/doc/v2.17/Documentation/notation/aligning-objects
So not a bug.
> Federico
Trevor
___
bug-lilypond mailing list
bug-lilypond
'' {
\time 5/16
c16^"default" c c c c |
%\set Timing.beatStructure = #'(2 3)
\time #'(2 3) 5/16
c16^"(2+3)" c c c c |
%\set Timing.beatStructure = #'(3 2)
\time #'(3 2) 5/16
c16^"(3+2)" c c c c |
}
Trevor
_
ntal centre lines. Other positions are unreachable.
d) The mark's extent is ignored, causing it to be positioned too close to the
following lyric word.
e) The alternative \auto-footnote command would probably work better,
but it gives a syntax error in a Lyrics context.
Trevor
__
David Kastrup wrote Thursday, September 06, 2012 11:49 PM
> David Kastrup writes:
>
>> "Trevor Daniels" writes:
>>
>>> e) The alternative \auto-footnote command would probably work better,
>>> but it gives a syntax error in a Lyrics context.
o:
"As we shall see shortly, the properties of different types of object
are modified by different commands, so it is useful to be able to
recognize the types of objects and properties from their names."
> If not, please add it to issue 2791.
Yes please.
Trevor
__
ed
Thanks. These have already been reported as issue 2777.
http://code.google.com/p/lilypond/issues/detail?id=2777
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
uld be deleted. The section on two-pass spacing was
deleted in
81f5263fa1b6adf642b06970cd34e10d4635495d 2009-08-23
Remove two-pass spacing code and documentation.
but this paragraph seems to have been missed.
Trevor
___
bug-lilypond mailing lis
#x27;s fixed
> in 2.16, then I'll upgrade.
No, it's not fixed in the latest 2.16 or 2.17 releases. It's a serious bug
caused by the way automatic beams are implemented.
A workaround is to manually beam the two e's:
\relative c' { r8 \hideNotes f8 \unHideNotes e8.[ e
ink so)
>>
>> have a look at /ly/engraver-init.ly. You'll see in `Dynamics' no
>> Font_size_engraver.
>
> If this is not a bug then it looks like an enhancement request from Carlo.
> Devs care to comment?
Well, maybe an oversight. It's not a
irpins is correct:
{
% \override Hairpin #'minimum-length = #5
\time 3/4
\clef F
<< e2. { \voiceTwo g4\< g4\> g4\!_"poco cresc." } >> |
d2. |
}
This looks like a bug to me, especially as spacer rests are commonly
used for this purpose.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Trevor Daniels wrote Wednesday, October 10, 2012 10:40 AM
>
> David Kastrup wrote Wednesday, October 10, 2012 10:27 AM
>
>> Rutger Hofman writes:
>>
>>> I meet the following bug:
>>>
>>> \version "2.16.0"
>>>
>&g
ether to classify it as a code bug or a
documentation
issue.
Comments?
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Keith OHara wrote Tuesday, November 06, 2012 4:05 AM
> Trevor Daniels treda.co.uk> writes:
>
>> While browsing the Learning Manual I
>> noticed the last example in Section 3.4.4
>> displays a fault. It is intended to show the
>> use of 'padding to dis
its name would have to be changed.
Bugsquad: could you raise an issue to check the docs for
unnumberedsubsubsecs without nodes using the above as
an example. Thanks.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Trevor Daniels wrote Thursday, November 15, 2012 4:10 PM
> Good suggestion. Done, although the link will take you to
> the start of the numbered section, NR 3.5.1, rather than
> the unnumberedsubsubsec Instrument names, as the latter
> is not a node. Hhm, perhaps it should be, a
Marek Klein wrote Friday, November 16, 2012 7:46 PM
>
>> Trevor Daniels wrote Thursday, November 15, 2012 4:10 PM
>>
>> > Bugsquad: could you raise an issue to check the docs for
>> > unnumberedsubsubsecs without nodes using the above as
>> > an exam
The predefined command \textLengthOn no longer always permits
TextScripts to align. I suspect it broke when the new skylining code
was implemented, but I haven't verified this.
\textLengthOn is defined to be
\override TextScript.extra-spacing-width = #'(0 . 0)
\override TextScript.extra-spac
m...@mikesolomon.org wrote Sunday, December 16, 2012 4:43 PM
> "Trevor Daniels" wrote in message
> news:assp.0697eb5db6.EB380C5E80F04264B181F9417B1D3AAD@TrevorLaptop...
>> The predefined command \textLengthOn no longer always permits
>> TextScripts to align. I s
far too many equally useful candidates.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ition you suggest. Overrides such
> as the one you suggest are (with very few exceptions) not
> included in the main text of Chapter 1 of the Notation Reference;
> there would simply be far too many equally useful candidates.
>
Trevor
___
I'd like to be more
> active in contributing back to the project and this helps me
> understand the best ways.
Great! All offers of help are most welcome. Unfortunately the
procedures we follow are quite daunting to newcomers.
> Arle
Trevor
___
e issue 2522)?
> Two snippets still use s1*0
Yes.
Will you submit a revised snippet, or shall I?
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Federico Bruni wrote Sunday, December 30, 2012 3:00 PM
> Il 30/12/2012 14:06, Trevor Daniels ha scritto:
>
>> Will you submit a revised snippet, or shall I?
>
> Please go ahead.
> I've logged in the LSR website but I cannot modify the snippets. Who
> said that w
ready done it. It was my snippet, so
I could change it easily.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e the time in the measure is calculated modulo the time
signature the position -1/8 is the same as 5/8 in 3/4 time. But -1/8
is at position 5/8 in the /previous/ bar.
The text tries to explain what \partial does, which is count backwards
over the anacrusis. If you set measurePositio
rationals (which
> have "arbitrary precision") and the problem will go away.
Until then we ought to document this as a "Known issue" in NR 1.2.1
under Scaling durations.
Copying to Bug list so bug squad can raise a Doc issue if they agree.
Trevor
___
David Kastrup wrote Friday, January 04, 2013 9:15 AM
> "Trevor Daniels" writes:
>
>> David Kastrup wrote Friday, January 04, 2013 8:21 AM
>>
>>> Oscar Dub writes:
>>>>
>>>> From a user perspective, I thought it might be nice fo
a beam-ending rule is defined in beamExceptions for a longer
> beam-type, use it to determined the valid places where beams may end,
> otherwise
> """
>
> /s/determined/determine
Yup.
Thanks. Will deal with these after an issue has been raised by the bug-squad.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Federico Bruni wrote Sunday, January 06, 2013 4:34 PM
> Il 06/01/2013 17:07, Trevor Daniels ha scritto:
>>> NR 1.2.6, Grace notes, section Known problems:
> Anyway, using a note before the \acciaccatura block in the example would
> make it more clear?
>
> \versi
@bug squad
Could you please raise an issue to enhance the documentation to include
the information in Nicolas's reply below. Thanks.
Trevor
- Original Message -
From: "Nicolas Sceaux"
To: "Christopher R. Maden"
Cc:
Sent: Saturday, January 12, 2013 10:50 A
reakbefore variable inside a \header block that is itself in a
> \score block, to make the top-level \header block titles appear on the first
> page on their own, with the music (defined in the \score block) starting on
> the next."
Thanks, Eluze. I've added this suggestion to the
ht pt) 2)))
> }
>
> \relative c'{
> c d e f g a b c
> }
> %===
>
You're right Nick. Looks like my 'fix' is not acceptable. I'll
investigate further.
Bug Squad: could you please raise a new issue for this.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Trevor Daniels wrote Monday, January 14, 2013 12:17 PM
>
> Nick Payne wrote Monday, January 14, 2013 7:46 AM
>
>> If I use the define fonts example in the documentation at
>> http://lilypond.org/doc/v2.17/Documentation/notation/fonts#entire-document-fonts
>>
>
ocumentation.
>
> At any rate, due to its better mnemonic value (and the availability of
> ly:moment-main and ly:moment-grace also from around that time), I think
> we should preferably aim for the rational form.
I agree.
Bug Squad: please raise an issue for
ly increasing the paging load, but it did
not stop 2.13.14 from crashing in the same way. I'm just about to try it with
the latest released binary before I report.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
s.
Good point, David. Copying to bug list to prompt the bug squad to
raise an issue to document this as a warning in
http://www.lilypond.org/doc/v2.17/Documentation/notation/different-editions-from-one-source#using-tags
Trevor
___
bug-lilypond ma
ering vertically, but in the
examples of piano and guitar music the fingering _is_ all aligned
vertically, even for chords with some notes displaced and chords
with accidentals before some notes.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
a dialogue box, in my case ConTEXT, but after selecting it, it opens a new
file.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
good. And it will, or can be made to, work under Windows within
the bash shell from MinGW. Useful if MS provides your every-day
environment.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
the moment I'm the only one doing that, I think,
and I have my own local variant anyway. What I suggest is you make the
changes you suggest and test them out under Linux, then pass them to me
and I'll see if they work within the MinGW Bash shell under Windows
(well, under Vista a
or down or adding another note gives a correct
placement
^~
_~
~
}
See also http://code.google.com/p/lilypond/issues/detail?id=962
and http://code.google.com/p/lilypond/issues/detail?id=904
and http://code.google.com/p/lilypond/issues/detail?id=141
Trevor
__
y impression I would also make a patch removing
> cg-section.sh and the reference in the CG.
I applied this patch and tried to execute the script within the Bash shell
of MinGW under Windows Vista, with this result:
Trevor@TREVOR-LAPTOP ~/lilypond-git (urs-lilypond-book)
$ scripts/auxiliar/
k.py
> On Linux I found the location by the result of `which lilypond-book`.
> Would that work on Windows too?
which lilypond-book.py works fine in the WinGW Bash shell.
I've just realised in your script you missed off the .py extension,
which would prevent it working.
Trevor
__
ber spending quite some time getting
this set up in Windows. It would probably put off the typical Windows
user.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
they have installed.
That's a reasonable thing to do, but it has no effect on reducing
spam.
> Alternatively, point people directly to the mailing lists.
That's a good suggestion. All the developers are contactable
via the devel list, and anyone can post there via gmane withou
ral
years ago.
> a) Is this intended behaviour? And if yes, shouldn't it be documented?
I don't think it is intended, so it should be recorded as a bug.
Copying to bug list for bug squad.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ication one has to blank/remove _all_ elements of the
> hidden voice: NoteHead, Stem, Flag, Beam, Dot.
> So the example should be rewritten (taking the decision on a) into account.
> If we find an agreement on a) I can do that and provide a patch
OK, but just submit a replacement snippet to the
Urs Liska wrote Monday, April 29, 2013 4:14 PM
> Am 29.04.2013 16:57, schrieb Trevor Daniels:
>> This snippet is in the LSR, so changes should be made by amending the
>> snippet there, otherwise it remains wrong in the LSR.
>
> Do I recall correctly having read that _n
Urs Liska wrote Monday, April 29, 2013 3:50 PM
> Am 29.04.2013 16:46, schrieb Trevor Daniels:
>
>> Urs Liska wrote Monday, April 29, 2013 3:02 PM
>>
>>> The NR (1.2.3 "Displaying Rhythms") states that time signatures "are
>>> printed at the b
ited with return code 3.
Under Windows Vista Home Premium and LilyPond 2.17.17 this gives:
> Processing `test.ly'
> Parsing...
> This application has requested the Runtime to terminate it in an unusual way.
> Please contact the application's support team for more information.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e, should I wait for someone
> on the bug squad to add a tracker issue, or should I add it
> myself?
Add it yourself. The bug squad's responsibility is to make sure reported
bugs don't get ignored by adding trackers if no developer has done so.
They and developers together raise tracke
ity-of-objects#index-layers
for details.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Eluze wrote Monday, July 29, 2013 12:42 PM
> Trevor Daniels wrote
>> The order in which grobs _in the same layer_ are placed is indeterminate,
>> but this can be controlled by setting the 'layer property. See
>>
>> http://www.lilypond.org/doc/v2.17/Documentatio
>> I propose that we remove string addition from assignments. It's
>> unlikely anybody was aware of it in the last 10 years, and it's not
>> like it is documented.
>
> +1
+1
Trevor
___
bug-lilypond maili
would like to trawl this for new tracker items?
Trevor
- Original Message -
From: "Curt"
To: "Lilypond-User List"
Sent: Friday, September 13, 2013 4:54 AM
Subject: film score example
> Hi all -
>
> About a year ago, several of you answered questions of
command
I see there are several node names in the documentation that include
native backslashes, but only the one noted above is used in a
reference across manuals. I'll fix ref_check.py to check for backslash
in note names to give a warning, and amend all the instances
ent 1 12)
This can be used to override Lily's estimation by setting a more suitable value
if only a small number of short notes are present.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
#scaling-durations
Did you intend to produce 7 g16s followed by 5 fis16s? If so, this is the
way to do it:
\repeat unfold 7 g16
\repeat unfold 5 fis16
See
http://www.lilypond.org/doc/v2.17/Documentation/notation/repeats
Trevor
Jimmie Felidae wrote Monday, October 28, 2013 1:15 PM
>&g
rb+ is intended? It's inside a verbatim block...
I'm not familiar with LaTeX, but this looks like valid input.
It produces the output lower down.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ceTwo \altV }
> >>
> \new Lyrics \lyricsto alt { A B C D E F G H }
>>>
> }
>
> Where are the four c4 notes of the soprano?
This may be a bug. Copying to the bug list.
Removing \lyricsto restores the missing
".
See
http://www.lilypond.org/doc/v2.17/Documentation/notation/techniques-specific-to-lyrics#index-NullVoice
It looks like you have found a further restriction relating to rests.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
bout this and has raised
an issue. Let's wait a little.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e bartype #'(end begin span)
Why not "\defineBarLine normal end start span"?
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Keith OHara wrote Tuesday, December 31, 2013 6:14 AM
> Trevor Daniels treda.co.uk> writes:
>
>> The description of \defineBarLine in NR 1.2.5 does
>> not make it clear that the parameter called bartype
>> doubles as both the name of the barline being defined
>&
Forwarding to bug list ...
- Original Message -
From: "Peter Crighton"
To: "LilyPond Mailing List"
Sent: Wednesday, January 15, 2014 10:27 PM
Subject: Error in documentation
Hello all,
in the documentation about percussion notation it is said that you need to
include the Parenthesis_e
k, so that this moves into
> 2.18.1 as well.
Thanks David. No need for a tracker then.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
This has been fixed already.
Trevor
Phil Holmes wrote Thursday, January 16, 2014 3:25 PM
> Copying to -bugs for an issue.
- Original Message -
From: Peter Crighton
To: LilyPond Mailing List
Sent: Wednesday, January 15, 2014 10:27 PM
Subject: Error in documentat
with git-cl for that patch). Otherwise you are going to have to say
> where you want the @cindex's specifically. Seems as you know how to make
> a patch that you might as well do them and submit them yourself. I don't
> think it is ever a bad
sicalPaperColumn.page-break-permission = ##f
}
}
}
> While examples are helpful of course I am wondering if we could better
> explain some of these functions/commands than having to 'waste' pages of
> webspace and documentation with literal (and verbatim) \pageBreak example
ntences as written are correct? I can't think of any.
> So I like James' suggestion for a more thorough explanation that would
> remove this ambiguity.
Indeed. I think we need a tracker to record this discussion and the
eventual conclusion. Bug Squad
Spanner? I think two examples are sufficient, considering the length of
the NR. That said, I'd be happy to see a simple list added giving _all_ the
spanners for which springs-and-rods has to be set to permit minimum-length to
become effective.
Trevor
__
the
> \markup command, so adding "Moderato" in bold is easy." to "The tutorial
> showed how to add a tempo indication with the \tempo command, so adding
> "Moderato" is easy.
>
> I'm not familiar with the patching process etc. so, if there are no
Trevor Daniels wrote Thursday, May 29, 2014 4:50 PM
>
> Simon Albrecht wrote Thursday, May 29, 2014 11:43 AM
>
>> http://www.lilypond.org/doc/v2.18/Documentation/learning/real-music-example
>>
>> Rereading this, I notice that the "Moderato" marking in t
at
the time the code change is pushed. Remember at the time you push
your changes it is likely that you are the only one who understands what
the implications are re the documentation. It is unlikely any doc editor
will pick this up otherwise.
Trevor
___
b
for Melchior is harmless but unnecessary.
You're right, Timothy. The notes for both Kaspar and Melchior are
entered at the correct sounding pitch, so no transposition is required
for either of them. I'll raise a bug report to fix it.
Trevor
__
Z"
"Enter" to get your usual command prompt back.
Trevor
- Original Message -
From: "Tony Warren"
To:
Sent: Saturday, October 11, 2014 10:13 PM
Subject: LilyPond - Can't get convert-ly to work
>> I'm not top posting.
>
> % I know nothin
Missed copying this to bug-lilypond ...
- Original Message -
From: "Trevor Daniels"
To:
Sent: Saturday, October 11, 2014 11:28 PM
Subject: Re: LilyPond - Can't get convert-ly to work
> Tony
>
> OK, thanks. It seems you have a more recent version of t
Hi Tony
Sorry, it's difficult to test here as I don't have a more recent python
installed. But it seems like you'll have to specify complete paths to the
python interpreter and convert-ly, like this (all one command):
C:\Users\Trevor>"C:/Program Files/LilyPond/usr/bin/
Hi Tony
You copied my instructions incorrectly, missing out "LilyPond" in the path to
"convert-ly" in all these examples.
Try again! It works here.
Trevor
- Original Message -
From: "Tony Warren"
To: "Trevor Daniels"
Sent: Sunday, October
re centered with respect
> % to the notes in the upper staff.
She seems silent on this point, AFAICS.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Thomas Morley wrote Saturday, November 01, 2014 12:05 PM
> Using d1*3/4\rest has a draw-back:
> The rest will change it's position, if \transpose is used.
Copying to bug list. This seems like a bug to me. Do others agree? I can't
see a relevant issue in the
ering.font-size = #-7
\once \offset font-size #-2 Fingering
}
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Urs Liska wrote Saturday, November 01, 2014 9:06 PM
> Am 1. November 2014 21:55:01 MEZ, schrieb Trevor Daniels
> :
>>
>>Thomas Morley wrote Saturday, November 01, 2014 12:05 PM
>>
>>> Using d1*3/4\rest has a draw-back:
>>> The rest will change it'
1 - 100 of 610 matches
Mail list logo
