switch back to xtightvncviewer for shared connection

This is needed because xtigervncviewer now fails to forward the input
from the other side when launched in this way.

There is the same buggy behavior in xtightvncviewer when connecting
in the 'reverse' style -- which has been removed from this code base
because of that regression.

The system as it is now uses both tiger and tight viewers.  It uses
tiger locally and tight when it projects the display remotely.  But
only tight has proven reliable in operation.  Tight should be available
locally.

Tiger is preferred because it supports use of a socket file and because
it supports many other features and has a superior UI. But these
features are not worth bugs and unreliability.

0 files changed, 0 insertions, 0 deletions