Le dimanche 07 mai 2023 à 15:44 +0100, Richard Shann a écrit :
>
> I couldn't follow up this suggestion because I don't have a way of
> building Denemo for Windows to experiment with. But it occurred to me
> that I *could* test this idea just by swapping the executables
> gspawn-win32-helper.exe
On Tue, 2023-04-04 at 12:03 +0200, Jean Abou Samra wrote:
> Le mardi 04 avril 2023 à 11:34 +0200, Jean Abou Samra a écrit :
> Le lundi 03 avril 2023 à 20:50 +0200, Jonas Hahnfeld via LilyPond
> user discussion a écrit :
> > This shouldn't be needed: g_spawn_sync internally uses a helper
> >
Le mardi 04 avril 2023 à 12:56 +0100, Richard Shann a écrit :
> I don't understand, I'm afraid. Denemo only makes calls to the g_spawn*
> functions as documented. The function might_be_console_process() is
> static - internal to glib - or rather to some executable that it calls,
>
On Tue, 2023-04-04 at 12:03 +0200, Jean Abou Samra wrote:
> Le mardi 04 avril 2023 à 11:34 +0200, Jean Abou Samra a écrit :
> Le lundi 03 avril 2023 à 20:50 +0200, Jonas Hahnfeld via LilyPond
> user discussion a écrit :
> > This shouldn't be needed: g_spawn_sync internally uses a helper
> >
Le mardi 04 avril 2023 à 11:03 +0100, Richard Shann a écrit :
> The documentation on -dlog-file doesn't specify where the file will
> appear in the case that a full path is not given,
I think it just gets put in the current working directory (as I would expect).
signature.asc
Description:
Le mardi 04 avril 2023 à 11:34 +0200, Jean Abou Samra a écrit :
> Le lundi 03 avril 2023 à 20:50 +0200, Jonas Hahnfeld via LilyPond user
> discussion a écrit :
>
> > This shouldn't be needed: g_spawn_sync internally uses a helper
> > executable that should take care exactly of this aspect.
On Tue, 2023-04-04 at 11:32 +0200, Jean Abou Samra wrote:
> Le mardi 04 avril 2023 à 10:29 +0100, Richard Shann a écrit :
> > The situation on Windows without lilypond-windows.exe is even worse
> > than I thought - the option -dlog-file no longer generates the log
> > file
> > into the prescribed
Le lundi 03 avril 2023 à 20:50 +0200, Jonas Hahnfeld via LilyPond user
discussion a écrit :
> This shouldn't be needed: g_spawn_sync internally uses a helper
> executable that should take care exactly of this aspect. LilyPond uses
> it internally to call Ghostscript.
Hmm, but Denemo is
Le mardi 04 avril 2023 à 10:29 +0100, Richard Shann a écrit :
> The situation on Windows without lilypond-windows.exe is even worse
> than I thought - the option -dlog-file no longer generates the log file
> into the prescribed place - instead the log is splashed onto the
> terminal box
The situation on Windows without lilypond-windows.exe is even worse
than I thought - the option -dlog-file no longer generates the log file
into the prescribed place - instead the log is splashed onto the
terminal box (which then vanishes when the typesetting is finished).
It means no error
On Mon, 2023-04-03 at 11:19 +0100, Richard Shann wrote:
> On Sun, 2023-04-02 at 11:54 -0700, Aaron Hill wrote:
> > I have never looked at Denemo or its source code, so what I am going
> > to say might not be so trivially applicable.
>
> You were quite right to be doubtful - Denemo tries to
On 2023-04-03 10:31 am, Jean Abou Samra wrote:
Le 3 avr. 2023 à 12:21, Richard Shann a
écrit :
Is there any chance the developers might re-instate the
lilypond-windows.exe?
Maybe. Is it as easy as compiling with -mconsole ? Does that have other
effects to take care of? Is there a use case
> Le 3 avr. 2023 à 12:21, Richard Shann a écrit :
>
> Is there any chance the developers might re-instate the
> lilypond-windows.exe?
Maybe. Is it as easy as compiling with -mconsole ? Does that have other effects
to take care of? Is there a use case where the current mode is important or
On 2023-04-03 3:19 am, Richard Shann wrote:
On Sun, 2023-04-02 at 11:54 -0700, Aaron Hill wrote:
I have never looked at Denemo or its source code, so what I am going
to
say might not be so trivially applicable.
But in the Win32 API, you can
call CreateProcess and use the process flag
On Sun, 2023-04-02 at 11:54 -0700, Aaron Hill wrote:
> On 2023-04-02 8:38 am, Richard Shann wrote:
> > there used to be an executable lilypond-windows.exe in addition to
> > the
> > lilypond.exe which has also vanished. I suspect it was compiled
> > using
> > the option
> >
> > -mconsole
> >
> >
On 2023-04-02 8:38 am, Richard Shann wrote:
there used to be an executable lilypond-windows.exe in addition to the
lilypond.exe which has also vanished. I suspect it was compiled using
the option
-mconsole
passed to gcc as this is how Denemo is compiled to avoid leaving a
terminal around that
On Sun, 2023-04-02 at 13:57 +0200, Robin Bannister wrote:
> Richard Shann wrote:
> > There was an option -dgui which allowed Denemo to run LilyPond in
> > the
> > background on Windows, but this has vanished without, as far as I
> > can
> > see, any entry in the Changes to account for it
> >
>
>
Richard Shann wrote:
There was an option -dgui which allowed Denemo to run LilyPond in the
background on Windows, but this has vanished without, as far as I can
see, any entry in the Changes to account for it
See
There was an option -dgui which allowed Denemo to run LilyPond in the
background on Windows, but this has vanished without, as far as I can
see, any entry in the Changes to account for it
https://lilypond.org/doc/v2.24/Documentation/changes-big-page
Is it possible for LilyPond 2.24 to be run in
19 matches
Mail list logo