home.social

#wslg — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #wslg, aggregated by home.social.

fetched live
  1. this is a very specific nerdsnipe: did anyone manage to get the linux IM (the input method, not the instant messenger) working in linux gui apps run via wslg on windows without running a full linux graphic shell?

    NOTE: i've tried most of what is findable on the web, including starting the IM engines manually and modifying wsl's weston implementation config, to no avail.

    not being able to use the XCompose sequences in these apps is extremely annoying.

    (the native windows apps are manageable via wincompose, and i dread for the day it stops working, because the last update was a while ago.)

    #WSL #WSLg

  2. this is a very specific nerdsnipe: did anyone manage to get the linux IM (the input method, not the instant messenger) working in linux gui apps run via wslg on windows without running a full linux graphic shell?

    NOTE: i've tried most of what is findable on the web, including starting the IM engines manually and modifying wsl's weston implementation config, to no avail.

    not being able to use the XCompose sequences in these apps is extremely annoying.

    (the native windows apps are manageable via wincompose, and i dread for the day it stops working, because the last update was a while ago.)

    #WSL #WSLg

  3. this is a very specific nerdsnipe: did anyone manage to get the linux IM (the input method, not the instant messenger) working in linux gui apps run via wslg on windows without running a full linux graphic shell?

    NOTE: i've tried most of what is findable on the web, including starting the IM engines manually and modifying wsl's weston implementation config, to no avail.

    not being able to use the XCompose sequences in these apps is extremely annoying.

    (the native windows apps are manageable via wincompose, and i dread for the day it stops working, because the last update was a while ago.)

    #WSL #WSLg

  4. this is a very specific nerdsnipe: did anyone manage to get the linux IM (the input method, not the instant messenger) working in linux gui apps run via wslg on windows without running a full linux graphic shell?

    NOTE: i've tried most of what is findable on the web, including starting the IM engines manually and modifying wsl's weston implementation config, to no avail.

    not being able to use the XCompose sequences in these apps is extremely annoying.

    (the native windows apps are manageable via wincompose, and i dread for the day it stops working, because the last update was a while ago.)

    #WSL #WSLg

  5. this is a very specific nerdsnipe: did anyone manage to get the linux IM (the input method, not the instant messenger) working in linux gui apps run via wslg on windows without running a full linux graphic shell?

    NOTE: i've tried most of what is findable on the web, including starting the IM engines manually and modifying wsl's weston implementation config, to no avail.

    not being able to use the XCompose sequences in these apps is extremely annoying.

    (the native windows apps are manageable via wincompose, and i dread for the day it stops working, because the last update was a while ago.)

    #WSL #WSLg

  6. 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!

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

  8. 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!

  9. 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!

  10. 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!

  11. #WSLg#IMM32#TSF#IMEが 使えるわけではないので、日本の衰退を感じています (中国勢から文句言われないの?) #WSL #InputMethod

  12. #WSLg#IMM32#TSF#IMEが 使えるわけではないので、日本の衰退を感じています (中国勢から文句言われないの?) #WSL #InputMethod

  13. 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

  14. 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

  15. 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

  16. 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

  17. 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

  18. 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: bevy-cheatbook.github.io/platf

    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!

  19. 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: bevy-cheatbook.github.io/platf

    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!

  20. 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: bevy-cheatbook.github.io/platf

    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!

  21. 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: bevy-cheatbook.github.io/platf

    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!

  22. 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: bevy-cheatbook.github.io/platf

    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!

  23. 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: github.com/microsoft/wslg/issu

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

  24. Meh. After updating 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 : github.com/microsoft/wslg/issu

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

  25. 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

  26. 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

  27. 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

  28. 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

  29. 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

  30. 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

  31. 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

  32. 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

  33. 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

  34. 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

  35. 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

  36. 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

  37. 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.

    #Bash #BashScript #Linux #Ubuntu #Kali #Windows #WSLg #WSL

  38. 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.

    #Bash #BashScript #Linux #Ubuntu #Kali #Windows #WSLg #WSL

  39. 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.

    #Bash #BashScript #Linux #Ubuntu #Kali #Windows #WSLg #WSL

  40. 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.

    #Bash #BashScript #Linux #Ubuntu #Kali #Windows #WSLg #WSL

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

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

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

  42. 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.

  43. Twisted idea of the day: put Steam Deck's OS into WSL2.

    (I just installed #WSL Debian on a new Windows 10 installation and discovered that #WSLg was, after all, made to work on Windows 10 as well. Whoever at Microsoft is responsible, thank you! I'm not big on Windows, but when I power on my desktop machine that i use for games, it'll be nice to be able to easily do Linuxish gamedev as well, without having to enable Secure Boot or buy a TPM2 machine apart from my Steam Deck.)
  44. Twisted idea of the day: put Steam Deck's OS into WSL2.

    (I just installed #WSL Debian on a new Windows 10 installation and discovered that #WSLg was, after all, made to work on Windows 10 as well. Whoever at Microsoft is responsible, thank you! I'm not big on Windows, but when I power on my desktop machine that i use for games, it'll be nice to be able to easily do Linuxish gamedev as well, without having to enable Secure Boot or buy a TPM2 machine apart from my Steam Deck.)
  45. 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.

  46. 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.

  47. 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.

  48. 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.

  49. 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.

  50. 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?

  51. 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?

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