From BARRYG at MIT-MC  Fri Feb 29 00:00:00 1980
From: BARRYG at MIT-MC (BARRYG at MIT-MC)
Date: 29 Feb 1980 00:00
Subject: filenames for automatic deletion
Message-ID: <mailman.877.1479821121.4695.its@nocrew.org>

I use EMACS in autosave mode and I'm getting tired of cleaning up after
it.  I'm stuck with a filename1 of BARRYG (by convention), so is there
a filename2 that will cause the file to be automatically reaped?
If there is, it will simplify life as I want to keep the number of
files I leave around to a minimum.
	/barry gold

From EJS at MIT-MC  Tue Feb 26 00:00:00 1980
From: EJS at MIT-MC (EJS at MIT-MC)
Date: 26 Feb 1980 00:00
Subject: No subject
Message-ID: <mailman.882.1479821121.4695.its@nocrew.org>

:call echoin
and 
:call ttyesc

do not provide documentation on the respective system calls.  Could
somebody please update the doc file?  Thanks.

From MOON at MIT-MC  Sun Feb 24 00:00:00 1980
From: MOON at MIT-MC (MOON at MIT-MC)
Date: 24 Feb 1980 00:00
Subject: No subject
Message-ID: <mailman.883.1479821121.4695.its@nocrew.org>

The garbling of bits was a central problem which I believe I have just fixed.
If the screen is still blank, try turning the monitor off and back on (if you
can't find the plug, pull the fuse in the back out and put it back in.)

From ECC at MIT-MC  Sun Feb 24 00:00:00 1980
From: ECC at MIT-MC (ECC at MIT-MC)
Date: 24 Feb 1980 00:00
Subject: No subject
Message-ID: <mailman.884.1479821121.4695.its@nocrew.org>

The TV in 902 was garbling a lot of bits on the screen, in particular
making the finger display shown when it is logged out almost totally
unreadable.  I logged in to see if :FINGER would produce a more readable
listing, which it sorta did.  However when I then logged out, it gave
a little "bizzap!" sound (not very noisy) and the screen went blank,
with nothing that I could type bringing it back.

From JLK at MIT-MC  Mon Feb 11 00:00:00 1980
From: JLK at MIT-MC (JLK at MIT-MC)
Date: 11 Feb 1980 00:00
Subject: No subject
Message-ID: <mailman.885.1479821121.4695.its@nocrew.org>

I think it is a rather major loss that :@ defaults to MIDAS or somesuch, given the
relatively few users of @ who make MIDAS listings.  If one were to base the defaults
on numbers, it should default to LISP code.  But I don't suggest that.
:@ <filename>
with no other JCL should obviously be the same as :@ <filename>/L[RANDOM]/D[DOVER]/#
these days.


From bak  Sun Feb 10 00:00:00 1980
From: bak (William A. Kornfeld)
Date: 10 FEB 1980, 00:00
Subject: No subject
Message-ID: <mailman.886.1479821121.4695.its@nocrew.org>

This is a qubbling point, but if someone is REALLY bored he may
wish to fix it.

If an archive is on an unmounted disk (i.e. SECOND) and you do
an AR2^F, it gives an incorrect error message.  It thinks AR2
is a non-existent directory.  The correct error message should
be PACK NOT MOUNTED.

From MOON at MIT-MC  Sat Feb  9 00:00:00 1980
From: MOON at MIT-MC (MOON at MIT-MC)
Date: 09 Feb 1980 00:00
Subject: %TDICP suggestion (EAK)
Message-ID: <mailman.887.1479821121.4695.its@nocrew.org>

Hmm, clever.  Sounds like it would work.

From EAKatMIT-MC  Sat Feb  9 00:00:00 1980
From: EAKatMIT-MC (Earl A. Killian)
Date: 9 February 1980, 00:00
Subject: %TDICP suggestion
Message-ID: <mailman.888.1479821121.4695.its@nocrew.org>

How about changing the definition of %TDICP n from being "insert
n blanks in the current line" to being "insert next n characters
in the current line"?  I suspect that no programs would have to
change (i.e. TECO wouldn't).  The reason for the chnage would be
to allow insertion to happen more reasonably on some terminals
(in particular those with an insert character mode), without
making it any less efficient for terminals like TVs or the
Teleray.  CRTSTY would make use of the new constraint on what can
follow a %TDICP, and maybe ITS could too.


From EAKatMIT-MC  Sat Feb  9 00:00:00 1980
From: EAKatMIT-MC (Earl A. Killian)
Date: 9 February 1980, 00:00
Subject: No subject
Message-ID: <mailman.889.1479821121.4695.its@nocrew.org>

How about changing the definition of %TDICP n from being "insert
n blanks in the current line" to being "insert next n characters
in the current line"?  I suspect that no programs would have to
change (i.e. TECO wouldn't).  The reason for the chnage would be
to allow insertion to happen more reasonably on some terminals
(in particular those with an insert character mode), without
making it any less efficient for terminals like TVs or the
Teleray.  CRTSTY would make use of the new constraint on what can
follow a %TDICP, and maybe ITS could too.


From GRAND  Sat Feb  9 00:00:00 1980
From: GRAND (Mark D. Grand)
Date: 9 FEB 1980, 00:00
Subject: No subject
Message-ID: <mailman.890.1479821121.4695.its@nocrew.org>

	How does one go about recovering a file that (I presume)
was reaped?

From CFFK at MIT-MC  Thu Feb  7 00:00:00 1980
From: CFFK at MIT-MC (CFFK at MIT-MC)
Date: 07 Feb 1980 00:00
Subject: No subject
Message-ID: <mailman.891.1479821121.4695.its@nocrew.org>

I was logged into TTY 7, and all of a sudden nearly everything I typed
gave IBO.