I have been using HOSTNAME since day one, because I shared my .ctwmrc across many hosts, and I never wanted to worry about names which might be the same at different sites. (esp. for sites which used generic hostnames, such as "mail", "www", etc., as the real host's name)
These days though I don't wander far from home with my X11 setup (unless
it's the one on my laptop). I don't know what CLIENTHOST would resolve
to on that system though. Probably not what I use, which is the system
hostname with ".local" appended to it.
This is the only line where I do currently use CLIENTHOST (obviously I
had to because there was no equivalent FQDN variant of SERVERHOST):
ifelse([SERVERHOST], [CLIENTHOST], [define(USE_X11SERVER, [yes])], [])
(other than lines where it CLIENTHOST appears in a string for use in a
menu entry, that is; and that was for convenience, but could cause
confusion if there were duplicates)
One thing I have often wondered about (well, only so often as I've had
to edit my .ctwmrc to add something for a new system, etc.) is whether
or not it might make sense to somehow expose some or all of the
environment variables to the M4 processing.... This should entirely
eliminate any need for the likes of CLIENTHOST, SERVERHOST, HOSTNAME,
etc.
--
Greg A. Woods
Planix, Inc.
<[email protected]> +1 250 762-7675 http://www.planix.com/
pgpS0rqORfTS_.pgp
Description: PGP signature
