On Sun, Dec 27, 2009 at 03:35:12PM +1100, Joe Neeman wrote:
> and I find the following:
> $ file out/share/lilypond/current/scm
> out/share/lilypond/current/scm: broken symbolic link to
> `/home/jneeman/src/lilypond//scm'
Sorry! I forgot to comment out some lines before pushing my
latest work on
>From a clean git clone (43a2f7a609ed14a1), I do
$ ./autogen.sh --enable-debugging --disable-optimising
$ make
and I find the following:
$ file out/share/lilypond/current/scm
out/share/lilypond/current/scm: broken symbolic link to
`/home/jneeman/src/lilypond//scm'
The problem is that my lilypond
On 12/26/09 7:14 PM, "Mark Polesky" wrote:
> Carl Sorensen wrote:
>> Have you considered whether "Using Git" should be an
>> appendix? To the extent that it's teaching about git,
>> rather than about LilyPond, it might belong in an
>> appendix.
>>
>> Maybe there should be a chapter called so
>> Did the old and new lists had exactly the same purpose? This would be
>> the case for lilyond-user-fr and lilypond-fr.
Two of the old lists were exactly replaced by new lists. The other
two old lists (help- and -discuss) were essentially merged to create
the -user list. The -devel list was c
Carl Sorensen wrote:
> Have you considered whether "Using Git" should be an
> appendix? To the extent that it's teaching about git,
> rather than about LilyPond, it might belong in an
> appendix.
>
> Maybe there should be a chapter called something like
> "Contributing patches" that mentions all t
I'm getting weird autogen-related errors in GUB, which is puzzling,
since I can't think of any recent futzing around with autogen.sh
(either in the GUB git tree or in lilypond itself).
I then tried making sure that I can do autogen.sh in a plain old
out-of-tree build, but it fails. It's obvious w
> lily-git
> lily-git-gui
> lily-gitg
> lily-gitp
> lilygit
> lilylibrarian
> lilypond-git
> lilysourcesafe
> lysourcestore
> lycodemanager
Here are some more (I prefer `lilypatch'):
develypond
easiLY
easylily
lilyfix
lilypatch
lydev
simplily
simpLY
- Mark
writing: /main/src/build-lilypond/./out-www/xref-maps/usage.fr.xref-map
touch -r out-www/usage.texi
/main/src/build-lilypond/./out-www/xref-maps/usage.fr.xref-map
cp -p web.texi out-www/web.texi
cp: cannot stat `web.texi': No such file or directory
make[3]: *** [out-www/web.texi] Error 1
make[3]: L
2009/12/27 Andrew Hawryluk :
> On Sat, Dec 26, 2009 at 10:22 AM, Graham Percival
> wrote:
>> On Sat, Dec 26, 2009 at 06:18:13PM +0100, John Mandereau wrote:
>>> What's the completion status of the essay? Are at least some chapters
>>> stabilized enough so that they can be translated, reusing tran
Le samedi 26 décembre 2009 à 16:13 -0700, Andrew Hawryluk a écrit :
> On Sat, Dec 26, 2009 at 10:22 AM, Graham Percival
> wrote:
>>
> Probably not stable enough to translate, but getting close. (I'm
> assuming that the translators would not want any changes to the
> English version once they star
On 12/26/09 3:57 PM, "Graham Percival" wrote:
> 2009/12/26 John Mandereau :
>> Le samedi 26 décembre 2009 à 12:27 -0700, Carl Sorensen a écrit :
>>> Shall we change the name to 'lilygit', or 'lilypond-git', or 'lily-git'?
>>>
>>> I think there *has* to be a better name than lilycontrib.
>>
>
On Sat, Dec 26, 2009 at 10:22 AM, Graham Percival
wrote:
> On Sat, Dec 26, 2009 at 06:18:13PM +0100, John Mandereau wrote:
>> What's the completion status of the essay? Are at least some chapters
>> stabilized enough so that they can be translated, reusing translations
>> of former Chapter 1 Intr
2009/12/26 John Mandereau :
> Le samedi 26 décembre 2009 à 22:57 +, Graham Percival a écrit :
>> Or just "lily-git" ? I don't follow the "porcelain" joke...?
>
> This is not a joke, this is the official name for Git user front-ends.
I... see. A few minutes of googling shows that you're indee
Le samedi 26 décembre 2009 à 22:57 +, Graham Percival a écrit :
> Or just "lily-git" ? I don't follow the "porcelain" joke...?
This is not a joke, this is the official name for Git user front-ends.
Sorry for not joking :-)
John
signature.asc
Description: Ceci est une partie de message numé
2009/12/26 John Mandereau :
> Le samedi 26 décembre 2009 à 22:14 +0100, Francisco Vila a écrit :
>> I agree (not fully happily) on lilypond-users-es, with an English word
>> on the name and a different name wrt our existing list, which is not
>> too old, after all.
>
> You gave good reasons for not
2009/12/26 John Mandereau :
> Le samedi 26 décembre 2009 à 12:27 -0700, Carl Sorensen a écrit :
>> Shall we change the name to 'lilygit', or 'lilypond-git', or 'lily-git'?
>>
>> I think there *has* to be a better name than lilycontrib.
>
> What about lily-git-gui, lily-gitg, lily-gitp ("p" for porc
Le samedi 26 décembre 2009 à 12:27 -0700, Carl Sorensen a écrit :
> Shall we change the name to 'lilygit', or 'lilypond-git', or 'lily-git'?
>
> I think there *has* to be a better name than lilycontrib.
What about lily-git-gui, lily-gitg, lily-gitp ("p" for porcelain ;-)?
Best,
John
signature.
Le samedi 26 décembre 2009 à 14:13 -0600, David R. Linn a écrit :
> As I recall, the "plan" in the migration from the GMP lists to the
> LilyPond lists was to annnounce the new lists and deprecate the old
> lists in one stable release and kill off the old lists with the
> *following* stable release
2009/12/26 John Mandereau :
> Le samedi 26 décembre 2009 à 20:58 +, Graham Percival a écrit :
>> John, please decide to go with lilypond-user-es. Once you've
>> decided that, I'll make the list, and this task will be done.
>
> I won't decide to go with lilypond-user-es, as grounds give by Fran
Le samedi 26 décembre 2009 à 22:17 +0100, Francisco Vila a écrit :
> And of course I'd like _very_ much to have the word 'español' which is
> the Spanish for 'Spanish' into the short description [when technically
> available]
I'm afraid this is out of our control; we can't kidnap gnu.org admins.
I
On 26/12/09 19:27, Carl Sorensen wrote:
Shall we change the name to 'lilygit', or 'lilypond-git', or 'lily-git'?
I think there *has* to be a better name than lilycontrib.
lilylibrarian, lilysourcesafe , lysourcestore, lycodemanager ?
Cheers,
Ian
__
Le samedi 26 décembre 2009 à 22:14 +0100, Francisco Vila a écrit :
> I agree (not fully happily) on lilypond-users-es, with an English word
> on the name and a different name wrt our existing list, which is not
> too old, after all.
You gave good reasons for not putting -users in the name, so I do
Le samedi 26 décembre 2009 à 20:58 +, Graham Percival a écrit :
> That's a good point. I mean, if somebody submits a bug report to
> the es list, presumably somebody would translate it and send it to
> the bug-lilypond list.
Sure, this has already happen with the French-speaking Lily communit
2009/12/26 Francisco Vila :
> 2009/12/26 Graham Percival :
>> John, please decide to go with lilypond-user-es. Once you've
>> decided that, I'll make the list, and this task will be done.
>
> I agree (not fully happily) on lilypond-users-es, with an English word
> on the name and a different name
2009/12/26 Graham Percival :
> John, please decide to go with lilypond-user-es. Once you've
> decided that, I'll make the list, and this task will be done.
I agree (not fully happily) on lilypond-users-es, with an English word
on the name and a different name wrt our existing list, which is not
t
On Sat, Dec 26, 2009 at 08:23:42PM +0100, Francisco Vila wrote:
> 2009/12/26 Valentin Villenave :
> > 2009/12/26 John Mandereau :
> >>> Should we ask the -user-fr
> >>> people to accept a name change to lilypond-fr ?
> >>
> >> This is perfectly acceptable, and I think a confirmation of Valentin,
>> I should be more comfortable having lilypond-es and lilypond-user-fr
>> than forcing a rename of the fr list. I am also willing to go on with
>> lilypond-user-es if regularity over names is so much important, but
>> probably -utilisateurs or -fr alone would have been better from the
>> begninnin
David,
These are mostly stylistic nit-picks.
I'd like the section to state clearly the relationship between Lilypond
scoping and the guile module system.
Cheers,
Ian
http://codereview.appspot.com/160048/diff/13001/13002
File Documentation/contributor/programming-work.itexi (left):
http://cod
We recently had some discussion about the directory for the local
repository.
Currently, lilycontrib uses ~/lilypond/, which may conflict with an
installed LilyPond directory.
Should we change the directory to ~/lilypond-git, or ~/lilypond-src?
It's trivial to do in lilycontrib.
Thanks,
Carl
On 12/26/09 10:30 AM, "Graham Percival" wrote:
> On Fri, Dec 25, 2009 at 07:13:32PM -0800, Mark Polesky wrote:
>
>> 2. Using the `lilycontrib' GUI
>> 3. Using Git
>
> I think these should be one chapter.
>
> 2. Source code
> 2.1 Using lilycontrib
> 2.2 Using git
Shall we change the name
2009/12/26 Valentin Villenave :
> 2009/12/26 John Mandereau :
>>> Should we ask the -user-fr
>>> people to accept a name change to lilypond-fr ?
>>
>> This is perfectly acceptable, and I think a confirmation of Valentin,
>> the other administrator, will be enough to decide to request it to
>> Sav
2009/12/26 John Mandereau :
>> Should we ask the -user-fr
>> people to accept a name change to lilypond-fr ?
>
> This is perfectly acceptable, and I think a confirmation of Valentin,
> the other administrator, will be enough to decide to request it to
> Savannah hackers. If this happens, we shou
Mark Polesky writes:
> David Kastrup wrote:
>> I really don't think a turnaround time of weeks for things
>> like that, taking an order of magnitude more of time,
>> effort, and spirit than actually writing the improvement,
>> contributes much to development.
>
> Hmm. Me neither. Is there somet
On 12/26/09 10:18 AM, "Graham Percival" wrote:
> On Fri, Dec 25, 2009 at 09:04:29PM -0700, Carl Sorensen wrote:
>>
>> On 12/25/09 8:13 PM, "Mark Polesky" wrote:
>>
>>> Carl Sorensen wrote:> As I think more about this, I wonder if there should
>>> be
>>> a
short and sweet summary for ex
Graham Percival wrote Saturday, December 26, 2009 5:18 PM
I like this idea, but I'm not certain if we all have the same
idea. Here's the idea that I like:
1. introduction
1.1 help us: duplicate material from website
1.2 summary for unix developers: 2-3 paragraphs. We use git, the
docs are
On Fri, Dec 25, 2009 at 07:13:32PM -0800, Mark Polesky wrote:
> I feel that it has taken me longer than it should have to
> get familiar with some of the basics of compiling, so this
> text would ideally reduce the confusion time for new
> developers.
Based on all my experience at doc restructurin
On Sat, Dec 26, 2009 at 06:18:13PM +0100, John Mandereau wrote:
> What's the completion status of the essay? Are at least some chapters
> stabilized enough so that they can be translated, reusing translations
> of former Chapter 1 Introduction of the Learning Manual and the Essay on
> the old webs
On Fri, Dec 25, 2009 at 09:04:29PM -0700, Carl Sorensen wrote:
>
> On 12/25/09 8:13 PM, "Mark Polesky" wrote:
>
> > Carl Sorensen wrote:> As I think more about this, I wonder if there should
> > be
> > a
> >> short and sweet summary for experienced Linux developers,
> >> followed by a gentle (a
Hi Andrew,
What's the completion status of the essay? Are at least some chapters
stabilized enough so that they can be translated, reusing translations
of former Chapter 1 Introduction of the Learning Manual and the Essay on
the old website? I can't figure it out myself from Git history.
In the
David Kastrup wrote:
> I really don't think a turnaround time of weeks for things
> like that, taking an order of magnitude more of time,
> effort, and spirit than actually writing the improvement,
> contributes much to development.
Hmm. Me neither. Is there something that would make it
easier f
On Sat, Dec 26, 2009 at 12:03:56PM -, Trevor Daniels wrote:
>
> David Kastrup wrote Saturday, December 26, 2009 9:55 AM
>
>> I really don't think a turnaround time of weeks for things like that,
>> taking an order of magnitude more of time, effort, and spirit than
>> actually writing the improv
>> Actually, thinking about this some more, do ottava
>> symbols make any sense in tablature?
none at all. tablature tells you where to put your fingers to get the
notes, not what notes need playing.
--
Dana Emery
___
lilypond-devel mailing list
lil
On 26.12.2009, at 13:38, Trevor Daniels wrote:
Trevor Daniels wrote Saturday, December 26, 2009 12:24 PM
James Bailey wrote Saturday, December 26, 2009 9:51 AM
Are the ottava symbols an intentional omission from
tabFullNotation? I couldn't find any documentation on the function.
Not as fa
Trevor Daniels wrote Saturday, December 26, 2009 12:24 PM
James Bailey wrote Saturday, December 26, 2009 9:51 AM
Are the ottava symbols an intentional omission from
tabFullNotation? I couldn't find any documentation on the
function.
Not as far as I know. I'll add them (unless
someone sho
James Bailey wrote Saturday, December 26, 2009 9:51 AM
Are the ottava symbols an intentional omission from
tabFullNotation? I couldn't find any documentation on the
function.
Not as far as I know. I'll add them (unless
someone shouts quickly).
Trevor
_
On 12/26/09 1:59 AM, "Trevor Daniels" wrote:
>
> I also find cherry-picking to be a useful alternative
> to rebasing, especially with the beautifully simple
> interface in gitk. Perhaps this could have a brief
> explanation, as the man pages are so confusing.
I typically do the following:
David Kastrup wrote Saturday, December 26, 2009 9:55 AM
I posted this patch already several days ago without any feedback,
so I
tried uploading it on Rietveld in order to get a better reaction.
A bit
of a nuisance how much work it is to get even trivial doc
improvements
accepted.
Thanks Da
Hi there,
I just tried the version 2.12.3-1 which you
recommand for MacOSX Intel 10.4 on my
10.6 Snow Leopard and it works very fine!
The first time I tried to typset a file nothing
happend. I quit Lilypond and tried again, and
it worked and since then every file works very
time excellent.
So
Le samedi 26 décembre 2009 à 02:32 +, Graham Percival a écrit :
> The attached patch lets me build xrefs by looking at
> Documentation/*.tely
> directly, instead of looking at the corresponding
> Documentation/out-www/*.texi
> files.
>
> This would be very nice for the website, since we ca
I posted this patch already several days ago without any feedback, so I
tried uploading it on Rietveld in order to get a better reaction. A bit
of a nuisance how much work it is to get even trivial doc improvements
accepted.
Unfortunately, my lack of expertise made it end up in a previous issue.
Are the ottava symbols an intentional omission from tabFullNotation?
I couldn't find any documentation on the function.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Are the ottava symbols an intentional omission from tabFullNotation?
I couldn't find any documentation on the function.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Mark Polesky wrote Saturday, December 26, 2009 3:13 AM
Carl Sorensen wrote:
As I think more about this, I wonder if there should be a
short and sweet summary for experienced Linux developers,
followed by a gentle (and longer) introduction for the
Windows guys.
Actually, I'm thinking there sh
53 matches
Mail list logo
