...size=-1>ISCUSS

Copyright © 1992 Student Information Processing Board of the Massachusetts Institute of Technology

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...Athena.

Throughout this document, DISCUSS client names, such as discuss, are printed in italics. DISCUSS meetings also are displayed in italic print. Commands that the user should enter or keys that should be pressed are quoted in boldface. Output from the clients is shown in typewriter print.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...meeting.

The .meetings implementation allows for any number of names for a meeting. The names are kept in a comma-separated list in the .meetings file, which you can edit with emacs if you wish to change meetings' names.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...Quotes_Misquotes_and_Out_of_Con...

The ellipsis simply means the meeting title was too long to fit on a single line and has been truncated.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...libels......

A reference to the Central_America meeting, which archives all changed .plan files each night.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...``send''.

The reasons behind having three different names are mostly historical; Multics Forum had the concept of an ``unprocessed'' transaction, one for which the text has been entered but has not been sent to a meeting. The ``talk'' command would start processing (input) of a new transaction, which was not necessarily saved. The ``enter'' or ``send'' command would save the unprocessed transaction in the meeting. In DISCUSS, unprocessed transactions have not been implemented.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...``1#1e''

This is taken from the Berkeley Mail command.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...far.

DISCUSS will use the environment variable EDITOR, or /bin/ed if EDITOR is not set. Athena's default startup files set the EDITOR environment variable to emacs. You may also specify another editor for DISCUSS by setting the environment variable DISCUSS_EDITOR.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...list:

The behavior of the spacebar can be modified so that it automagically ``does the right thing'': pressing spacebar can enter the next changed meeting, page through to the end of a transaction, and continue to the next transaction; pressing delete would have the opposite effect. To get this behavior, place ``(setq discuss-DWIM t)'' in your .emacs file. ``DWIM'' stands for ``Do What I Mean''. Alternately, you can press ``Escape Escape spacebar'' (twice, not the Meta key), then at the ``Eval:'' prompt enter ``(setq discuss-DWIM t)'' to have the same effect. To return to the default behavior, remove the line from your .emacs file or press ``Escape Escape spacebar'' and enter ``(setq discuss-DWIM nil)''. This feature is recommended mostly for people who feel comfortable with the more arcane features of emacs.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...system.

xdsc currently uses an edsc co-process which does the actual communication with DISCUSS. By default, xdsc runs /usr/athena/etc/edsc. If you want to use a different edsc, set the environment variable EDSC to its full pathname.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...file.

The greyed out 38#38 button is a feature that has not yet been implemented.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...pathname.

To set an environment variable, place a line such as ``setenv MEETINGS /mit/username/meetings_file'' in your .environment file; if you do not have a .environment file, you can create one with emacs or another editor.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...data.

Since the meetings file is deleted during each update, however, you should not set it up to refer to a symbolic link, because the link will simply be removed.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.