Re: CTWM and XDM

--pgp-sign-Multipart_Tue_Aug_19_14:03:57_2025-1
Content-Type: text/plain; charset=US-ASCII

At Tue, 19 Aug 2025 11:26:58 +0100, BC HABS <[email protected]> wrote:
Subject: Re: CTWM and XDM
>
>
> If it is possible to build *without* workspaces, then I haven found
> it, or to not have that section in the .ctwmrc file and not have
> issues, but having just one workspace defined is no hardship and it
> seems to have fixed the issues being experienced

It is impossible to compile ctwm without workspace support.

However not defining any workspaces should just work.

On a quick walk-through of the code the only thing I noticed was that
the flag variable field used to indicate whether any workspaces are
defined or not is not explicitly initialized in the InitScreenInfo().
However since it's a plain normal boolean flag and the struct is
allocated with calloc(), the default should be "false" anyway.

I just tried running my latest build of ctwm with "-f /dev/null", which
will of course avoid defining any WorkSpaces, and it works just fine.  I
can also send it a SIGHUP and it restarts just fine.

BTW one can test ctwm in an Xnest display with relative ease provided
one allows for controlling which window manager is run from one's
~/.xinitrc through, e.g., an environment variable.  For example I do
this with the following commands:

    (
	cd;
	WM="/work/woods/f-ctwm/build-NetBSD-x86_64/work/woods/f-ctwm/ctwm -v -f /dev/null" \
	XNESTDISPLAY=$display \
	xinit -- $X11PATH/bin/Xnest;
	cd -
    )

It's helpful to have your ~/.xinitrc detect when it is run from a
terminal and redirect all output to a file for analysis too, though
without doing so you'll see any errors wherever you run xinit from.

--
					Greg A. Woods <[email protected]>

Kelowna, BC     +1 250 762-7675           RoboHack <[email protected]>
Planix, Inc. <[email protected]>     Avoncote Farms <[email protected]>

--pgp-sign-Multipart_Tue_Aug_19_14:03:57_2025-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Description: OpenPGP Digital Signature

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCaKTmwAAKCRBmfXG3eL/0
fzIdAKCgQ+AdXnx5Ea+0g4lMwtNHP8jM9gCePBha7FaJcEjq4qxtq8ECLLD/xTs=
=jfzG
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Tue_Aug_19_14:03:57_2025-1--