The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Wed, 25 Jan 2023 07:45:44 +0000	[thread overview]
Message-ID: <3h5FEAegoTs6FrhHODiW-rBdB59dt_Rmr4G0PIw7flqaJLsmorgPsilm4f2aJkDud-qEljDjnCJcE1uY05Iw4HNQcyNG4W3wzVlLD0UZfLg=@protonmail.com> (raw)
In-Reply-To: <3e272d72-b77a-d347-b5c3-7ed19482e5af@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4258 bytes --]

I suspect even what with Wayland making the rounds, there'll probably be X around for a looooong time. My guess anyway. I just recently built an X setup from scratch on Linux, it wasn't too much of a pain save that the protocol headers have merged into the xorgproto package. I didn't realize this until I had already installed older versions of all the individual packages.

I was surprised to learn in the process that xterm is not distributed by XOrg, but by someone else. It even features in the default xdm session along with xconsole and xsm, so certainly considered a standard component of X, but distributed and maintained independently it seems.

Aa for the questions of the UNIX-ness of X, it started in Athena, which as I understand it was supposed to be relatively OS-agnostic distributed computing? In any case, the predecessor ran on a different OS, not sure how significant that is to the genesis of what would be called X or what OS it "started" on.

Aside from the ubiquitous X books (which I mean to add to my library...) USL also shipped a handful of books with SVR4 concerning both X and NeWS. I've only got the Xlib one but it seems to cover the basics pretty well. I'd be curious to compare it to the other set. One of these days I mean to round out that SVR4 documentation set.

There were probably materials in the SVR4.2 era as well but I haven't focused as much on those books. Dunno what if any documentation Novell then Caldera/SCO kept up with. I'd love a fresh round of print books, I much prefer paper for reference, but nowadays new tech material is most certainly second/third-hand rather than thoughtfully crafted by the team and those adjacent to whatever is being described. I love me a good primary source....

I've played with XQuartz a bit, mainly remote X from one of my Linux boxes. Kinda slow...but I did zero tuning so not sure what the expected performance of X-over-ssh is. In any case, given the ubiquity, I doubt we'll see X going anywhere soon, and even when it does eventually start to sunset, there'll probably be shims and wrappers for compatibility for a while longer. Plus, I don't know what the prospects are regarding Wayland and SVR4 derivs, but they're all happily running X still, and aren't necessarily getting any new large-scale development love, so likely will ride out with X.

- Matt G.
------- Original Message -------
On Tuesday, January 24th, 2023 at 5:46 PM, Will Senn <will.senn@gmail.com> wrote:

> All,
>
> If you think unix ends without x, just move along, nothing to see here. Otherwise, I thought I would share the subject of my latest post and a link with those of you interested in such things.
>
> Recently, I've been tooling around trying to wrap my head around x windows and wanted to give programming it a shot at the xlib level... on my mac, if possible. So, I bought a copy of Adrian Nye's Xlib Programming Manual for Version 11 R4/R5, aka Volume One of The Definitive Guides to the X Window System, published, get this... 30+ years ago, in 1992 :) and started reading like a madman. As usual, this was an example of great technical writing from the prior millenium, something rarely found today.
>
> Anyway, I hunted up the source code examples as published, unpacked them, did a few environmental things to my mac, and built my first xlib application from that source. A few tweaks to my XQuartz configuration and I was running the application in twm on my mac, with a root window.
>
> To read about it and see it in all of its glory, check it out here:
>
> https://decuser.github.io/operating-systems/mojave/x-windows/2023/01/24/x-windows-dev-on-mac.html
>
> The same sort of setup works with Linux, FreeBSD, or my latest environment DragonFly BSD. It's not the environment that I find interesting, but rather the X Window System itself, but this is my way of entering into that world. If you are interested in running X Windows, not as an integrated system on your mac (where x apps run in aqua windows), but with a 'regular' window manager, and you haven't figured out how, this is one way.
>
> On the provocateur front - is X part of unix? I mean this in oh so many nuanced ways, so read into it as you will. I would contend, torpedoes be damned, that it is :).
>
> Will

[-- Attachment #2: Type: text/html, Size: 5951 bytes --]

  reply	other threads:[~2023-01-25  7:46 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25  1:46 [TUHS] " Will Senn
2023-01-25  7:45 ` segaloco via TUHS [this message]
2023-01-25  8:00   ` [TUHS] " Lars Brinkhoff
2023-01-25 16:41   ` Rich Salz
2023-01-25 19:53     ` Theodore Ts'o
2023-01-25 20:04       ` Dan Cross
2023-01-25 20:23         ` Larry McVoy
2023-01-25 20:27           ` Chet Ramey
2023-01-27  4:49         ` Theodore Ts'o
2023-01-27 18:05           ` Henry Mensch
2023-01-27 18:24             ` Charles H Sauer (he/him)
2023-01-26 13:17       ` Marc Donner
2023-02-08 22:12       ` [TUHS] project athena (was Re: Setting up an X Development Environment for Mac OS) Jonathan Gray
2023-02-09  2:51         ` [TUHS] " Theodore Ts'o
2023-02-11  0:13           ` Henry Mensch
2023-02-11  0:53             ` Larry McVoy
2023-02-11  3:51               ` Jonathan Gray
2023-02-11 14:48                 ` Larry McVoy
2023-02-12  2:26                   ` Jonathan Gray
2023-02-12 21:35                   ` Henry Mensch
2023-02-11  0:23         ` Henry Mensch
2023-01-25 20:38 [TUHS] Re: Setting up an X Development Environment for Mac OS Noel Chiappa
2023-01-25 21:25 ` Clem Cole
2023-01-26  6:30   ` Lars Brinkhoff
2023-01-26 10:56     ` Ralph Corderoy
2023-01-26 12:01       ` arnold
2023-01-26 13:25         ` Lars Brinkhoff
2023-01-26 15:28       ` [TUHS] " josh
2023-01-26 16:07         ` [TUHS] " segaloco via TUHS
2023-01-26 16:48           ` emanuel stiebler
2023-01-26 21:19             ` segaloco via TUHS
2023-01-26 22:51               ` Andy Kosela
2023-01-27  0:48                 ` segaloco via TUHS
2023-01-27  4:07                   ` Will Senn
2023-01-27 14:08                     ` Chet Ramey
2023-01-27 14:49                       ` Ron Natalie
2023-01-27 15:53                     ` Dan Cross
2023-01-27 14:17             ` Ralph Corderoy
2023-01-27 13:56         ` Ralph Corderoy
2023-01-27 14:54           ` Ron Natalie
2023-01-27 16:10             ` Larry McVoy
2023-01-28 22:15               ` Dave Horsfall
2023-01-29  0:31                 ` Kevin Bowling
2023-01-29 11:07                   ` emanuel stiebler
2023-01-27 21:42             ` Tom Perrine
2023-01-28  2:18               ` Larry McVoy
2023-01-28  2:49                 ` Tom Perrine
2023-01-26  6:32 ` Lars Brinkhoff
2023-01-26  9:45 ` emanuel stiebler via TUHS

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='3h5FEAegoTs6FrhHODiW-rBdB59dt_Rmr4G0PIw7flqaJLsmorgPsilm4f2aJkDud-qEljDjnCJcE1uY05Iw4HNQcyNG4W3wzVlLD0UZfLg=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    --cc=will.senn@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).