Le lundi 05 janvier 2009 à 15:32 +, Trevor Daniels a écrit :
> I have a git problem with your recent commit
> c553fc2251b508befebd1dc297c4baa898463f34 to clean up the build scripts.
> The reason is that aux is a reserved word in Windows, along with a few
> others like com, lpt1, nul, prn, Lp
John
I have a git problem with your recent commit
c553fc2251b508befebd1dc297c4baa898463f34 to clean up the build scripts.
The commit tries to create a directory python/aux and fails.
The reason is that aux is a reserved word in Windows, along with a few
others like com, lpt1, nul, prn, Lpt4,
On 1/5/09 7:06 AM, "Andrew Wilson" wrote:
> Hi Carl
>
>
> Since I'm mailing you anyway, I'll include this. I was planning to use cygwin
> to
> do the lilypond development. I've installed git, worked through a basic
> tutorial
> and grabbed a copy of the sources from the main repository.
Hi Han-Wen,
Sorry for the quite unreasonable delay, but I hope I've sorted out GCC
warnings mentioned in this thread.
Le samedi 08 novembre 2008 à 16:59 -0200, Han-Wen Nienhuys a écrit :
> +#define EPSNULL 1e-12
> this looks fishy. Why another EPS value? Joe?
I apologize for this obviously wr
On 2009/01/05 12:31 +, Sawada, Yoshiki wrote:
> Then, I did as following:
> ./autogen.sh
> ./configure
> make
> make install
You needn't install LilyPond to work on translations, but it is very
good you can build it. Have you tried "make web"? See Application
Usage -> Install -> Compiling fr
Thank you for your replys.
Thanks to you, I could go to the next step.
I resolved the "./autogen.sh" step by installing texi2html
using the usual trio as John said, and installing texlive-metapost
package.
texi2html is installed into /usr/local/bin.
Then, I did as following:
./autogen.sh
./confi
On Mon, Jan 5, 2009 at 12:16 AM, Carl D. Sorensen wrote:
>> git checkout pristine
>> make test-baseline
>> git-apply-patch bugfix
>> make check
>>
>> For the rest, the patches should be reviewed, and in the case of
>> bugfixes, accompanied by a regtest file; I trust Carl's judgement to
>
Mark
Look up layers in the Notation Reference index. The
relevant sentence there is "The order of printing objects
with the same value of 'layer is indeterminate."
Setting 'layer explicitly may solve your problem.
Trevor
- Original Message -
From: "Mark Polesky"
To: "lilypond-devel
2009/1/5 Mats Bengtsson :
> As far as I can see from the source code, everything between the % and the
> end of the line
> should be ignored by LilyPond, no matter if you have a space after the % or
> not.
> The only special case is %{ which is the start of a block comment.
By the way, it's funny
As far as I can see from the source code, everything between the % and
the end of the line
should be ignored by LilyPond, no matter if you have a space after the %
or not.
The only special case is %{ which is the start of a block comment.
/Mats
Mark Polesky wrote:
Hi again!
recently I've f
Hi again!
recently I've found some odd behaviors that I
traced down to some ly % comments that had no
space between the % and the next character.
Things like
%what's going on here?
or
%you gotta be kidding me...
And when I changed them both to
% oh, weird...
normal behaviors resumed as fa
Guys,
this is driving me crazy. I responded to a
request on -user for a "torn-page" effect at
the end of each system, preferably random. I
made some progress, then slammed head-first
into inexplicable buggy behavior. I tried to
recreate this on a smaller scale, but this
is as small as I can get
Le dimanche 04 janvier 2009 à 00:39 +0100, John Mandereau a écrit :
> I will include this removal in the patch that splits stuff in
> buildscripts.
I actually made two commits, because these two issues only intersect at
builder.py and these commits are large enough.
Cheers,
John
__
Le dimanche 04 janvier 2009 à 20:54 -0200, Han-Wen Nienhuys a écrit :
> Please junk
Done, and did the same for metapost-*.make.
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Juergen Reuter wrote Monday, January 05, 2009 1:47 AM
On Sun, 4 Jan 2009, Trevor Daniels wrote:
BTW, the term "accidental style" appears twice in the documentation
with a
completely different meaning:
- in 1.1.3, meaning the way how to display and reset accidentals
In the detailed explanat
15 matches
Mail list logo
