* Collect TALK files into lispusers/talk/ renamed with hyphen convention. Also pull over TALKGAP files that were previous obsolete, and remove them from obsolete/lispusers * Replace TALK.TEDIT--file got smashed * TALK.TEDIT now comments the current situation
171 lines
50 KiB
Plaintext
171 lines
50 KiB
Plaintext
en·vÅos TALK
|
||
2
|
||
|
||
4
|
||
|
||
1
|
||
|
||
TALK
|
||
1
|
||
|
||
4
|
||
|
||
By: Christopher Lane (Lane@Sumex-Aim.Stanford.Edu)
|
||
Uses: Various editor and network protocol modules.
|
||
[NOTE (Ron Kaplan): TALKS does not currently work in modern Medley.
|
||
The TALK-relevant files were spread out in lispusers, and some of the relevant files had been moved to obsolete. I have created a talk> subdirectory of lispusers and put all the relevant files there (including moving them from lispusers), all now renamed as lispusers/talk/TALK-* according to the hyphen filenaming convention.
|
||
TALK doesn't appear to workfor reasons known and unknown. But this pulls them into a single place for future work. Maybe this whole subdirectory should be moved to obsolete, a separate question.
|
||
This is related to issues #7 and #2095, and maybe some others concerning the organization of lispusers/.
|
||
Here are at least some of the problems:
|
||
1. Some of the functions include local record declarations of the form (* DECLARATIONS: (RECORD...)). This is sanctioned in the release notes, but does not appear to be understood by the compiler.
|
||
2. The TEDIT interface advises a set of internal \TEDIT functions that may or may not behave as they did originally.
|
||
3. At least some of the protocol files to do not load.
|
||
It may be possible to bring this up to snuff, but it will take some work. In the meantime, all of the relevant files have been gathered into the lispusers/talk/ directory, with names that conform to the hyphen convention for components of a larger package.]
|
||
|
||
TALK allows users to hold conversations between machines across the Ethernet. TALK uses various services (TTY, TEdit and Sketch) and network protocols (NS and IP).
|
||
3 |