Hi all, I've just discovered a buried shovel (catch 22, positive feedback paradox, etc) in ctwm. Specifically, the following command fails if X isn't running:
ctwm --cfgchk The preceding command is a must when you have a damaged ctwm, perhaps damaged to the extent that it can't run a terminal. In other words, if you could run ctwm --cfgchk, you could repair ctwm well enough to run, and if you could repair ctwm well enough to run, you could run ctwm --cfgchk. 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. Thanks, SteveT Steve Litt October 2017 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21
