🚀 go-pugleaf

[I don't much like to do Stuart support via netnews, but I also
 want to make certain this point is publicly cleared up.  In the
 future, if anyone has problems with Stuart, _please_ contact me
 directly and I'll clear them up directly -scott]

In article <1992Sep15.184414.108626@zeus.calpoly.edu>
	Alex Raftis <alex@cosmos.acs.calpoly.edu> writes:
>Daniel M. Rosenberg writes
>> On some NeXT's, you type "talk," and it says,
>>
>> "Go away. You don't exist."
>
>I've occaissionally had this problem and the only thing I can find
>is that talk doesn't like to work with Stewart, and I'm not sure
>why, since I can execute the call that has problems in other code
>under Stewart. I blame Stuart, because I can start up X and an
>xterm and talk will work fine. This problem may hold true for
>Terminal, since it's based on Stuart.

Just FYI, this is not due to a bug in Stuart, but the result of
incorrect installation.  Terminal comes pre-installed, so installation
is not a problem (though these types of problems can occur if one
gets too aggressive with trying to improve security on their system).
The problems described do not occur when Stuart is installed
correctly.  Stuart2.4 includes an online manual which describes
how to install things correctly.  It also has a section (Trouble
Shooting/talk Isn't Working) which details some of the problems
that are likely to occur due to an incorrect installation, including
the exact problems that have been described on this newsgroup.
For more information, I refer you to that section of the online
manual.

>I think the has the effect of confusing talk, which doesn't manage
>to associate you talk request with a name and a tty. I've tried
>playing with the code a little, but like I said, the calls work
>individually from other code fragments, so until I have more time,
>I remain stumped.

As noted above, _please_ contact me directly with these problems.
There is no reason for you to spend time attempting to solve problems
that shouldn't be there in the first place.  I'll try to fix them
or try make a good argument for why they aren't really problems
(and thus shouldn't be fixed).  As a last resort I'll hide behind
the excuse that I don't currently have the time to fix them correctly.
In the case of the problems mentioned in this groups, I'd have sent
back the five-line explanation of where to look for the fix, and
much confusion and annoyance would have been avoided.

Thanks,
--
scott hess <shess@ssesco.com>       <A port is a port, of course, of course>
12901 Upton Avenue South, #326  Burnsville, MN 55337 (612) 895-1208 Anytime!
<You praise me with faint damns, the dragon growled.  -Castle Roogna, Xanth>