Meanwhile, I have compiled make 3.82 and made it available before make
4.0 in the PATH. Then the process goes further up to this point:
$ bin/gub --verbose darwin-x86::cross/gcc
...
building package: linux-x86::cross/gcc
*** Stage: download (cross/gcc, linux-x86)
*** Stage: untar (cross/gcc, lin
>> Then some downloads and later it came to this error saying make is too old:
>>
>> Tail of target/linux-x86/log/glibc-core.log
>> checking for gnumsgfmt... no
>> checking for gmsgfmt... no
>> checking for msgfmt... msgfmt
>> checking version of msgfmt... 0.19.2, ok
>>
Hi,
I am trying to build a cross compiler for darwin on openSUSE.
I downloaded gub (491404f3d602df5f0a86f408d44c7d345eea1a24) and ran:
$ bin/gub --verbose darwin-x86::cross/gcc
I got for example that output:
dependencies[darwin-x86]: system::gcc tools::librestrict tools::make
tools::libtool too
> I'm trying to make something like an `installed-font?'
> scheme procedure, but it looks like I need a c++ procedure
> first. Something like `ly_font_config_get_fonts', exactly
> like the following except it would return the list of fonts
> instead of displaying it. This is from
> font-config-sc
Just in case the lilypond package for fedora is built by the lilypond team:
I have submitted a bug report to fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1005394
vim has been updated from 7.3 to 7.4 but the lilypond package
continues to put its files in /usr/share/vim/vim73.
Frédéric
_
Hi,
> Countdown – September 3rd – 06:00 GMT
> 3513 Enhancement Frederic Bron Push Patch: removed unused code: functions
> that are declared but never defined and stream.hh
> 3511 Enhancement Frederic Bron Push Patch: removed unused header
> tie-column-format.hh
> Countdown – September 6th – 06:0
> I think there is some nominal difference between configuring the
> variables VISUAL or EDITOR for your default editor.
I found what's the issue looking at git-cl code:
def UserEditedLog(starting_text):
editor = os.getenv('EDITOR', 'vi')
(file_handle, filename) = tempfile.mkstemp()
file =
Hi,
When I use git-cl, a pop-up window opens with vim. I typed a message
but couldn't find it anywhere in the issue tracker nor in codereview.
Also, I noticed that git-cl was continuing in the initial terminal
while I was typing the message in the popup window.
What is this message window for? Is i
> Two choices have been mentioned. One is
> 1) void function(std::string);
> 2) void function(const std::string&);
>
> In my professional experience, we usually pass a structure by reference when
> it can't fit in a register. We always use (2) with strings that the function
> will not modify
> Where in the source are the chord symbols for diminished
> (like °) and half-diminished (like ø) defined? Are they
> glyphs, characters, markups or what? I looked but I can't
> find them. And why is the half-diminished sign so much
> bigger than the diminished? Is that intentional?
>
> \chord
When I run the regression tests on master, 3257 run nicely.
Some fail (more than 100, difficult to count on the html page) like
input/regression/context-mod-context.log which produces the output
found below.
Is it an issue on my platform (Fedora 19, g++ 4.8.1, Guile 1.8.8) or
are those normal regre
> Which textbooks would that be?
I think for example at Scott Meyers books (Effective C++, More
effective C++...).
I also read this in the 4th edition (includes C++11) of the C++
programming language (Stroustrup):
"How do we choose among the ways of passing arguments? My rules of thumb are:
[1] U
>> Also I check for compiler warnings but lilypond builds with a lot of
>> compiler warnings which does not help. I think we should try to remove
>> all warnings.
>>
> Such as what?
Maybe there are new in g++ 4.8.1. I get 260 lines of warnings with
make. Here all the warnings I get (duplicates rem
> Have you double-checked the code g++ generates? I should not be overly
> surprised if current versions don't actually do much copying unless
> required.
I know what you mean: "premature optimization is the root of all
evil". But here, it is just following standard practice as recommended
by all
> I would at least normally expect that you do a 'make' to see that it builds
> against current tree - sometimes on the morning of the PATCH countdown, that
> is hard because someone may push a patch and the new tree is merged before
> the test scripts are run and you submitted a patch based on the
> it does a make a make check (reg test comparison) and by default a full make
> doc.
Good point. I am preparing a large patch to replace 'string' by 'const
string&' where it makes sense (to avoid string copy when possible) and
although I am going to run make check my-self before submitting, I am
> Patchy the autobot says: passes tests.
What tests are run by patchy?
- compilation?
- regressions?
Frédéric
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
The following functions are declared in flower/include/std-vector.hh
but defined in flower/std-string.cc:
vector string_split (string str, char c);
string string_join (vector const &strs, const string &infix);
This does not sound logical to me. What about moving the declaration
to std-string.hh?
> git-cl will create the issue for you when you upload your patch. If it
> doesn't, please report it as a bug.
done, issue 3511.
Cheers,
Frédéric
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-deve
> Please read
> http://www.lilypond.org/doc/v2.17/Documentation/contributor-big-page.html#summary-for-experienced-developers
> and start using git-cl. Plain patches posted to -devel tend to get forgotten
> in mist of syntax changes and font standards debates.
I know but there is no issue in the tr
Dear all,
The header tie-column-format.hh is unused. tie-column-format.cc was
removed in 2.10 and removing the header does not prevent lilypond to
build. Only 2 files were including it without actually using it.
Here is the proposed patch.
Frédéric
0001-removed-unused-header-tie-column-format.h
diff --git a/lily/engraver.cc b/lily/engraver.cc
index b8bf123..dfd2c21 100644
--- a/lily/engraver.cc
+++ b/lily/engraver.cc
@@ -105,20 +105,21 @@ LY_DEFINE (ly_set_grob_creation_callback,
"ly:set-grob-creation-callback",
Grob *
Engraver::internal_make_grob (SCM symbol,
diff --git a/flower/include/std-string.hh b/flower/include/std-string.hh
index 5b7d2af..22a5f1b 100644
--- a/flower/include/std-string.hh
+++ b/flower/include/std-string.hh
@@ -35,7 +35,8 @@
#include
+/// ARGH! What does it do in header?!?! It's death, ,
it's total destruction! It burns my e
diff --git a/lily/tie.cc b/lily/tie.cc
index 88d3ee4..227ea3f 100644
--- a/lily/tie.cc
+++ b/lily/tie.cc
@@ -99,20 +99,24 @@ Tie::get_column_rank (Grob *me, Direction d)
{
Grob *col = 0;
Spanner *span = dynamic_cast (me);
if (!span)
col = dynamic_cast (me)->get_column ();
else
> For the programmers, i'd like to ask you to look at the branch
> dev/tie-crusade/comments
> and read the comments we've added to the code together with Franek.
Just in case some would need, we can read all the added comments with:
git diff 5c99661096f110920b86c61e99b460514fcfa9e2^
remotes/origin
> All that looks unrelated to LilyPond and more like a buggy installation
> of gdb
>
> And that one's
> http://sourceware.org/bugzilla/show_bug.cgi?id=15415>
>
> You can get around it by doing
> break main
> run toto.ly
> set argv[0] = "/home/fred/lilypond/build-2013-07-25_11-30/out/bin/lilypond"
>
Hi,
I would like to run lilypond in gdb to understand what happens when using ties.
How can I build lilypond for that?
When I run configure --help, it says it is built with debug info by default:
"--enable-debugging compile with debugging info. Default: on"
But when I run gdb, I get some stran
> Could you make the Guile-1 compatibility a separate issue from 3382,
> which is about tex-info versions?
Oh, sorry that you missed that but Julien fixed this already:
http://code.google.com/p/lilypond/issues/detail?id=3461
Frédéric
___
lilypond-devel
> Could you take a look at readme.txt in Dropbox folder and confirm that
> it explains the
> issue?
Yes, I started from there.
I also read the proposed ideas in "notes about solution.txt" but I
admit that it is difficult to understand for a novice to the lilypond
C++ code. However, thanks for hav
> Of course not! This is just a simulation of a wider spacing.
> Is this clearer now?
That's fine now. Thanks,
Frédéric
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
>> I see that boost is not used. Is it deliberate? These are c++03
>> libraries and most of them have been the source of the new standard.
>
> "source of standard" means that they are liable to change particularly
> in the course of becoming part of a standard.
I use boost every day for my profess
>> I see this in your "bad" examples of ties:
>> d'4~ s4 d' s2 e'4~ s4 e' s
>>
>> How do you justify that this should work with non logical spacers included?
>
> What do you mean by "non logical spacers"? I don't quite understand
> this question.
I mean why would you write d'4~ s4 d' in real life
> Change them so that they will fail using anything but C++11? That
> sounds like it would not buy us anything but trouble at the current
> point of time.
OK, I forget that.
I see that boost is not used. Is it deliberate? These are c++03
libraries and most of them have been the source of the new
Hi Janek,
I see this in your "bad" examples of ties:
d'4~ s4 d' s2 e'4~ s4 e' s
How do you justify that this should work with non logical spacers included?
I tried to replace this with logical spacers and do not get any issue:
<< {
> \repeat unfold 8 { d''8[ d''] }
} \\ {
d'4~ d' e'4~
Hi,
g++ defaults to the C++ standard of 2003. 2 years ago a new standard
has been published with a log of improvements.
Today the g++ commands in the build process of lilypond do not specify
any standard so that it defaults to c++03.
Could we switch to c++11?
I suspect that a test would be require
>> out/usage/lilypond-book.texi:1179: @itemx must follow @item
>> the section level of @unnumberedsubsubsec which is too low
>>
>> I wonder if texi2html version in F19 is too new? I have version 1.82
>> installed.
>>
>
> Not texi2html, but recent texinfo causes problems. The patch is ready and I
>
> I don't think ./configure should do this automatically, but at the very
> least, it should fail when it finds a guile version that is incompatible
> with our source code. Can you please open an issue for it\?
good point, I will do that.
Frédéric
___
l
I can now build lilypond and compile at least the simple score { c }
But when I do my build process:
export GUILE=/usr/bin/guile1.8
export GUILE_CONFIG=/usr/bin/guile1.8-config
export GUILE_TOOLS=/usr/bin/guile1.8-tools
sh autogen.sh --noconfigure
mkdir build
cd build
../configure
make -j8 CPU_CO
> I read also that:
> "The packages will have to be patched to Require and BuildRequire the
> compat-guile18(-devel) package. Furthermore, they will have to be
> patched (if necessary) to use the renamed autotools macros. The
> patches to spec files and autotools macros are easy to implement.
> Pac
> Sounds like Fedora allows you to install both development libraries in
> parallel, but then you have to set some preferences or environment
> variables or similar in order to have it actually find 1.8.8.
I found that on http://fedoraproject.org/wiki/Features/Guile2
"guile-1.8.8 should be properl
configure complains:
ERROR: Please install required programs: echo no guile-config >=
1.8.2 (installed: )
I do not understand what to do. How did you say that the lilypond that
comes with F19 has to use guile 1.8?
Frédéric
---
I have just moved to fedora 19 and tried to build lilypond to
contribute to some bug fix to #3369.
However, when I run a simple example like { c }, below is what I get.
I guess this is because Fedora 19 comes with guile2, doesn't it?
And I guess, there is nothing I can do against it?
What is strang
> My misunderstanding: from Frédéric's comment, I thought he was posting a
> changed patch, which should have a Patchy test. It was late last night
> after wrestling a recalcitrant trial balance at the office, so perhaps the
> synapses weren't firing in sequence. At any rate, I see Graham has pus
-j2
> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> 14:45:13Success:sudo -u lilybuild nice make check
> -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>
> --
> You received this message because you are the owner of the issue.
> You may adjust your notification pr
> LGTM
> http://codereview.appspot.com/6448169/
Here is the patch.
Frédéric
0001-Doc-added-link-to-conversion-tools-from-Encore-to-li.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/li
>> My question remains: should we sort alphabetically the list under
>> "Programs that can export LilyPond code" in the following webpage? It
>> looks like a mess.
>
> Yes, they should be sorted alphabetically.
It is now done. New patch uploaded: http://codereview.appspot.com/6448169/
Also fixed m
>> Please review this at http://codereview.appspot.com/6448169/
>> Affected files:
>> M Documentation/fr/web/introduction.itexi
>> M Documentation/web/introduction.itexi
>
> While you are at it, you could add https://github.com/hanwen/go-enc2ly here
> too.
Done, added link to go-enc2ly.
Pleas
> I wanted to run regression tests and compare before and after a change.
> However, I obtained the error given below after make -j8 CPU_COUNT=8 check
>
> I suspect this is because I am compiling with gcc/g++ 4.7.0 (coming
> with Fedora 17) and its release notes say:
> "Avoid polluting the global n
> http://codereview.appspot.com/6447043/diff/1/Documentation/de/notation/rhythms.itely#newcode2271
> Documentation/de/notation/rhythms.itely:2271: % by default we beam in
> (6) due to beamExceptions
> are you sure you don't want German comments here?
Only Japanese has japanese comments, all other
> I proposed a patch for issue 2401 (see tracker).
Now in codereview: http://codereview.appspot.com/6447043
got this message:
WARNING: could not change issue labels;
please email lilypond-devel with the issue number: 2401
Frédéric
___
lilypond-devel m
> A description of the issue. For new issues, this is usually filled in
> with the commit message(s) automatically.
OK, I did it but failed when asking for :
Could not find stored credentials
/home/fred/.lilypond-project-hosting-login
Please enter login details manually
Username (google account
> Using git-cl will usually be the easiest way to make use of that
> infrastructure.
OK, I have installed git-cl and tried git cl upload master but I gvim
opened with a temporary file in /tmp. What should I write in this
file?
Frédéric
___
lilypond-deve
> If you are familiar with various linux utilities, you
> could follow the instructions here
> http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers
Do you mean that with git-cl, I could submit a patch that would be
automatically added to staging if successful?
Hi,
any chance to have this patch reviewed?
Cheers,
Frédéric
-- Forwarded message --
From: Frédéric Bron
Date: 2012/7/11
Subject: error while running make check (g++ 4.7.0): missing include of unistd.h
To: lilypond-devel@gnu.org
I wanted to run regression tests and compare
Hi,
I proposed a patch for issue 2401 (see tracker).
Frédéric
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
I proposed a patch for issue 2563.
Frédéric
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
> Add only the new test file, but check carefully that `make test` succeeds
> with the new test included, and take care that the header is correct
> and that no errors are generated, so that `make doc` will also succeed.
patch proposed.
I saw that the error was only in 3/4. But in the proposed tes
I wanted to run regression tests and compare before and after a change.
However, I obtained the error given below after make -j8 CPU_COUNT=8 check
I suspect this is because I am compiling with gcc/g++ 4.7.0 (coming
with Fedora 17) and its release notes say:
"Avoid polluting the global namespace an
>> The following snippet does not give 1/32 notes grouped together as
>> expected with 2.15.39:
>>
>> \new Staff {
>> \clef treble \key bf \major \time 3/4
>> \set Score.beamExceptions = #'(
>> ( end .
>> (
>> ( (1 .
> commit f6b1f6ebcd527e6262add9c9cf3e4df5b3e5d63f
>
> Refine mid-measure beams in 3/4 time; Issue 2566
>
> includes several regtests. Are you sure this is not covered?
I have looked at the different "*beam*" regtests but let me look at
this particular commit.
I will tell you.
Thanks,
Frédéric
The following snippet does not give 1/32 notes grouped together as
expected with 2.15.39:
\new Staff {
\clef treble \key bf \major \time 3/4
\set Score.beamExceptions = #'(
( end .
(
( (1 . 32) . (4 4 4 4 4
>>> I mentioned in passing that Fedora 17 (currently in beta) ships
>>> Lilypond 2.15.29 that reports bogus bar checks.
>>>
>>> It turns out that both the current Lilypond from git and Lilypond
>>> 2.14.2 are miscompiled on the up-to-date Fedora 17 so they exhibit the
>>> same problem.
>>
>> What c
> In top directory from commit , I have done:
> $ make all && make doc
>
> It stopped after an error in lilypond-book.py (see below).
I have rerun the same from a fresh clone and no error appeared. Maybe
I should have done make distclean before.
Frédéric
__
In top directory from commit , I have done:
$ make all && make doc
It stopped after an error in lilypond-book.py (see below).
Frédéric
lilypond-book.py: warning:
/home/bronf/lilypond/out/lybook-db/6f/lily-68fe9560.ly: duplicate
filename but different contents of orginal file,
printing diff again
> 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
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> 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 . ("t
>>> \relative c' {
>>> \override Fingering #'text =
>>> #(lambda (grob)
>>> (let ((finger-text (ly:event-property (event-cause grob) 'text)))
>>> (if (markup? finger-text)
>>> finger-text
>>> (fingering::calc-text grob
>>> c4
If someone can help me on this, it would be nice.
Regards, Frédéric
-- Forwarded message --
Comment #3 on issue 1029 by frederic...@m4x.org: \thumb should behave
like other fingerings
http://code.google.com/p/lilypond/issues/detail?id=1029
So I would like to sum up all comments be
> According to
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git
> it is.
I am a bit lost: should it be git.sv or git.savannah? Maybe this does
not matter.
Frédéric
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mai
> The git repository at savannah has been updated, everyone
> should do a fresh clone.
I can only use the http server because I cannot get outside my
firewall using the git protocol.
I was using http://git.sv.gnu.org/r/lilypond.git before. I have tried
http://git.savannah.gnu.org/r/lilypond.git an
> I didnt have time to write the songs in the notation. However, I have
> another sample, the easier one. This time, the song is "Amazing Grace" --
> translated to Bahasa Indonesia. (yes, it's in Indonesia).
> Can you take a look and see if it make sense? The notes are simple enough.
> The score is
> However, I live in the country where most of the people cannot read music in
> notation model. Instead, we are reading music in the solfegio: do, re, mi
> fa, sol, la, ti. We called the model as "solmisasi"
Interesting! I did not know that could exist. Can you tell us in what
country you live?
> At last, thanks to help above and beyond the call of duty by Neil, I have
> finally got the autobeam engraver fixed so it beams 4 4 right when there are
> 16th notes in the 2nd or 4th beat of the measure.
Very nice job. That's now a good reason for me to upgrade to 2.13.X.
Does this apply only t
> Everything compiles OK. And it runs fine until I get into recheck_beam.
> Recheck_beam actually executes successfully, but an exception is thrown
> later, and the exception doesn't make sense to me when I use gdb. Values
> are changed between the calling procedure and the called procedure in a
>> create a mount point:
>> $ mkdir /mnt/Share
>> then add the following line to /etc/fstab:
>> Share /mnt/Share vboxsf defaults 0 0
>
> Hmm. Is there any way to have this pre-configured? i.e. tell
> uses to create
> C:\lilybuntu-share\
> in windows (or create it for them), and h
> The only two problems I've yet to resolve are how to share files
> with my Windows host
Create a directory in windows for that, let's say d:\Share
Then you go in VirtualBox, click on the virtual machine name and in
the menu "Machine/Preferences".
Here you find shared directories where you can ad
> - estimated time: 30 minutes a week. (not counting normal reading
> of mailists)
Can you say how you do it in 30 minutes because each time I want to
update the NR after a small modification, its 15 to 20 minutes of
compilation...
Do you have a secret to make it quicker?
Frédéric
___
> You forgot "make doc-clean" in this sequence; in this case "make -C
> Documentation/ doc-clean" (which avoids rebuilding all snippets with
> lilypond-book) might be enough to get rid of your error with pdftex.
That worked, thanks,
Frédéric
___
lilyp
> For info I had the needed packages provided by a "sudo apt-get
> build-dep lilypond" command with the only difference that
> I used texi2html-1.82 (compiled from sources) instead of 1.78 (in
> Ubuntu's repository), as recommended when running ./autogen.sh.
did not know that (not in CG): I did th
> I have redone it again and the doc is now compiling since 1 hour so I
> assume it is working! Do not understand what happens.
> Will see tomorrow morning if anything good happened.
Well it stopped with an error before tomorrow:
cd ./out-www; texi2pdf -I ./out-www -I
/home/bronf/lilypond/Documen
> I hope that you did a "make clean; make" first. There was a
> commit recently that did something about strings and markups, so
> perhaps that's the problem.
I did make dist-clean and rerun autogen.sh
I have redone it again and the doc is now compiling since 1 hour so I
assume it is working! Do
Since I upgraded ubuntu to 9.10, make doc does not work anymore but
why? Is it because of the ubuntu upgrade or because of git pull?
Here is the output:
...
Renaming input to: `music-function-string-markup.ly'
music-function-string-markup.ly:15:24: error: syntax error, unexpected
STRING, expecting
> I've been there (had patches rejected because of bad indentation) and I
> remember the pain it was to completely reindent the file (as part of that
> process I learned to use the automatic indentation in vim). But my code is
> easier to read (which is *really* important for Scheme code IMO), so
Is there a debugger for .scm files? How is it possible to debug the
code, to print the variables, to run line by line...?
Regards,
Frédéric
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
- the addition to scm/music-functions.scm uses standard indentation,
>>> Not quite. Compare your additions to the previous rule
>>> (neo-modern-cautionary).
>>
>> done
>
> It's still not right: the indentation level is too shallow. Are you
> using an editor which changes tabs to spaces?
>
>
>> >> >> which is normal because directory Documentation does not exist in
>> >> >> out-www.
>> >> > Yes, but out-www/index.html *does* exist.
>> >> It contains only a redirection to the file that does not exist:
>> >
>> > Sorry, I was unclear: Documentation/out-www/index.html should
>> > exist.
>
>> 1. where the documentation goes (where should I find index.html to
>> browse the doc that was built; I went to out-www but index.html does
>> not work)
>
> What do you mean "does not work"? It's fine here, other than the
> broken xrefs for general.texi
When I try to open out-www/index.html, I
I have worked a bit with documentation.
I have difficulties to understand:
1. where the documentation goes (where should I find index.html to
browse the doc that was built; I went to out-www but index.html does
not work)
2. how to rebuild the doc when I do some minor changes; for example, I
change
Here is my new proposal:
- the addition to scm/music-functions.scm uses standard indentation,
- I modified slightly the example for all automatic accidental styles
(the same for all), in particular added staff change,
- I modified the doc of translations accordingly.
Hope it is now OK.
Frédéric
>> > If the current example does not work for the new styles, then we
>> > should modify the example and change it for everything on that doc
>> > page.
>>
>> I think the most confusing aspect of the snippet is the left hand
>> voice switching staves; \showStaffSwitch might help clarify things
>> h
> Why not use the existing snippet to demonstrate the new styles?
I have included the existing snippet but added a new one because I
think it demonstrates better the interaction between voices. I find
the piano example difficult to follow.
> Indentation/code style (format in the same manner as th
I would like to submit a patch that adds two new accidental styles:
neo-modern-voice and neo-modern-voice-cautionary.
Regards,
Frédéric
0001-added-new-automatic-accidental-behaviours-neo-moder.patch
Description: Binary data
___
lilypond-devel mailing l
> That reminds me of a problem I once encountered. Aren't accidentals
> normally supposed to be cancelled by the next bar line? This one carries
> over, so that the second B flat has no flat printed.
>
> \version "2.12.1"
> \include "english.ly"
>
> \relative c'
> {
> c4 c bf \bar "||" bf | c1
>
This is a bug: automatic accidentals do not take into account
alternatives after volta repeat:
{
#(set-accidental-style 'modern)
\time 2/4
\repeat volta 2 { cis'4 dis' }
\alternative { { c' d'8 eis'8 } { d'4 c'8 e' } }
}
in the second alternative: we should have:
- natural d, natural c, n
Hi folks,
I refer to that portion of the documentation:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Displaying-pitches#Automatic-accidentals
I think that the fact that automatic accidentals should apply at voice
or staff level should be set separately from the type of automatic
acci
> Reinhold and Frederick: as you may have guessed, I'm proposing
> that your patch waits until 3.0. Anything requiring such manual
> tweaks will make some people very unhappy, such as mutopia.
>
> I think we should make *all* manual changes at once, but reassure
> people that this will (probably)
>>> Is it because I have only version 1.78 of texi2html? However this is
>>> the only version proposed by ubuntu!
>>
>> I believe so. Try download texi2html 1.82
>> http://www.nongnu.org/texi2html/
>> then do
>> ./configure
>> make
>> sudo make install
Worked fine, thanks !
Frédéric
Hi!
I have installed a virtual machine with VirtualBox on my windows
machine. I have installed ubuntu and all stuff for lilypond.
I obtained the sources via git.
I tried to run the regression tests but obtained the following error:
WARNING: Unable to load the map file
Undefined subroutine &main::
> Attached is a sample file to show how the definition of spanners could work
> with my patch. I've also implemented two functions to give the text of the
> spanner directly in the postfix call.
When I look at your dynamic_spanners_postfix.pdf file, it seems to me
that on the second line (with the
> So, I took a look at the issue today and created a patch, which will now allow
> all dynamic spanner starters to be implemented as postfix-operators.
>
> The short (<15 quite trivial lines!) patch is up for review at:
> http://codereview.appspot.com/39047
>
> Basically, my question for now is whe
1 - 100 of 110 matches
Mail list logo
