photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

247
active users

#xserver

0 posts0 participants0 posts today

Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.

Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login window

eugene-andrienko.com/en/it/202

Dragon’s notes · How to configure X11 in a simple way
More from Eugene :emacs: :freebsd:

Another change proposal was submitted to the Fedora Engineering Steering Committee (FESCo) for approval[1]:

Replace the #Xorg #Xserver with the X11Libre Xserver for #Fedora 43-

lists.fedoraproject.org/archiv

fedoraproject.org/wiki/Changes

Will be interesting to see how FESCo will react to it, but I'd be willing to bet that it will be rejected. And I'd assume that the change will be resubmitted in later cycles.

[1] reminder, anyone can submit such change proposals!

Replied in thread

@mrmasterkeyboard @cesarpose case in point:

Just because "My Little Distro" (#OS1337) runs of a single /etc/init file doesn't mean this is the "correct" or "authoritative" way to do it nor that this is scalabe at all.

  • Just 'let me cook' on @OS1337 because it's more of a 'learning exercise' rather than "production grade"...

Back to #Xorg: I do think that metux's actions really salted the fields re: #Xlibre and any #X11 releases!

GitHubOS1337/build/0.CORE/fdd/fs/etc/init at main · OS-1337/OS1337OS/1337 Project . Contribute to OS-1337/OS1337 development by creating an account on GitHub.
Replied in thread

@mrmasterkeyboard @cesarpose I mean, #Xorg - like #SysVinit - both have severe issues that just ain't gonna be addressable under reasonable expectations re: hardware support, compatibility and software support.

  • But there's a reason "Big Distros" and the community in general came to the conclusion that #Wayland and #SystemD are at worst 'necessary evils' and for the most part deliver a lot of quality-of-life features.

youtube.com/watch?v=o_AIw9bGogo

There is no "#conspiracy" of #BigTech wanting to kill #X11 or even sabotage #Xlibre for that matter. It's just that some folks have trouble letting go and acknowledge that #Xserver is kept on "life support" as #Xwayland so people can run their 25+ year old #Windows games in #Wine without going apeshit.

  • I mean, ask @fuchsiii about that effort, where she's basically "workarounding" wine devs by literally pulling a "#Steam compatibility layer" kind of trick and swapping "good known working" Wine versions in just before launching a game because that works for setups where you have one user playing one game at a time on one machine and where shuffling around files/symlinks is possible.

On #fvwm #xorg #windows #compatibility

With all the recent bullsh^H^H^Htalk about #xorg, I realised an interesting historical piece of information. As early as 1999, fvwm (and not twm, from which fvwm is based) supported a raised-over-unmanaged workaround.

Specifically, it was for the following XServer implementations:

"Hummingbird Communications Ltd."
"Network Computing Devices Inc."
"WRQ, Inc."

It looks as though there was a bug in these servers, where a raise of the windows was needed:

github.com/fvwmorg/fvwm3/blob/

From what I can tell:

Hummingbird Communications Ltd were acquired:

en.wikipedia.org/wiki/Hummingb.

Netwrok Computing Devices Inc:

en.wikipedia.org/wiki/Network_

Defunct, but they did purchase some dumb terminals (TekXPress ) from Tektronix

WRQ Inc:

en.wikipedia.org/wiki/The_Atta

I could find no further information other than the paragraph or so mentioned here.

If anyone has any additional information on the #XServer used and its quirks, I'd love to know.

This has been a piece of #fvwm history for over 30 years so I'd love to hear from anyone who has further insight, please. :)

GitHubfvwm3/fvwm/stack.c at 6000175467fada5d5329f2ecf9e1c0b99937b3ce · fvwmorg/fvwm3FVWM version 3 -- the successor to fvwm2. Contribute to fvwmorg/fvwm3 development by creating an account on GitHub.