@TheQuinbox Update to the prerelease WSL2. Install Ubuntu (this is the thing I got it to work with the best). Install Emacs 29: https://ubuntuhandbook.org/index.php/2023/08/gnu-emacs-29-1-ubuntu-ppa/

Now, apt install ffmpeg, tcl*, tk*, mplayer, libasound*, sox, mpg123, and make sure tclx is installed too, apt install tclx. Oh also install build-essential

Now, git clone https://www.github.com/tvraman/emacspeak

cd emacspeak

make

Install Voxin if you have it.

make outloud

If it doesn't work, make sure build-essential is installed. If it still doesn't work, look at whatever it's failing with, and install the dev package of whatever it's failing with.

Now, go to the home directory:

cd ~/

nano .emacs.el

(load-file "~/emacspeak/lisp/emacspeak-setup.el")
(outloud)

and it should be working. If not, make sure you're on Win11, have WS2, and WSLG installed, and make sure packages are up to date with sudo apt update; sudo apt upgrade. the stars in package names (*), mean a wildcard character. I do this because I honestly don't know the exact dependencies of all this bullcrap just to get one thing to work. And if I try just the essentials, it doesn't work. So maybe someone smarter than me can make some kind of nix environment that works 100% of the time. Or just a script.

#emacspeak #emacs #wsl #wslg #foss #linux

Please boost for reach. Okay y'all, I made the issue. If anyone else is experiencing anything like this, please comment on the issue, or thumb it up or upvote it for higher visibility. This issue is about audio in the Windows Subsystem for Linux graphical support. After locking and unlocking the computer, audio is very sluggish, about a second of delay. It would definitely help me to not have to restart Emacs every 30 minutes. Audio not being sluggish after unlocking the computer could help others, people playing Linux games, or even Orca users. I can't get my Orca to work cause ATSPI can't connect to the system bus or something. Still, I love having Emacs and Emacspeak on my Windows computer!

#accessibility #wsl #wslg

https://github.com/microsoft/wslg/issues/1026

Hmm, yeah. Looks like upgrading WSL2 helped a bit. Now, every time I launch Emacs, it's fine and fast. But after an hour of not using it, it'll be sluggish. But restarting it makes it fast again. I'll make the issue and post it here so others can comment and upvote it.

#accessibility #WSL2 #WSLG

So I just launched Emacs with Emacspeak in WSL2, and it's just as fast as on an actual Linux system. Trouble is, I can't get it to work every time.

#wsl #windows #wslg #win11

Meh. After updating #WSL today, I started receiving RDP popups saying that the "identity of remote computer could not be verified" and asking whether I wanted to connect it anyway. Seems to be this issue related #WSLg: https://github.com/microsoft/wslg/issues/997

There is a workaround of disabling WSLg which works for me: https://github.com/microsoft/WSL/issues/9347

100 days of code BASH edition

💻 Day 4 created my own system variable, made persistent within the .bashrc file.
[export hoy="$((date +"%H") | awk '{if ($1 < 12) print "morning"; else if ($1 >= 12 && 1 < 17) print "afternoon"; else if ($1 >= 17 && $1 < 20) print "evening"; else print "night";}')"] (OpenAI GPT-3 script with few corrections) Displays the time of day in morning/afternoon/evening/and night format!

#BASH #Linux #Kali #WSLg #100DasyOfCode #BashScript #Calendar #Time #bashrc

100 days of code BASH edition! :linux:

Day 3, expanding on the previous script adding more statements to display more system variables dealing with time formats and calendars.

#BASH #Linux #Kali #WSLg #100DasyOfCode #BashScript #Calendar #Time #TimeZones

100 days of code - BASH edition!

Day 2, using what I got from Open AI GTP-3, I expanded the script and made a few other statements to display additional system variables.

#BASH #Linux #Kali #WSLg #100DasyOfCode #OpenAi #GTP3 #BashScript

Incidentally, #neovim-qt works GREAT under #wslg!

Anyone who doesn't see why anyone would want to run WSL isn't looking very hard :) The #linux desktop is seriously amazeballs but it can't be all things to all people, and IMO sharing all that beautiful 100% FLOSS GUI app love with the #windows world is a win for all parties concerned.

right now it seems that #WSLg applications don't respond to #Windows #snapping commands. Curious if anyone knows a way to get around this or if this is coming to #WSL anytime soon?

#Wayland RDP Server with audio using #Microsoft's #WSLg stack

I wonder that Microsoft did not stole Wayland already. They already took Vmware or KVM and named it sandbox, stole KDE GUI and called it Aero.

Blog post
https://blog.jacobstoner.com/wayweston-rdp/

I've loved #wsl for a long time, the availability of #wslg on #windows10 and integration of #systemd only exponentially increase my fondness. kudos to the folks at #microsoft.

@FritzkeinWitz @stsz

Ich nutze #wsl2 mit #wslg seit Monaten auf meinem #windows11 Arbeitsplatz-PC und bin sehr zufrieden damit. Würde zwar lieber komplett auf #windows verzichten aber der Arbeitgeber will halt anders.

Mache aber nichts aufregendes damit, keine Docker Container oder sowas.
Nur ein paar einfache CLI und GUI Tools.

EFF YEAH! #wslg #wsl #wsl2

Great job, #Microsoft. No, seriously, this isn't sarcasm.

Current iteration of trying to get #wsl and #wslg working:

- Uninstalled the Microsoft Store version of WSL
- Removed the Windows Feature version of WSL
- Reboot
- Install Microsoft Store version of WSL
- run `wsl --install` in an admin command promt
- reboot

Currently waiting on said reboot. As a certain #hachyderm founder says: Hold on to your butts!

#wsl has prevailed for the time being. I can't get past this error:

To be clear, my WSL instances are still running just fine, but I cannot, for the life of me, use the version that's on the Microsoft Store, which means I can't use #WSLg :(

Hmm. . .or . . .not? Okay, still troubleshooting. #wsl2 #wslg are giving me some grief, but getting it to work will be worth it.

Hey #wsl nerds, if you're trying to get #wslg working, and you've had WSL installed for a while, you probably forgot that you need to go in and _disable_ the "Feature" version of WSL. Then you can start the "microsoft store" version normally, and wslg should be working!