Re: Buried shovel in ctwm

On Tue, Oct 10, 2017 at 01:17:29AM -0400 I heard the voice of
Steve Litt, and lo! it spake thus:
> 
> I suggest that ctwm be modified so that if --cfgchk is the only
> argument, it outputs the errors to stdout whether or not X is
> running, and that it not error out because X isn't running.

It's probably not impossible to make at least a fair approximation at,
but it wouldn't be easy.  Connecting to X happens very early in the
startup, since it needs to know how many screens to initialize and
information about them to setup the screen bits, including a number of
things in that process that are needed to run the config files.
Actually, cfgchk is slightly broken in the multi-screen case anyway,
since it would only run the first screen's config.


-- 
Matthew Fuller     (MF4839)   |  [email protected]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.