home.social

#xephyr — Public Fediverse posts

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

  1. Just learned about #Xephyr for running a second x session inside the first one. Very cool. Can't believe I hadn't heard about it before now. Years and years ago, I used to routinely run a second session on vt8. Good for testing out different window managers or desktop environments or running things as a different user.

    Using Xephyr to troubleshoot #stumpwm - it starts and exits / crashes immediately. Testing a few things, so not giving up hope yet.

  2. オンライン勉強会などで画面?

    ?有する場合 Xephyr でメインと別の X server を起動してその画面を?

    ?有したりしています.

    ?

    ?れ子になった X の中でフルスクリーンにしたり,アプリケーションを切り替えたりしています.

    しかし,小江戸らぐやオープンソースカンファレンスなどで利用しているビデオミーティングアプリの Zoom では画面?

    ?有時に Xephyr が出てきません.Chromium や Firefox や Electron アプリでは一覧に出てきて Xephyr の画面?

    ?有もうまく行きます.

    仕方がないので Zoom での画面?

    ?有時は「画面の一部分」を使っています.

    今回画面の指定領域を仮想ディスプレイとして利用できる clipscreen でかんたんに画面?

    ?有ができないか試してみました.

    […]

    https://matoken.org/blog/2024/10/26/share-xephyr-screen-with-clipscreen-failed/

  3. I now added a screenshot of #qXmoji on github. People need to see screenshots for some reason (I'm no exception) 😄

    I wanted "default looks", so, disabled any #Qt theming and thought #fvwm3 with default config should be a very nice match for a tool targeting "plain #X11", and firing up a #Xephyr session, I was quite surprised how polished fvwm3's default config looks nowadays, even integrating #stalonetray when available 👍

    I still prefer my custom config, but nevertheless, great job 🙂

    github.com/Zirias/qxmoji

  4. @dani Haha 😎

    I'm running a (heavily configured) #fvwm3 here. This screenshot was just for demonstration that #dos2ansi and #showansi don't depend on any configuration, so this was a completely unconfigured X session in #Xephyr, which by default runs #twm.

    You can even see the test mode in #xterm can only use 8 colors (because this is what the default xterm #terminfo entry announces), still the #xterm windows launched by #showansi have full color support, they explicitly set the terminal name to "xterm-256colors".

  5. @dani Haha 😎

    I'm running a (heavily configured) #fvwm3 here. This screenshot was just for demonstration that #dos2ansi and #showansi don't depend on any configuration, so this was a completely unconfigured X session in #Xephyr, which by default runs #twm.

    You can even see the test mode in #xterm can only use 8 colors (because this is what the default xterm #terminfo entry announces), still the #xterm windows launched by #showansi have full color support, they explicitly set the terminal name to "xterm-256colors".

  6. @dani Haha 😎

    I'm running a (heavily configured) #fvwm3 here. This screenshot was just for demonstration that #dos2ansi and #showansi don't depend on any configuration, so this was a completely unconfigured X session in #Xephyr, which by default runs #twm.

    You can even see the test mode in #xterm can only use 8 colors (because this is what the default xterm #terminfo entry announces), still the #xterm windows launched by #showansi have full color support, they explicitly set the terminal name to "xterm-256colors".

  7. @dani Haha 😎

    I'm running a (heavily configured) #fvwm3 here. This screenshot was just for demonstration that #dos2ansi and #showansi don't depend on any configuration, so this was a completely unconfigured X session in #Xephyr, which by default runs #twm.

    You can even see the test mode in #xterm can only use 8 colors (because this is what the default xterm #terminfo entry announces), still the #xterm windows launched by #showansi have full color support, they explicitly set the terminal name to "xterm-256colors".

  8. @dani Haha 😎

    I'm running a (heavily configured) here. This screenshot was just for demonstration that and don't depend on any configuration, so this was a completely unconfigured X session in , which by default runs .

    You can even see the test mode in can only use 8 colors (because this is what the default xterm entry announces), still the windows launched by have full color support, they explicitly set the terminal name to "xterm-256colors".

  9. It's #archaic #x11 application time!

    This time, it's #xmcolor (the Motif Color Picker), written by Ti Kan. I believe this was written sometime in 1994. The embedded ident marker indicates: `@(#)xmcolor.c 1.11 94/12/05`

    This was developed using Xt and #motif, and provides a means of mixing one's own colours, as well as using pre-defined colours from `rgb.txt`. One could then select the hexadecimal string for that colour.

    It operates on 8-bit colour-depth displays only, which is why I have been running this inside #Xephyr so I can emulate this.

    To this day, it compiles just fine -- only very minor tweaking from myself. Not bad for a program that's ~28 years old!

    I really like how simple and self-contained so many of these applications were, and how much of a teaching aid it meant for someone to write them. The source file has 1066 lines in it -- quite a lot when you consider how much of that is Xt/Xm boilerplate.

    These days, you'd just use a colour-picker from google without giving it a second thought. #x11cp

  10. It's #archaic #x11 application time!

    This time, it's #xmcolor (the Motif Color Picker), written by Ti Kan. I believe this was written sometime in 1994. The embedded ident marker indicates: `@(#)xmcolor.c 1.11 94/12/05`

    This was developed using Xt and #motif, and provides a means of mixing one's own colours, as well as using pre-defined colours from `rgb.txt`. One could then select the hexadecimal string for that colour.

    It operates on 8-bit colour-depth displays only, which is why I have been running this inside #Xephyr so I can emulate this.

    To this day, it compiles just fine -- only very minor tweaking from myself. Not bad for a program that's ~28 years old!

    I really like how simple and self-contained so many of these applications were, and how much of a teaching aid it meant for someone to write them. The source file has 1066 lines in it -- quite a lot when you consider how much of that is Xt/Xm boilerplate.

    These days, you'd just use a colour-picker from google without giving it a second thought.

  11. It's #archaic #x11 application time!

    This time, it's #xmcolor (the Motif Color Picker), written by Ti Kan. I believe this was written sometime in 1994. The embedded ident marker indicates: `@(#)xmcolor.c 1.11 94/12/05`

    This was developed using Xt and #motif, and provides a means of mixing one's own colours, as well as using pre-defined colours from `rgb.txt`. One could then select the hexadecimal string for that colour.

    It operates on 8-bit colour-depth displays only, which is why I have been running this inside #Xephyr so I can emulate this.

    To this day, it compiles just fine -- only very minor tweaking from myself. Not bad for a program that's ~28 years old!

    I really like how simple and self-contained so many of these applications were, and how much of a teaching aid it meant for someone to write them. The source file has 1066 lines in it -- quite a lot when you consider how much of that is Xt/Xm boilerplate.

    These days, you'd just use a colour-picker from google without giving it a second thought. #x11cp

  12. It's #archaic #x11 application time!

    This time, it's #xmcolor (the Motif Color Picker), written by Ti Kan. I believe this was written sometime in 1994. The embedded ident marker indicates: `@(#)xmcolor.c 1.11 94/12/05`

    This was developed using Xt and #motif, and provides a means of mixing one's own colours, as well as using pre-defined colours from `rgb.txt`. One could then select the hexadecimal string for that colour.

    It operates on 8-bit colour-depth displays only, which is why I have been running this inside #Xephyr so I can emulate this.

    To this day, it compiles just fine -- only very minor tweaking from myself. Not bad for a program that's ~28 years old!

    I really like how simple and self-contained so many of these applications were, and how much of a teaching aid it meant for someone to write them. The source file has 1066 lines in it -- quite a lot when you consider how much of that is Xt/Xm boilerplate.

    These days, you'd just use a colour-picker from google without giving it a second thought.

  13. It's #archaic #x11 application time!

    This time, it's #xmcolor (the Motif Color Picker), written by Ti Kan. I believe this was written sometime in 1994. The embedded ident marker indicates: `@(#)xmcolor.c 1.11 94/12/05`

    This was developed using Xt and #motif, and provides a means of mixing one's own colours, as well as using pre-defined colours from `rgb.txt`. One could then select the hexadecimal string for that colour.

    It operates on 8-bit colour-depth displays only, which is why I have been running this inside #Xephyr so I can emulate this.

    To this day, it compiles just fine -- only very minor tweaking from myself. Not bad for a program that's ~28 years old!

    I really like how simple and self-contained so many of these applications were, and how much of a teaching aid it meant for someone to write them. The source file has 1066 lines in it -- quite a lot when you consider how much of that is Xt/Xm boilerplate.

    These days, you'd just use a colour-picker from google without giving it a second thought.

  14. Linux Fu: Raspberry Pi Desktop Headless - It seems to me there are two camps when it comes to the Raspberry Pi. Some people use them as little... more: hackaday.com/2020/06/01/linux- #hackadaycolumns #raspberrypi #linuxhacks #xephyr #linux #xnest #kde #x11