From: dove at mit-dspg at mit-mc It is disgusting that "eval `test -s vt52`" works and "eval `tset -s vt100`" fails. Apparently, the file matching chars in the vt100 termcap seq (e.g. '[') cause setenv to come back with a too many arguments message. Why can't there be a way to jam the results of an execution into a variable without further interpretation?