Re: source file ... .scm newer than compiled ... .go file

2022-11-01 Thread Jean Abou Samra 

Le 01/11/2022 à 23:58, Federico Bruni a écrit :
Today I noticed that the current Frescobaldi flatpak (LilyPond 
2.23.80) doesn't hang, but it always prints a wall of annoying 
messages like:

[...]
I though that disabling Scheme recompilation would have also stopped 
this check.


Here's the PR where I introduced the change:
https://github.com/flathub/org.frescobaldi.Frescobaldi/pull/14

How can I disable these messages?



Your patch to Guile disables recompilation with a "return 1;"
at the end of the function but keeps the logic of the check and
the messages. Just additionally remove the code just above the line
it's touching, or add "return 1;" at the beginning of the function
rather than at the end.

Re: source file ... .scm newer than compiled ... .go file

2022-11-01 Thread Federico Bruni 




Il giorno gio 13 ott 2022 alle 00:29:15 +0200, Federico Bruni 
 ha scritto:
Il giorno mer 12 ott 2022 alle 23:59:32 +0200, Federico Bruni 
 ha scritto:

I'll have to find a solution when building the flatpak.
Waiting for minutes or hours while CPU hits 100% is not an option.


For the records, another application using Guile (GNU Cash) had the 
same problem with flatpak three years ago.

Their workaround was disabling recompilation. Bad idea or good idea?
https://github.com/flathub/org.gnucash.GnuCash/blob/master/patches/0001-Never-recompile.patch

Open issue which did not receive any feedback from flatpak developers:
https://github.com/flatpak/flatpak/issues/3064



Today I noticed that the current Frescobaldi flatpak (LilyPond 2.23.80) 
doesn't hang, but it always prints a wall of annoying messages like:


%

lilypond 2.23.80 [Senza nome] in avvio...
;;; note: source file /app/share/guile/2.2/ice-9/psyntax-pp.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/ice-9/psyntax-pp.go

;;; note: source file /app/share/guile/2.2/srfi/srfi-1.scm
;;;   newer than compiled /app/lib/guile/2.2/ccache/srfi/srfi-1.go
;;; note: source file /app/share/guile/2.2/srfi/srfi-9.scm
;;;   newer than compiled /app/lib/guile/2.2/ccache/srfi/srfi-9.go
;;; note: source file /app/share/guile/2.2/srfi/srfi-9/gnu.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/srfi/srfi-9/gnu.go

;;; note: source file /app/share/guile/2.2/srfi/srfi-11.scm
;;;   newer than compiled /app/lib/guile/2.2/ccache/srfi/srfi-11.go
;;; note: source file /app/share/guile/2.2/rnrs/bytevectors.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/rnrs/bytevectors.go

;;; note: source file /app/share/guile/2.2/system/base/compile.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/system/base/compile.go

;;; note: source file /app/share/guile/2.2/system/vm/vm.scm
;;;   newer than compiled /app/lib/guile/2.2/ccache/system/vm/vm.go
;;; note: source file /app/share/guile/2.2/language/tree-il/optimize.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/tree-il/optimize.go
;;; note: source file 
/app/share/guile/2.2/language/tree-il/primitives.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/tree-il/primitives.go

;;; note: source file /app/share/guile/2.2/language/tree-il/peval.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/tree-il/peval.go

;;; note: source file /app/share/guile/2.2/language/tree-il/effects.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/tree-il/effects.go
;;; note: source file 
/app/share/guile/2.2/language/tree-il/fix-letrec.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/tree-il/fix-letrec.go

;;; note: source file /app/share/guile/2.2/language/cps/optimize.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/optimize.go

;;; note: source file /app/share/guile/2.2/language/cps/constructors.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/constructors.go

;;; note: source file /app/share/guile/2.2/language/cps.scm
;;;   newer than compiled /app/lib/guile/2.2/ccache/language/cps.go
;;; note: source file /app/share/guile/2.2/language/cps/intmap.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/intmap.go

;;; note: source file /app/share/guile/2.2/language/cps/with-cps.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/with-cps.go
;;; note: source file 
/app/share/guile/2.2/language/cps/contification.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/contification.go

;;; note: source file /app/share/guile/2.2/language/cps/renumber.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/renumber.go

;;; note: source file /app/share/guile/2.2/language/cps/cse.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/cse.go
;;; note: source file 
/app/share/guile/2.2/language/cps/effects-analysis.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/effects-analysis.go

;;; note: source file /app/share/guile/2.2/language/cps/dce.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/dce.go

;;; note: source file /app/share/guile/2.2/language/cps/types.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/types.go

;;; note: source file /app/share/guile/2.2/language/cps/licm.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/licm.go

;;; note: source file /app/share/guile/2.2/language/cps/peel-loops.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/peel-loops.go

;;; note: source file /app/share/guile/2.2/language/cps/simplify.scm
;;;   newer than compiled 
/app/lib/guile/2.2/ccache/language/cps/simplify.go
;;; note: source file

Re: texi2any upgrade: Is there a regtest showing the results needed?

