I would add it to:
filetype off
set runtimepath+=/usr/local/share/lilypond/current/vim/
filetype on
syntax on
maybe:
set nocompatible
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Fedora 19 comes with guile 2. However, it is possible to have both
guile 2 and guile 1.8.8 installed but the default is to point to guile
2.
configure does not complain when it finds guile 2 and the build
process can continue although the final lilypond binary fails to
compile lilypond sources.
It is due to a bug in ghostscript. I submitted a bug report 29th of
Nov (2012) and it is now corrected. But it will take time until the
new version of ghostscript comes to everybody's distribution.
Do you have a patch to go with this? We could put the patch into GUB
right away.
Do you mean
I suspect URL:http://code.google.com/p/lilypond/issues/detail?id=2985,
and if that is the problem, it would likely go away if you used some
non-Latin-1 characters, like ἦ or so in the same string as well.
It is due to a bug in ghostscript. I submitted a bug report 29th of
Nov (2012) and it is
Hi, it seems, that simple repeat with command \repeat volta has no effect
on midi output.
This is explained in the doc:
http://www.lilypond.org/doc/v2.16/Documentation/notation/repeats-in-midi
Frédéric
___
bug-lilypond mailing list
Hello, I've followed your example on full measure rests to try and create
a 23/16 measure rest, however this doesn't work, whereas your 13/8
example does :/ Complete code below.
23/16 works fine but you made a mistake:
replace R1*23/16 | R1*13/8*12 | by R1*23/16 | R1*23/16*12 |
Cheers,
I am not sure this email has been seen.
I have proposed a patch for issue 2563.
Cheers,
Frédéric
-- Forwarded message --
From: Frédéric Bron frederic.b...@m4x.org
Date: 2012/7/12
Subject: patch proposed for issue 2563
To: bug-lilypond bug-lilypond@gnu.org
in the tracker
I transfer this email to bug-lilypond because I got no answer on lilypond-devel.
Cheers,
Frédéric
-- Forwarded message --
Subject: error while running make check (g++ 4.7.0): missing include of unistd.h
I wanted to run regression tests and compare before and after a change.
proposed patch in the tracker for issue 2401.
Frédéric
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
in the tracker.
Frédéric
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Not sure about translations. But if it is one over the denominator in
English, you should _write_ one over the denominator rather than the
one over denominator.
http://code.google.com/p/lilypond/issues/detail?id=2644
new patch added to the tracker.
Frédéric
Please find a patch attached to this email to correct an inconsistency
about baseMoment in the documentation.
I think baseMoment is one over the denominator, not one over the numerator.
Modified English and French.
Regards,
Frédéric
0001-fixed-documentation-inconsistency-about-baseMoment.patch
Not sure about translations. But if it is one over the denominator in
English, you should _write_ one over the denominator rather than the
one over denominator. I agree that it was both grammatically as well
as mathematically wrong before, but why not fix both while you are at
it?
As I am
This is normal behaviour.
\cadenzaOn contains \set Timing.autoBeaming = ##f (which was maybe not
the case in 2.12).
Yes, I have seen this in the Changes.
Manual beaming [ ] behaves like slur ( ) because of the melisma rules
(which are based on common engraving practices), see NR 2.1.1
In the following code, no word is placed below the second eight note.
Commenting \cadenzaOn or removing manual beaming [] works fine.
Manual beaming [ ] behaves like slur ( ).
This worked in previous versions.
\version 2.14.0
\score {
\context Voice = notes \relative {
I suppose that a short-term solution would be to simply push the
@bs{} patch. It feels a bit icky, but that's hardly the ickiest
part of lilypond development. And it's inconsistent to kick up a
fuss now when some other languages already do this.
Well, the @example immediately above the
I tried to 'git am' the patch file and got an error 'Patch format detection
failed'.
I've downloaded it via three different methods (in case it was my mail
client) but I cannot apply this to push.
Sorry, it just produced with diff -u
The one attached is a proper git patch.
Frédéric
Patch attached.
My build suite is broken, I cannot test but it looks straightforward
as the solution was already used in some translations.
Frédéric
download.patch
Description: Binary data
___
bug-lilypond mailing list
bug-lilypond@gnu.org
I really don't think that we should start manually changing /
characters in filenames. Can't we find a more general solution
for this?
Some langage files have the following instead:
@code{/Applications/}
When I display the French version for instance, this is replaced by
C:\Program Files.
Is
I've just made a more extensive change to the LM so it accords with the new
behaviour in 2.13.
Thanks for answers. I have checked the new documentation for 2.13.55
and it corresponds to the output.
I have built an exhaustive example showing the placement of all
objects. Maybe you could include
It could go in the Notation Reference with some introductory
text, but I prefer Phil's suggestion to include this in the
regression test suite.
However we choose to use it, many thanks for the contribution!
You are welcome.
I have a remaining question: why have TextScript and
Could this lead to undefined behavior? i.e. sometimes have TextScript
above MultiMeasureRestText and sometimes the contrary?
Yes. I believe in this case it depends on the order
in which they appear in the .ly file.
What order would you like?
I have tried to inverse the order in the .ly
I believe the documentation specifies that the Rehearsal, Metronome and Bar
Number marks normally live in the Score context; to put them into your
order, you need to take them out of Score and put them into Staff, per the
note in NR 4.4.3.
I know that and I am not saying the contrary but the
Although outside-staff-priorities seem to not have changed between
2.12 and 2.13 (I compared roughtly define-grobs.scm), there is
something strange:
In the example below, the vertical placement of OttavaBracket,
TextScript and MetronomeMark is not in the same order with 2.12.3 and
2.13.54 although
2.13.54
There is an issue with Notation Manual in big format:
http://lilypond.org/doc/v2.13/Documentation/notation-big-page.html
when clicking on an item of the table of contents (with firefox 3.6.15
on Windows), I get an error message:
Erreur d'encodage de contenu. La page que vous essayez de
I noticed that convert-ly does not converts auto beaming settings.
Didn't convert-ly give you a message that said you needed to change it
manually?
I have run conver-ly for many files so that I did not see the message!
It would have been nice to have a rule that added a comment in the
file
Let's go for that, I will prepare a patch.
Patch available here: http://code.google.com/p/lilypond/issues/detail?id=1029
Frédéric
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
1. short-term fix: change thumb definition (avoid-slur . around
+ add other Fingering properties that also exists for Script),
but keeping \thumb engraved by Script_engraver.
Here is what I think could be fine:
(thumb
. (
(script-stencil . (feta . (thumb . thumb)))
When using \tag inside a music expression that is used as argument of
\partcombine, some notes (unrelated to the \tag command) are not
printed anymore.
In the following example, the last c of upper voice should be
printed but is not.
Happens with 2.12.2 and 2.13.6.
Frédéric
music = {
I've brought said backlog down to one week or so. I can deal with
Frédéric's report, but there are older (more complex) reports that I'd
like to deal with first.
OK, sorry for pushing, I just wanted to be sure it was not lost.
Thanks for taking care of it, even if it is in one week, Frédéric
When using \tag inside a music expression that is used as argument of
\partcombine, some notes (unrelated to the \tag command) are not
printed anymore.
In the following example, the last c of upper voice should be
printed but is not.
Happens with 2.12.2 and 2.13.6.
Frédéric
music = {
\set
Since the \key command still works at the Staff level (both technically in
LilyPond and musically, since there's no notation available to specify
separate key signatures for separate voices within a stave), I clearly see
it as a bug if the Staff key isn't seen by each Voice.
What if, at the
Under this premise, I think it makes sense to inherit the key signature.
Now if we have _within_ a voice { xxx } \\ { yyy } , what does this
mean? Since the purpose of voice accidental style is to write stuff
that several different people read, this corresponds to splitting a
tenor voice
Here is my first post:
In voice style, when switching from one voice to two voices, the
program writes too much accidentals.
This example demonstrates the problem (2.12.2 and 2.13.6): the second
bes should not have a written flat.
\relative c'' {
#(set-accidental-style 'voice)
Sorry, I got lost in the discussion. Can you help me updating the bug report?
Here is my first post:
In voice style, when switching from one voice to two voices, the
program writes too much accidentals.
This example demonstrates the problem (2.12.2 and 2.13.6): the second
bes should not have a
1. can somebody feed the bug tracker with this bug?
2. can somebody give me some clue to help me fix the bug, if I can...
For example, I suspect that the following line returns the wrong key
signature but how can I print what is in local-key-sig?
(local-key-sig (ly:context-property context
In voice style, when switching from one voice to two voices, the
program writes too much accidentals.
This example demonstrates the problem (2.12.2 and 2.13.6): the second
bes should not have a written flat.
\relative c'' {
#(set-accidental-style 'voice)
\key f \major
bes1
Hmm, forget this, since it doesn't make any sense. It seems the new
voice behaves as if there's no key signature, so there's still a
problem.
Yes, because this does not work either:
\relative c'' {
#(set-accidental-style 'voice)
\key f \major
bes1
{ \voiceOne d }
\new Voice {
Trying to narrow down the problem to a simple example, which follows, showed
that removing the
\context
{
\Staff
\consists Mark_engraver
}
construct solves the problem.
I do not remember where does this construct came from, the file I am working
on went
2.10.19 windows
Strange error message for a missing end curly brace }:
Traitement de « bug.ly »
Analyse syntaxique...
d:/Softs/LilyPond/usr/bin/../share/lilypond/current/ly/init.ly:32:0:
ERREUR : syntax error, unexpected SCM_TOKEN
#(if (and (ly:get-option 'old-relative)
ERREUR : erreur sur
Congratulations, I have never succeeded! I am highly interested in a
cygwin package.
Regards,
F. Bron
Luis Rivera a écrit :
Hello,
I managed to compile and install Ly 2.8.6 on Cygwin; however, the exe
doesn't run, and there are a few quirks I'd like to report.
Can you try to press the Details button and try to find out more
exactly what happens where it hangs.
Details - blank window.
I suspect that it is because I am not administrator of my computer?
F. Bron
___
bug-lilypond mailing list
In the documentation package (2.8.5 and earlier), the images of music
examples are symbolic links to other files. For example
Documentation/user/lilypond/lily-1919872861.png is a link to
Documentation/user/lily-1919872861.png). This does not work properly
with Windows: the browser does not
Using 2.8.4 on Windows XP:
The windows uninstaller does not work (not only with 2.8.4, it started
earlier): the progess bar moves very quickly around 50% and the program
never finishes. Note that I do not install in default directories but in
D:\Softs\Lilypond and I am not administrator of my
To write French characters, you need a text editor that can read/write
UTF-8 (unicode with 8 bits for ASCII char and 16 bits for others) like
vim or emacs or possibly some others.
If you cannot find such an editor, please use the attached file and copy
paste the 2 bytes characters, even if they
Please write in English on this list.
You can use 2.6.5 on Windows and it should work.
What do you exactly mean by it does not work?.
Fred
Gilles Quesne a écrit :
Bonjour à toute l'équipe de Lilypond.
Retraité depuis peu de l'enseignement, j'enseignais les mathématiques au
collège,musicien
The binary of python has disappeared from the bin directory in 2.7.26-2
for Windows. Then it is not possible to run convert-ly.
Fred
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
When using the trick to add staccato to all notes, there is a bad
interference with \relative.
In the example given in the doc, just replace :
a b \applymusic #(lambda (x) (music-map add-staccato x)) { c c }
by
a b \applymusic #(lambda (x) (music-map add-staccato x)) { c' c, }
and you will
:
On Thursday 22 December 2005 21.14, Frédéric Bron wrote:
With this small example, I get an error and wrong output (graces notes
grouped in a chord with the next note!).
Note that if you just remove \clef treble, the bug disappears!!
This has to do with implicit creation of contexts. Try adding
OK, it does not work in 2.6.4 but it is fine in 2.7.17. You probably
tried on a development version.
I will wait for 2.8.0 then.
Fred.
Erik Sandberg wrote:
On Friday 23 December 2005 09.39, Frédéric Bron wrote:
I have tried to add \new Voice { ... } or \context Voice = 1
Same problem as the one I reported. Also solved in development version
2.7.17 (and probably later).
Fred
Gilles wrote:
Hi.
Running lilypond 2.6.3 on the following:
%---
\version 2.6.3
theMusic = \relative c''' {
\time 4/4
\acciaccatura g16 f1 |
f1 |
}
\score {
{
\key a \minor
With this small example, I get an error and wrong output (graces notes
grouped in a chord with the next note!).
Note that if you just remove \clef treble, the bug disappears!!
Fred
\version 2.6.4
\include english.ly
\new Staff {
\clef treble
\relative {
Very small error: in the following please replace aise by raise.
\lower amount (number) arg (markup)
Lower arg, by the distance amount. A negative amount indicates
raising, see also aise.
Fred
___
bug-lilypond mailing list
bug-lilypond@gnu.org
In the following example, Solo should be written above the first note.
Note that if the crescendo is removed, everything is fine.
\version 2.6.4
\include english.ly
\score {
\partcombine
{
r4 c'\ r d'
e'\!\f
}
{
R1*1
In the following example, the crescendo has airpins instead of text.
Everything is fine if \partcombine is replaced by polyphony ... \\
... .
\version 2.6.4
\include english.ly
\score {
\partcombine
{
\setTextCresc
r4 c'\ r d'
I have seen this also but only when I select some instrument that do not
play for the same period of time which is not the case for the complete
score. So I do not think it is a bug.
Fred
[EMAIL PROTECTED] wrote:
The following is a bug I noticed several versions ago (whatever 2.7 version
I
In the doc, please remove one also in Voice contexts can also also be
instantiated manually...
Frédéric
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
I have spent some time to understand what should be the pitch in
\transposition pitch. In particular, I found difficult to understand
what octave to use.
I would like to propose to add a comment that could be something like:
The pitch that should be given to \transposition corresponds to the
\repeat unfold 15 { g'2 g'~ } g'1
}
}
F. Bron
Erik Sandberg wrote:
On Monday 05 December 2005 08.42, Frédéric Bron wrote:
Using lilypond 2.6.4 on Windows (not cygwin)
In the following
In the following example, the ties at the beginning of the second
system
are not typeset correctly. It seems that the problem comes from the
different key of the first instrument: if you remove the \key af
\major, everythings looks fine. I had some difficulties to rediuce it
to such a small
Using lilypond 2.6.4 on Windows (not cygwin)
In the following example, the ties at the beginning of the second system
are not typeset correctly. It seems that the problem comes from the
different key of the first instrument: if you remove the \key af
\major, everythings looks fine. I had some
Using lilypond 2.6.4 on Windows (not cygwin)
In the following fragment, the flat in front of the last d flat should
not be cautionnary (in parenthesis).
\version 2.6.4
\include english.ly
\new Staff {
#(set-accidental-style 'modern-cautionary)
\clef G
\key c \major
62 matches
Mail list logo
