guilev2-work [was: LilyPond boolean syntax? \true and \false]

[Thomas Morley]

2016-01-05 21:54 GMT+01:00 David Kastrup :
> Thomas Morley  writes:
>
[...]
>
>> Btw, you complained repeatedly about noone else but you cares about
>> moving to guilev2.  Otoh, I remember you wrote, all low hanging fruits
>> are done already.
>>
>> I always felt I wouldn't have the needed depth to help, I never asked
>> expecitely, though.
>
> The one thing that needs to be done next is seeing where current Guile
> stable-2.0 sits with respect to encoding problems.  I think I have a
> patch somewhere that is supposed to work with current versions.  But
> 2.0.12 (?) has not been released yet and anyway will take some time to
> make it into Ubuntu, so one needs to work with one's own compilations.
> And I was just too tired to pick this up again after the last round of
> fixes.
>
> At any rate, the encoding problems concern the C/Scheme interplay
> mostly.  So it's indeed not really a field where you specifically would
> not be likely to make progress once you did get stuck.
>
> Once the encoding business is past, the next stretches to be covered
> would likely be mostly Scheme-only, and then trying to bring a sensible
> way for precompiling/installing the Scheme files to bytecode into the
> Makefiles and cross-compilations.
>
> I don't know what the current Guile-2.0 situation is, but compiling
> Guile-2.1 (namely master) is insane.  It takes about a day on my
> computer.

Took me ~8h

> I don't really have much of a clue about Gub: it might be
> that this only needs to be done once per platform and then you can keep
> the stuff around for the next releases.
>
> --
> David Kastrup

Now I'm at:

~$ cd ../../usr/lib/x86_64-linux-gnu/guile-2.0/bin
[...]@[...] /usr/lib/x86_64-linux-gnu/guile-2.0/bin$ ./guile
GNU Guile 2.0.11
Copyright (C) 1995-2014 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guile-user)> (version)
$1 = "2.0.11"
scheme@(guile-user)>

Looks ok?
Next step would be (trying) to compile LilyPond with guilev2, right?
There is an option to do that, I vaguely remember. Let's see, if I find it ...

Then start tackling problems.

Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: guilev2-work [was: LilyPond boolean syntax? \true and \false]

[David Kastrup]

Thomas Morley  writes:

> [...]@[...] /usr/lib/x86_64-linux-gnu/guile-2.0/bin$ ./guile
> GNU Guile 2.0.11
> Copyright (C) 1995-2014 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(guile-user)> (version)
> $1 = "2.0.11"
> scheme@(guile-user)>
>
> Looks ok?

I seem to remember you had to run meta/guile in order to have it find
its modules.

> Next step would be (trying) to compile LilyPond with guilev2, right?

Sure.

> There is an option to do that, I vaguely remember. Let's see, if I find it ...

--with-guilev2 I think, but it's mentioned when doing ./configure --help

But you have to point it to your guilev2 libraries somehow.

>
> Then start tackling problems.

The files using utf-8 in the input bomb out or do nonsensical things.
Once you get there, I should have some patch here that might now work
better than before, using binary string streams from R6RS which
previously lost proper position in connection with #{ #}.

The \char markup's internal work function does not do the correct thing
in Guilev2 and probably needs some #ifdef for an alternate approach.
There is something ly_scm2string or the other way round that likely
needs to be split into several different variants (for latin1 which is a
euphemism for binary and for utf8, and possibly even for locale) and its
uses need to be checked and distributed among the appropriate version.

Copying of fonts into PDF files had some encoding problem I think, at
least for some fonts (either OTF or Type1 I think).

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Request for developer status on the issue tracker

[Trevor Daniels]

Heikki Tauriainen wrote Friday, January 08, 2016 1:04 PM

> I understand that running git-cl to create new issues requires
> developer status on the issue tracker at Sourceforge. I've just
> created a SourceForge account, and would kindly request developer
> access to the issue tracker (if possible). My username at SourceForge
> is "htlily".

Hi Heikki

Added to Devs as requested.  You'll be known in issues as "H T LilyPond".

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Request for developer status on the issue tracker

[Heikki Tauriainen]

Hi,

I understand that running git-cl to create new issues requires
developer status on the issue tracker at Sourceforge.  I've just
created a SourceForge account, and would kindly request developer
access to the issue tracker (if possible).  My username at SourceForge
is "htlily".

Thanks,
Heikki


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Request for developer status on the issue tracker

[Trevor Daniels]

Heikki, you wrote Friday, January 08, 2016 4:18 PM

> I still managed (like I always seem to do when I run git-cl with
> several months having passed since the last time...) to fail to submit
> a patch with git-cl fully successfully (*), so I had to create a new
> issue for the tracker (https://sourceforge.net/p/testlilyissues/issues/
> 4730/) manually. I'm sorry if I didn't get the values of all metadata
> fields right when creating the issue - I'd be grateful for any help
> whether something still needs to be fixed there.

Only the Owner field was missing, so I added your username,
and Accepted the Issue.
 
> (*) Failing with git-cl was simply my own fault, as I didn't anticipate
> (remember) that git-cl would need to open a web browser in the middle
> of the patch submission procedure - this didn't work well as I wasn't
> logged on in a GUI session, and had to abort the script.

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Request for developer status on the issue tracker

[Heikki Tauriainen]

On pe, 2016-01-08 at 13:54 +, Trevor Daniels wrote:
> 
> Added to Devs as requested.
> 
> Trevor

Thanks!

I still managed (like I always seem to do when I run git-cl with
several months having passed since the last time...) to fail to submit
a patch with git-cl fully successfully (*), so I had to create a new
issue for the tracker (https://sourceforge.net/p/testlilyissues/issues/
4730/) manually.  I'm sorry if I didn't get the values of all metadata
fields right when creating the issue - I'd be grateful for any help
whether something still needs to be fixed there.

(*) Failing with git-cl was simply my own fault, as I didn't anticipate
(remember) that git-cl would need to open a web browser in the middle
of the patch submission procedure - this didn't work well as I wasn't
logged on in a GUI session, and had to abort the script.

-- 
Heikki Tauriainen


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Request for developer status on the issue tracker

[Heikki Tauriainen]

On pe, 2016-01-08 at 16:36 +, Trevor Daniels wrote:
> Heikki, you wrote Friday, January 08, 2016 4:18 PM
> 
> > I still managed (like I always seem to do when I run git-cl with
> > several months having passed since the last time...) to fail to
> > submit
> > a patch with git-cl fully successfully (*), so I had to create a
> > new
> > issue for the tracker (https://sourceforge.net/p/testlilyissues/iss
> > ues/
> > 4730/) manually. I'm sorry if I didn't get the values of all
> > metadata
> > fields right when creating the issue - I'd be grateful for any help
> > whether something still needs to be fixed there.
> 
> Only the Owner field was missing, so I added your username,
> and Accepted the Issue.

Thank you!

Heikki


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel