On Sun, Jan 04, 2009 at 11:48:10AM +0100, Jan Nieuwenhuizen wrote:
> Op zaterdag 03-01-2009 om 11:58 uur [tijdzone -0800], schreef Graham
> Percival:
>
> > I had great success converting another project to cmake last Aug,
> > but this isn't anything I'd attempt with my current situation. I
> > mi
On Thu, Jan 01, 2009 at 12:52:53PM -, Trevor Daniels wrote:
>
> Graham Percival Thursday, January 01, 2009 12:19 AM
>> Yes, texinfo screws up if a @macro{is spread
>> over two lines}. IIRC this was listed in the old texinfo-todo.txt
>> (list of technical problems with the docs).
>
> Fixed in g
The most recent version of the CG is now online. I'll upload it
very soon after each update:
http://percival-music.ca/gop/
I plan on doing more work on it later today, but if there's any
comments about the broad organization of it, please give them
now/soon.
Cheers,
- Graham
__
On 1/10/09 4:57 PM, "Ian Hulin" wrote:
> Hi Carl,
> I understand your answers but I find the distinction a bit confusing for
> lilypond users.
>
> If we're producing a list in an appendix of the documentation of the syntax
> for bits of Lilypond, if the user's trying to look up how to code
On Sat, Jan 10, 2009 at 07:30:23AM -0700, Carl D. Sorensen wrote:
>
> On 1/10/09 5:59 AM, "John Mandereau" wrote:
>
> > I propose to adopt either of the following solutions:
> >
> > 1. Define a macro for each predefined command: the docstring of each
> > function \foo would be stored in a macro
Hello,
This patch reworks def-grace-function so that it inserts the
docstring, if defined, into the template for define-music-function.
If the docstring is not defined, the unquote-splicing strips the empty
list from the template. All further processing is left to
define-music-function.
Will thi
Hello, everyone
Finally, I got Japanese HTML files and git-patches.
Thank you very much for your great helps =)
I put HTML files (which include index.html, Preface.html and Introduction.html)
on
http://irjb.s346.xrea.com/lilypond/
and put git-patches on
http://irjb.s346.xrea.com/lilypond/First-Ja
Patrick McCarty a écrit :
`make all' fails on current master. Is this because the new
directory, Documentation/es/topdocs/, doesn't have a makefile yet?
It had the makefile on my working tree, but I forgot adding it to Git :-/
make[3]: Entering directory
`/home/pnorcks/git/lilypond/Document
Hello,
`make all' fails on current master. Is this because the new
directory, Documentation/es/topdocs/, doesn't have a makefile yet?
touch ./out/dummy.dep
echo '*' > ./out/.gitignore
make[2]: Leaving directory `/home/pnorcks/git/lilypond/Documentation/es'
make[2]: Entering directory `/home/pnor
On Sat, Jan 10, 2009 at 06:30:23PM +0100, John Mandereau wrote:
> Neil Puttock a écrit :
>>> Any thoughts on what is wrong or how I can get this patch to apply?
>>
>> It applies OK using `git am'.
>
> BTW git-apply should be used for patches without authoring information,
> i.e. patches not made w
On Sat, Jan 10, 2009 at 11:40 AM, Reinhold Kainhofer
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Samstag, 10. Januar 2009 20:27:34 schrieb Carl D. Sorensen:
>> On 1/10/09 12:16 PM, "Reinhold Kainhofer" wrote:
>> > Can you maybe attach the file (rather than pasting its contents
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 10. Januar 2009 20:27:34 schrieb Carl D. Sorensen:
> On 1/10/09 12:16 PM, "Reinhold Kainhofer" wrote:
> > Can you maybe attach the file (rather than pasting its contents into the
> > mail), so that end-of-line characters are preserved...
>
On 1/10/09 12:16 PM, "Reinhold Kainhofer" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Samstag, 10. Januar 2009 19:29:31 schrieb Carl D. Sorensen:
>> On 1/10/09 11:24 AM, "John Mandereau" wrote:
>>> Carl D. Sorensen a écrit :
> Are "diff --git a/... b/..." lines broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 10. Januar 2009 19:32:23 schrieb John Mandereau:
> Reinhold Kainhofer a écrit :
> > Am Samstag, 10. Januar 2009 18:49:40 schrieb John Mandereau:
> >> Have you tried installing libtool-ltdl-devel (or whatever this Fedora
> >> package is call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 10. Januar 2009 19:29:31 schrieb Carl D. Sorensen:
> On 1/10/09 11:24 AM, "John Mandereau" wrote:
> > Carl D. Sorensen a écrit :
> >>> Are "diff --git a/... b/..." lines broken in the patch you actually
> >>> tried to apply? They should n
Reinhold Kainhofer a écrit :
Am Samstag, 10. Januar 2009 18:49:40 schrieb John Mandereau:
Have you tried installing libtool-ltdl-devel (or whatever this Fedora
package is called on Ubuntu) system-wide?
Yes, it is installed:
lilyp...@server:~$ locate libltdl.so
/usr/lib/libltdl.so
/usr/lib/libl
On 1/10/09 11:24 AM, "John Mandereau" wrote:
> Carl D. Sorensen a écrit :
>>> Are "diff --git a/... b/..." lines broken in the patch you actually tried to
>>> apply? They should not be broken, I guess.
>>
>> No, they're not broken. It's one line.
>
> Ugh, I'm almost short of ideas; which O
Carl D. Sorensen a écrit :
Are "diff --git a/... b/..." lines broken in the patch you actually tried to
apply? They should not be broken, I guess.
No, they're not broken. It's one line.
Ugh, I'm almost short of ideas; which OS do you use to work with Git? Could
a non-Linux system be confu
On 1/10/09 10:54 AM, "John Mandereau" wrote:
>>> Carl D. Sorensen a écrit :
fatal: git apply: bad git-diff - expected /dev/null on line 46
Patch failed at 0001.
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 10. Januar 2009 18:49:40 schrieb John Mandereau:
> Hi Reinhold,
>
> Reinhold Kainhofer a écrit :
> > So, apparently, ./conftest can't find the libltdl.so.3 any more (which it
> > was linked against), since the tools directory is no longer i
Carl D. Sorensen a écrit :
fatal: git apply: bad git-diff - expected /dev/null on line 46
Patch failed at 0001.
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "g
Hi Reinhold,
Reinhold Kainhofer a écrit :
So, apparently, ./conftest can't find the libltdl.so.3 any more (which it was
linked against), since the tools directory is no longer in LD_LIBRARY_PATH...
It seems that while building (and of course also when running) all the tools,
we still need the to
On 1/10/09 10:40 AM, "John Mandereau" wrote:
> Carl D. Sorensen a écrit :
>> fatal: git apply: bad git-diff - expected /dev/null on line 46
>> Patch failed at 0001.
>> When you have resolved this problem run "git am --resolved".
>> If you would prefer to skip this patch, instead run "git am --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 10. Januar 2009 13:46:15 schrieb John Mandereau:
> > 2. Get GUB setup and working. Whatever bugs you find and fix
> > will be less that I'll encounter. Since I'm using kainhofer, I'll
> > probably find bugs (in x64) that you don't find,
Carl D. Sorensen a écrit :
fatal: git apply: bad git-diff - expected /dev/null on line 46
Patch failed at 0001.
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "g
On 1/10/09 10:22 AM, "Neil Puttock" wrote:
> Hi Carl,
>
> 2009/1/10 Carl D. Sorensen :
>
>> Any thoughts on what is wrong or how I can get this patch to apply?
>
> It applies OK using `git am'.
Thanks for the tip. I hadn't known about git am.
But it still didn't apply properly for me:
Neil Puttock a écrit :
Hi Carl,
2009/1/10 Carl D. Sorensen :
Any thoughts on what is wrong or how I can get this patch to apply?
It applies OK using `git am'.
BTW git-apply should be used for patches without authoring information, i.e.
patches not made with git-format-patch.
Cheers,
Joh
Hi Carl,
2009/1/10 Carl D. Sorensen :
> Any thoughts on what is wrong or how I can get this patch to apply?
It applies OK using `git am'.
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilyp
I received the following patch from Patrick McCarty;; From
61917179406f567351d73282ca4ed008b3e4b859 Mon Sep 17 00:00:00 2001
From: Patrick McCarty
Date: Tue, 6 Jan 2009 16:26:22 -0800
Subject: [PATCH] Docs: Add new procedure for barNumberVisibility
* The default value of barNumberVisibility, the
Frédéric Bron a écrit :
That's what I did before 2.10.33. But then, cygwin came with the right
lilypond version and I preferred switching to cygwin.
I have now installed mingw version of lilypond. However, who/how was
lilypond added to cygwin?
Bertalan Fodor used to do it when MinGW binaries di
On 1/10/09 8:28 AM, "John Mandereau" wrote:
> Carl D. Sorensen a écrit :
>> I propose something different. I think the current NR documentation is
>> right, with a usage description in the section of the NR, and a short
>> description from the docstring in the appendix that lists all music
>>
Carl D. Sorensen a écrit :
I propose something different. I think the current NR documentation is
right, with a usage description in the section of the NR, and a short
description from the docstring in the appendix that lists all music
functions. The reason I use the Identifiers page is that it
On 1/10/09 5:59 AM, "John Mandereau" wrote:
> Graham Percival a écrit :
>> On Sat, Jan 10, 2009 at 08:12:49AM +0100, Frédéric Bron wrote:
>>>- I have mainly copied documentation from the Notation Manual. Would be
>>>better to enter the documentation only once because if the function
>>
On Sat, Jan 10, 2009 at 01:46:15PM +0100, John Mandereau wrote:
> Hi Graham,
> Graham Percival wrote:
>> If anybody doesn't like it (and doesn't know/feel like fixing it),
>> just revert that commit.
>
> Reverting commits is not good for the moral.
Yeah, but I specifically made it an option.
> I
Graham Percival a écrit :
On Sat, Jan 10, 2009 at 08:12:49AM +0100, Frédéric Bron wrote:
- I have mainly copied documentation from the Notation Manual. Would be
better to enter the documentation only once because if the function
changes, we have to change the doc. at two locations.
De
Hi Graham,
Graham Percival wrote:
If anybody doesn't like it (and doesn't know/feel like fixing it),
just revert that commit.
Reverting commits is not good for the moral. It's best not to break
compilation on master though, so I suggest you create a branch dev/gpercival
if you like. That sa
Frédéric Bron a écrit :
Hi, is there a chance that we have a 2.12.1 release for cygwin?
Using 2.10.33 on cygwin was great, I'd love to switch to 2.12.1.
Have you already tried MinGW binary available on lilypond.org?
You can run it from Cygwin if you set the PATH accordingly, and it is
probably
On Fri, Jan 09, 2009 at 08:35:41PM +0100, John Mandereau wrote:
> Graham Percival a écrit :
>> Could I get this dir created and added to the build scripts? I'd
>> like to move the stuff from web-gop/texinfo/contributing into
>> there, so that Carl can see what's there and add to it.
>
> Done.
I m
38 matches
Mail list logo
