On Fri, Mar 13, 2009 at 12:49:48PM +0100, John Mandereau wrote:
> Graham Percival a écrit :
>> I'm not clear about this, either. Actually, if anything
>> introduction.itely is going to die entirely (as part of the
>> web-gop stuff).
>>
> All right. I can't work on GOP in the 4 coming weeks: I
I have a (largish, sorry) code review up for new min-systems-per-page, max-
systems-per-page and systems-per-page variables in the paper block:
http://codereview.appspot.com/28041
Also, the code is in the dev/jneeman git branch, if anyone wants to test.
Joe
___
Han-Wen Nienhuys writes:
> On Fri, Mar 13, 2009 at 8:50 AM, David Kastrup wrote:
>
>> It is a bit disappointing since the info documentation with images is
>> essential for really getting moving smoothly with Lilypond, and the
>> procedure for producing them is so broken or obfuscate that none,
Le 13 mars 09 à 18:36, Ian Hulin a écrit :
Hi Nicolas,
So how do you do interactive debugging if you're trying to write (or
modify) Scheme code for Lilypond. I'd be interested to know as an
apprentice Frog.
you can try that:
-foo.ly-
#(module-define! (resolve-module '(guile-user)
Hi Nicolas,
Nicolas Sceaux wrote:
Le 10 mars 09 à 10:22, David Kastrup a écrit :
As some sort of progress,
'#{ \notemode { c e g } #}
puts out
(let ((parser-clone (ly:parser-clone parser))) (parse-string-result "
\\notemode { c e g } " parser-clone))
but since parser is #f, without quot
On Fri, Mar 13, 2009 at 8:50 AM, David Kastrup wrote:
> It is a bit disappointing since the info documentation with images is
> essential for really getting moving smoothly with Lilypond, and the
> procedure for producing them is so broken or obfuscate that none, I
> repeat none of _any_ lilypond
Nicolas Sceaux free.fr> writes:
>
> - test.ly -
> #(display (current-module))
> #(top-repl)
> ---
>
> ==>
>
> #
> guile> (current-module)
> #
> guile>
>
> So after invoking (top-repl), we are not the same module as the one
> used in the input file. That's why `parser'
John Mandereau writes:
> David Kastrup a écrit :
>> I don't think that is standard usage. install-info would be the norm
>> when available.
>>
> Will fix this, but see below my request.
>
>
make install bombs out, anyway:
Traceback (most recent call last):
File "/home/tm
Hi,
On Fri, 13 Mar 2009, Carl D. Sorensen wrote:
> > It might be nice if some developers made it into a habit to try
> > building from a freshly checked out tree from time to time without
> > reverting to their secret knowledge.
>
> Is it really necessary to get nasty?
Like I said in another
Hi,
On Fri, 13 Mar 2009, John Mandereau wrote:
> > It might be nice if some developers made it into a habit to try
> > building from a freshly checked out tree from time to time without
> > reverting to their secret knowledge.
>
> I spent a lot of time testing compilation and installation of In
David Kastrup a écrit :
I don't think that is standard usage. install-info would be the norm
when available.
Will fix this, but see below my request.
make install bombs out, anyway:
Traceback (most recent call last):
File "/home/tmp/lilypond/stepmake/bin/install.py", line 78, in
s
Cameron Horsburgh writes:
> On Fri, Mar 13, 2009 at 12:50:23PM +0100, David Kastrup wrote:
>>
>> make && sudo make install
>
>>
>> does not work.
>
> These work fine for me. They don't make much in the way of
> documentation (which is a good thing, AFAIAC), but these two commands
> install
On Fri, Mar 13, 2009 at 12:50:23PM +0100, David Kastrup wrote:
>
> make && sudo make install
>
> does not work.
These work fine for me. They don't make much in the way of
documentation (which is a good thing, AFAIAC), but these two commands
install lilypond for me perfectly well from whatev
Jan Nieuwenhuizen a écrit :
Op donderdag 12-03-2009 om 10:43 uur [tijdzone +0100], schreef John
Mandereau:
I compiled Python 2.6.1 and installed it in my home, setting
LD_LIBRARY_PATH to /home/lilydev.
So, does that help?
Not at all: I set PLATFORMS=linux-64 to avoid choking on od
Op vrijdag 13-03-2009 om 09:50 uur [tijdzone +0100], schreef John
Mandereau:
Hi John,
> ..and input/lsr too. I added toplevel info and intall-info target.
Great.
> This is already what is done, except that the relative symlink from
> prefix/share/info was wrong ;-)
Ah, oh. I see that we now
"Carl D. Sorensen" writes:
> On 3/13/09 4:51 AM, "David Kastrup" wrote:
>>
>> It might be nice if some developers made it into a habit to try
>> building from a freshly checked out tree from time to time without
>> reverting to their secret knowledge.
>
> Is it really necessary to get nasty?
I
John Mandereau writes:
> David Kastrup a écrit :
>> John Mandereau writes:
>>
>>> ..and input/lsr too. I added toplevel info and intall-info target.
>>>
>> No, you didn't.
> Oops, I meant info-install.
I don't think that is standard usage. install-info would be the norm
when available
Graham Percival a écrit :
I'm not clear about this, either. Actually, if anything
introduction.itely is going to die entirely (as part of the
web-gop stuff).
All right. I can't work on GOP in the 4 coming weeks: I must work on
translaed documentation compilation by translating
node names in
On 3/13/09 4:51 AM, "David Kastrup" wrote:
>
> It might be nice if some developers made it into a habit to try building
> from a freshly checked out tree from time to time without reverting to
> their secret knowledge.
Is it really necessary to get nasty?
Carl
>
> --
> David Kastrup
>
>
David Kastrup a écrit :
John Mandereau writes:
..and input/lsr too. I added toplevel info and intall-info target.
No, you didn't.
Oops, I meant info-install.
At least a freshly fetched lilypond copy has only
(according to bash programmable completion) the targets
install-help2m
On Fri, Mar 13, 2009 at 10:56:40AM +0100, John Mandereau wrote:
> Trevor Daniels a écrit :
>> Re your recent commits:
>>
>> shouldn't compile.itely and introduction.itely be in /devel rather
>> than /user?
> I don't understand why you suggest to place introduction.itely in devel/.
I'm not clear
John Mandereau writes:
> Jan Nieuwenhuizen a écrit :
>> Good points, everything should be fixed. Improvements could be
>>
>> * add toplevel info and install-info targets that redirect to
>> Documentation/user
>>
> ..and input/lsr too. I added toplevel info and intall-info target.
No, you
0;241;0cOn Fri, Mar 13, 2009 at 09:48:41AM +0100, John Mandereau wrote:
>
> "make web-install" is the recommended one by Application Usage, section
> Building documentation. I just added "make info-install", as suggested
> by Jan.
Ah, this is good. For some reason I don't quite understand I l
Trevor Daniels a écrit :
Re your recent commits:
shouldn't compile.itely and introduction.itely be in /devel rather
than /user?
I don't understand why you suggest to place introduction.itely in devel/.
As for compile.itely, it's easier to put it in user/, because
compilation of Texinfo docs i
John
Re your recent commits:
shouldn't compile.itely and introduction.itely be in /devel rather
than /user?
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
John Mandereau a écrit :
*WWW* targets must be called with out=www;
these targets are purposely undocumented and not listed in
"make help" because they are reserved for internal use or hacking.
BTW we probably should enclose all WWW targets in ifeq($(out),www) blocks.
Any thoughts on this before
Jan Nieuwenhuizen a écrit :
Good points, everything should be fixed. Improvements could be
* add toplevel info and install-info targets that redirect to
Documentation/user
..and input/lsr too. I added toplevel info and intall-info target.
* make info with images automagically (
2009/3/9 David Kastrup :
make prefix=/usr/local/lilypond install-info-WWW
make --no-builtin-rules -C Documentation/user install-info
make[1]: Entering directory `/lisa/lilypond/Documentation/user'
export LILYPOND_DATADIR=
export
PYTHONPATH=/lisa/lilypond/python/out:../../python/auxiliar:/lisa/li
Hello Yoshiki,
Sawada a écrit :
Do you mean that you will make node names and section titles translated only by
manual
(that is, they are translated in the source files, but not by the po file)?
Yes, that's it.
If it is correct, I want new commands as following rather than it:
@rinternalsn
29 matches
Mail list logo