2022-11-01 Thread Karlin High 

On 11/1/2022 4:44 PM, Jean Abou Samra wrote:
As Jonas said: you are welcome to work on this, but be prepared for a 
bumpy ride.


Provided the expectations stay low and long-term, I have a pretty deep 
patience for whatever community process is needed along the way.


Feedback like this regarding best approaches is appreciated. My coding 
background is Microsoft Office Visual Basic for Applications, which is 
not the best foundation for an effort like the texi2any upgrade.

--
Karlin High
Missouri, USA

Re: texi2any upgrade: Is there a regtest showing the results needed?

2022-11-01 Thread Jean Abou Samra 

Le 01/11/2022 à 14:54, Karlin High a écrit :

If not, does it seem like anything worth pursuing?



Not to me, because the code to port is in our texi2html configuration 
file, not the Texinfo sources themselves. The basic Texinfo language is 
the same on both sides, it is the configuration that changes.


In your shoes, I would start by just making the build system use 
texi2any without configuration and see what happens.


As Jonas said: you are welcome to work on this, but be prepared for a 
bumpy ride.


Best,
Jean

Re: weird error engraving two files with 2.23.14

2022-11-01 Thread Jean Abou Samra 

Le 01/11/2022 à 23:16, Han-Wen Nienhuys a écrit :

Some PDF metadata features are missing, IIRC.



Off the top: -dembed-source-code, and PDF outlines. There are also some 
obscure font features like -dgs-load-lily-fonts.

Re: weird error engraving two files with 2.23.14

2022-11-01 Thread Han-Wen Nienhuys 
On Thu, Oct 13, 2022 at 1:28 PM Kevin Barry  wrote:
> > It works great using the cairo backend!
> > I wanted to test it so I think I'll set it as default for all my scores.
> > What are the current drawbacks? There's any page in the docs about cairo?
>
> It looks like there was some kind of mixup adding info about cairo to
> the changes doc. I can see the doc code in this diff:
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1651/diffs?commit_id=1df07dd726ff8bf16e60501080fcbd47b82ae6d4
> but it looks like that merge request somehow didn't end up including
> that. I'll see about preparing a patch for it.
>
> To summarise what's there: it should be an improvement over ghostscript,
> but it's still experimental and doesn't implement all of the features of
> the other backends (I can't remember what, if anything, is missing).

Some PDF metadata features are missing, IIRC. Also, raw PostScript
only works if you export to PS, but not for PDF/PNG/SVG.


-- 
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen

Re: texi2any upgrade: Is there a regtest showing the results needed?

2022-11-01 Thread Werner LEMBERG 


> With the start-afresh approach for lilypond-texi2html.init, it seems
> to me the first thing that would be needed is a regtest or Minimal
> Working Example of sorts: A concise texinfo file calling for each
> feature or function needing equivalent replication in the upgrade.
> 
> Once the targeted version of texi2any is producing acceptable
> results from that file, then move on to testing on the full
> documentation.

I'm not sure this is worth the trouble.  The main reason is that we
have to take care of a *single instance only*, namely the LilyPond
documentation as shown at https://lilypond.org.  If something works
there, it's good enough.

However, what would be very helpful is to get Merge Request artifacts
(kind-of) for HTML documentation changes, too.  For example, the
artifacts could be a diff file filtered by a script to remove diff
noise, allowing to concentrate check the essential differences.


Werner

New French PO file for 'lilypond' (version 2.23.80)

2022-11-01 Thread Translation Project Robot 
Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'lilypond' has been submitted
by the French team of translators.  The file is available at:

https://translationproject.org/latest/lilypond/fr.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

https://translationproject.org/latest/lilypond/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

https://translationproject.org/domain/lilypond.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

The Translation Project robot, in the
name of your translation coordinator.

texi2any upgrade: Is there a regtest showing the results needed?

2022-11-01 Thread Karlin High 

On 10/25/2022 4:00 PM, Jonas Hahnfeld wrote:
> I think it may be better to rewrite the needed customizations more or
> less from scratch. From a few preliminary tests some time ago, many
> things will work very differently with texi2any; some customizations
> won't be necessary anymore (because there are options to get the same
> effect) and some new ones will be needed.
>
> From 



With the start-afresh approach for lilypond-texi2html.init, it seems to 
me the first thing that would be needed is a regtest or Minimal Working 
Example of sorts: A concise texinfo file calling for each feature or 
function needing equivalent replication in the upgrade.


Once the targeted version of texi2any is producing acceptable results 
from that file, then move on to testing on the full documentation.


I read the Contributors Guide, Chapter 9, Regression Tests, and did not 
see any references to something like this. Does anyone know if such a 
thing already exists?


If not, does it seem like anything worth pursuing?

Personally, I could see it aiding future upgrade efforts. And for my 
involvement in such efforts currently, I would almost need to do it 
regardless to fill in the gaps in my understanding of the codebase, 
Texinfo old and new, and what feature requests if any need sent upstream.

--
Karlin High
Missouri, USA