Thank you #wsl2 team at #msft

Today I discovered that you folks have been working hard on #wslg - I can now run graphical apps from #wezterm and everything works like a treat!

With a recent #WSL #Ubuntu update, my #neovim started blowing up when I tried to paste in #neovim

I use #tmux so I don't care about all the #Windows clipboard hoo-ha others use. I just need cut and paste within tmux to work.

Unfortunately, because today in #WSLg you get Wayland but without the wayland server and commensurate socket, @neovim sees $WAYLAND_DISPLAY set, tries to run wl-copy and KABOOM.

Here's the bodge I'm using. If we detect WSL, we unset WAYLAND_DISPLAY so I can work but also add a 'wway' alias in case I want to futz around with Wayland GUI apps.

Under WSL, we KINDA have Wayland, but not really, and that blows up Neovim. Ungh. :)

Add an alias so if we actually WANT the pseudo wayland, we can haz.

if [[ $(uname -r | grep "microsoft") ]] then
unset WAYLAND_DISPLAY
alias wway='export WAYLAND_DISPLAY=wayland-0'
fi

The #WSLg experience

If you are working with #bevyengine or other #rustlang (particularly GUI) development, and you want to work in #wsl, check out the guides I have written in Bevy Cheatbook: https://bevy-cheatbook.github.io/platforms/windows/wsl2.html

I show two different ways of building and running your app from WSL: cross-compilation (which is actually not that hard to set up in Linux), letting you run #windows builds of your game from #wsl, or Microsoft's #WSLg, letting you run #linux builds of your game with limited performance.

Try it out!

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 to 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!

100 days of code BASH edition!

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

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 scripting right? Can't live with it, can't live without it!

One of the things I never paid attention to was learning bash scripting. Maybe, it is because I work mostly in the Windows environment. Linux is not a required skill where I work but does come in handy when trying out things. Most of my Linux work has been done through a GUI and rarely use the command line for anything.

My sister asked me about running an Ubuntu GUI software, and I directed her to #WSLg.

Now it turns out she trying to run a complex web application for libraries- #Koha.

Hope she will succeed. I will show her a docker-compose solution.

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?

As someone who uses both #Windows and #Linux daily, this is a huge quality-of-life boost:

https://arstechnica.com/gadgets/2022/11/windows-subsystem-for-linux-with-gui-apps-launches-for-windows-10/

#Windows10 #Ubuntu #WSL2 #WSLg

Here's Task Manager / System Monitor / Notepad / Mousepad all running side-by-side on my almost-10-year-old personal HP laptop.

#WSL #WSL2 #WSLg
I fired up xterm and UXTerm from WSL Ubuntu. Both of them look bad because neither of them are compatible with the fancy NerdFont I use with oh-my-zsh in both Windows Terminal and gnome-terminal.

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.

#WSL blues: Now that I've installed the MS Store WSL app with #WSLg... gedit won't run anymore. I get this Python traceback saying I don't have a hand in my cursor file. I'll have to find a solution sometime, like resetting my themes. But not tonight. There's also the problem I'm having with sound in Linux VLC.

But those and other problems will have to wait till later...

Next test: gnome-terminal. Instead of crashing like it did in old WSL2, it's now blazingly fast, maybe even faster than Windows Terminal (which admittedly is a really slick app I really love).

gedit, on the other hand, crashes. No problem though, as I prefer to invoke Notepad++ from WSL.

Next: installing VLC (obligatory app in Linux as well as Windows). Having problems with sound I'll have to deal with. But hey, it plays DVDs.