csh and tset

Article View: net.bugs.2bsd

Article #91

#91

From: utzoodecvaxucbvaxARPAVAXUNKNOWNd...
Date: Tue, 14 Sep 1982 17:32

6 lines
673 bytes

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?

Technical Details

Message-ID: <bnews.ucbvax.8495>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

From: utzoo!decvax!ucbvax!ARPAVAX:UNKNOWN:dove@mit-dspg@mit-mc
Newsgroups: net.bugs.2bsd
Title: csh and tset
Article-I.D.: ucbvax.8495
Posted: Tue Sep 14 17:32:32 1982
Received: Wed Sep 22 07:32:50 1982
Subject: csh and tset
Date: Tue, 14 Sep 1982 17:32:32 +0000
Message-ID: <bnews.ucbvax.8495>