I'd be happy to help test as well.
On Wed, Dec 19, 2018, 9:32 AM Michael Gerdau
> > Indeed, it's not a real problem to compose a special command line for
> WSL Windows - if we know exactly how it should look like.
> > Testing would be a little bit awkward, though
>
> I‘d be happy to test it.
>
>
OK, great.
First step would be running Frescobaldi from its Git repository
(and at that occasion test if the description is accurate and also works
for Windows 10):
https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows
Am 19.12.18 um 18:54 schrieb Saul Tobin:
I'd
> First step would be running Frescobaldi from its Git repository
> (and at that occasion test if the description is accurate and also works
> for Windows 10):
> https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows
Commenting as I go:
These are the discrepancies so
> How does one calculate the extra numbers needing to be for the spacing OUT
> of notes as the feather speed up slow down. They always look spaced tight
> together as real notes just beamed differently. When you engrave a feather
> beam measure should youy first figure out how many notes you
On 2018-12-19 2:17 am, Michael Gerdau wrote:
Not really.
What I *can* say is this:
* LilyPond installations are registered in Frescobaldi by pointing
to
their executable.
* Frescobaldi calculates a path relative to that executable and adds
that to the library path in the LilyPond
Am 19. Dezember 2018 11:53:26 MEZ schrieb Aaron Hill :
>On 2018-12-19 2:17 am, Michael Gerdau wrote:
>>> Not really.
>>> What I *can* say is this:
>>>
>>> * LilyPond installations are registered in Frescobaldi by pointing
>
>>> to
>>> their executable.
>>> * Frescobaldi calculates a
> Not really.
> What I *can* say is this:
>
> * LilyPond installations are registered in Frescobaldi by pointing to
> their executable.
> * Frescobaldi calculates a path relative to that executable and adds
> that to the library path in the LilyPond process's environment
>
> I have
Am 19.12.18 um 08:09 schrieb Aaron Hill:
On 2018-12-18 10:51 pm, Urs Liska wrote:
This UI is populated by running LilyPond with the
-dshow-available-fonts option, so it actually displays what LilyPond
can really use.
Ah, that greatly reduces confusion.
However, my point still stands that
> How does one launch Linux programs then? Is that some specific "WSL Shell"
> that you start and then have a bash or something? And this does mean theWSL
> can only be used to do stuff on the Linux command line, no way to use Linux
> commands triggered from Windows applications?
Yes.
As the
On 2018-12-19 3:43 am, Urs Liska wrote:
Am 19. Dezember 2018 11:53:26 MEZ schrieb Aaron Hill
:
But if Frescobaldi needs to have a path to the LilyPond installation,
then it can never be made to work with WSL. There is no* path to the
WSL file system that a Windows program can access. Instead,
> The Windows program "wsl.exe" is the interop program that ties things
> together. You can call it and pass it a command to be executed within
> the WSL environment.
>
> So, while I can simply say "lilypond" in a WSL shell, under a Windows
> shell I need to say "wsl lilypond" to have the
Am 19.12.18 um 17:12 schrieb Michael Gerdau:
The Windows program "wsl.exe" is the interop program that ties things
together. You can call it and pass it a command to be executed within
the WSL environment.
So, while I can simply say "lilypond" in a WSL shell, under a Windows
shell I need to
Aaron Hill writes:
> On 2018-12-18 9:26 pm, Saul Tobin wrote:
>> 1) Is there a technical obstacle or other reason preventing a Windows
>> 64-bit build?
>
> I would presume that GUB can target 64-bit MinGW,
I should be surprised, given just when GUB was under active development.
It probably is
> Indeed, it's not a real problem to compose a special command line for WSL
> Windows - if we know exactly how it should look like.
> Testing would be a little bit awkward, though
I‘d be happy to test it.
Kind regards,
Michael
___
lilypond-user
14 matches
Mail list logo