Re: WSL - Visual Studio Code - point and click
Hi Andrew I agree completely about registry changes but this one's easily undo-able. I'm just experimenting really - I've got Arch Linux working well now in Virtualbox and Lilypond/Frescobaldi also running well. Damian On 30 October 2020 at 15:15, Andrew Bernard wrote: Hi Damian, I know this may not be the answer you are wanting, but given that you have such a lot of heavy machinery on Windows to run LilyPond under Linux, why not simply run Debian or distro of your choice in Virtualbox, and you can even get VSC for Linux if you must. It's very easy to get point and click going in Linux. I am deeply averse to messing with the Windows 10 registry, no matter how clever the hack may be. But my feelings about the registry are not shared by all. I do all my professional work in Virtualbox Linux with Lilypond happily pointing and clicking away for years. On this list some time ago I posted a HOWTO for Ubuntu in this area, and the NR of course has some other useful info for Linux. Andrew On Sat, 31 Oct 2020 at 01:33, damianlegassick wrote: I've got WSL running fine with a Debian distro, Lilypond working fine, Visual Studio Code doing it's remote thing and Sumatra picking up all the changes in pdf back on the Windows side. but no point and click.
Re: WSL - Visual Studio Code - point and click
Hi Damian, I know this may not be the answer you are wanting, but given that you have such a lot of heavy machinery on Windows to run LilyPond under Linux, why not simply run Debian or distro of your choice in Virtualbox, and you can even get VSC for Linux if you must. It's very easy to get point and click going in Linux. I am deeply averse to messing with the Windows 10 registry, no matter how clever the hack may be. But my feelings about the registry are not shared by all. I do all my professional work in Virtualbox Linux with Lilypond happily pointing and clicking away for years. On this list some time ago I posted a HOWTO for Ubuntu in this area, and the NR of course has some other useful info for Linux. Andrew On Sat, 31 Oct 2020 at 01:33, damianlegassick wrote: > I've got WSL running fine with a Debian distro, Lilypond working fine, Visual > Studio Code doing it's remote thing and Sumatra picking up all the changes in > pdf back on the Windows side. > > but no point and click. >
Re: WSL - Visual Studio Code - point and click
On 30 October 2020 at 14:34, damianlegassick wrote: Hi I've got WSL running fine with a Debian distro, Lilypond working fine, Visual Studio Code doing it's remote thing and Sumatra picking up all the changes in pdf back on the Windows side. but no point and click. I tried to hack Aaron Hill's answer from a couple of years ago https://www.mail-archive.com/lilypond-user@gnu.org/msg129393.html but no joy (it could be me of course) Anyone out there got a method for Windows 10 64bit and current VSC/WSL2 etc? thanks Damian This is how far I've got: textedit.reg: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Classes\textedit] "URL Protocol"="" @="URL:textedit" [HKEY_CURRENT_USER\Software\Classes\textedit\shell] [HKEY_CURRENT_USER\Software\Classes\textedit\shell\open] [HKEY_CURRENT_USER\Software\Classes\textedit\shell\open\command] @="C:\\Tools\\textedit\\textedit.cmd %1" textedit.cmd: @ECHO OFF SETLOCAL SET CODE=/mnt/c/Users/damia/AppData/Local/Programs/Microsoft\ VS\ Code/bin/code SET URL=vscode://file/`/bin/wslpath -m %%(file)s`:%%(line)s:%%(column)s SET ENV=/usr/bin/env -i LYEDITOR='%CODE% --open-url %URL%' SET CMD=/usr/local/bin/lilypond-invoke-editor %* C:\Windows\System32\wsl.exe %ENV% %CMD%
WSL - Visual Studio Code - point and click
Hi I've got WSL running fine with a Debian distro, Lilypond working fine, Visual Studio Code doing it's remote thing and Sumatra picking up all the changes in pdf back on the Windows side. but no point and click. I tried to hack Aaron Hill's answer from a couple of years ago https://www.mail-archive.com/lilypond-user@gnu.org/msg129393.html but no joy (it could be me of course) Anyone out there got a method for Windows 10 64bit and current VSC/WSL2 etc? thanks Damian
