Le 02/11/2022 à 12:02, Federico Bruni a écrit :
Il giorno mer 2 nov 2022 alle 00:12:07 +0100, Jean Abou Samra
ha scritto:
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
Il giorno mer 2 nov 2022 alle 00:12:07 +0100, Jean Abou Samra
ha scritto:
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
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
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,
Le 19/10/2022 à 23:25, Carl Sorensen a écrit :
Can't we add a batch file or shell script that contains the command
(pointing to the lilypond binary) with the proper environment variable
set, and point Frescobaldi to the batch file/shell script, rather than
to the lilypond binary? We could
On Wed, Oct 19, 2022 at 2:54 PM Federico Bruni wrote:
>
>
> Il giorno mer 19 ott 2022 alle 18:06:16 +0200, Jean Abou Samra
> ha scritto:
> > Le 19/10/2022 à 17:25, Federico Bruni a écrit :
> >> You have to manually add `/app/dev/bin/lilypond` in Frescobaldi.
> >> (it's explained in the Github
Il giorno mer 19 ott 2022 alle 18:06:16 +0200, Jean Abou Samra
ha scritto:
Le 19/10/2022 à 17:25, Federico Bruni a écrit :
You have to manually add `/app/dev/bin/lilypond` in Frescobaldi.
(it's explained in the Github README)
It's a Frescobaldi limitation: it checks and adds only the
Le 19/10/2022 à 17:25, Federico Bruni a écrit :
You have to manually add `/app/dev/bin/lilypond` in Frescobaldi. (it's
explained in the Github README)
It's a Frescobaldi limitation: it checks and adds only the first
lilypond executable in the PATH.
OK, I may have invented a nonexistent
Il giorno mer 19 ott 2022 alle 17:12:31 +0200, Jean Abou Samra
ha scritto:
Basically it limits "never recompile" to files whose path starts
with "/app/".
I don't know Flatpak enough to be certain that /app/ is the right
path to check, though.
I think it's correct. I'll test and let you
Le 17/10/2022 à 22:23, Federico Bruni a écrit :
If anybody can provide a patch which can disable automatic
recompilation internal to Guile and LilyPond only, I'd be happy to
apply it.
I'm not sure how to test this but I think it should work:
From fa8f848423d6a104aad0e8ba8fdf87feedd0c4a6
Il giorno dom 16 ott 2022 alle 21:35:39 +0200, Jean Abou Samra
ha scritto:
Le 16/10/2022 à 20:41, Federico Bruni a écrit :
Il giorno dom 16 ott 2022 alle 12:18:25 +0200, Jean Abou Samra
ha scritto:
Le 14/10/2022 à 19:55, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
Le 16/10/2022 à 20:41, Federico Bruni a écrit :
Il giorno dom 16 ott 2022 alle 12:18:25 +0200, Jean Abou Samra
ha scritto:
Le 14/10/2022 à 19:55, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
For the records, another application using Guile (GNU Cash) had the
same
Il giorno dom 16 ott 2022 alle 12:18:25 +0200, Jean Abou Samra
ha scritto:
Le 14/10/2022 à 19:55, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
For the records, another application using Guile (GNU Cash) had the
same problem with flatpak three years ago.
Their workaround
Le 14/10/2022 à 19:55, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
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?
> Touching the .go files is not allowed by flatpak.
> I tried this and got an error:
>
> find /app/lib/guile/2.2/ -name *.go -exec touch '{}' \;
> [...]
> touch: cannot touch '/app/lib/guile/2.2/ccache/web/uri.go': Permission
> denied
>
> I'll have to find a solution when building the flatpak.
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
Il giorno mer 12 ott 2022 alle 21:23:03 +0200, Jonas Hahnfeld
ha scritto:
On Wed, 2022-10-12 at 00:30 +0200, Federico Bruni wrote:
Hi all
I think I've already seen discussions about this.
Can you please remind how to work around this error?
Guile looks at file timestamps and the .go
On Wed, 2022-10-12 at 00:30 +0200, Federico Bruni wrote:
> Hi all
>
> I think I've already seen discussions about this.
> Can you please remind how to work around this error?
Guile looks at file timestamps and the .go files must always be newer
than their .scm counterparts. Guile's build system
Federico Bruni writes:
> Hi all
>
> I think I've already seen discussions about this.
> Can you please remind how to work around this error?
>
> The 2.23.14 lilypond version built and bundled in Frescobaldi flatpak
> hangs forever and cannot compile any simple file, probably because
> it's
Hi all
I think I've already seen discussions about this.
Can you please remind how to work around this error?
The 2.23.14 lilypond version built and bundled in Frescobaldi flatpak
hangs forever and cannot compile any simple file, probably because it's
checking this stuff.
[
20 matches
Mail list logo
