From ED  Tue Aug 28 00:00:00 1979
From: ED (Ed Schwalenberg)
Date: 28 AUG 1979, 00:00
Subject: No subject
Message-ID: <mailman.957.1479821122.4695.its@nocrew.org>

Why is it that 
.CALL [SETZ ? '?_____ ? SETZM]
is an ILOPR, while
.CALL [SETZ ? 'FOOBAR ? SETZM]
fails to skip and returns an ILLEGAL SYSTEM CALL NAME error code?
I smell a crock.  Of course, I deserve no better, executing randomly
named system calls.  On the other hand, and related to this, the
.GETSYS uuo returns a list of NCALLS that includes ?_____ not once, but
200-<number of real system calls> times.  This should either be fixed or
documented.

From EAKatMIT-MC  Sun Aug 26 00:00:00 1979
From: EAKatMIT-MC (Earl A. Killian)
Date: 26 August 1979, 00:00
Subject: No subject
Message-ID: <mailman.958.1479821122.4695.its@nocrew.org>

When I exit my EMACS and type-ahead, most of the type-ahead isn't
echoed.  Perhaps DDT could check the %TXPIE bit and echo the character
itself if ITS didn't?  Or better, maybe ITS could do this?

Also, what about DDT option to use MP echoing instead of PI echoing?


From RWK  Sun Aug 26 00:00:00 1979
From: RWK (RWK)
Date: 26 Aug 1979, 00:00
Subject: SYS directories full
Message-ID: <[MIT-DMS].120744>

Date: 26 August 1979, 00:00
From: Robert W. Kerns <RWK at MIT-MC>
Subject:  SYS directories full
To: EBM at MIT-DMS, BUG-its at MIT-DMS

    Date: 25 Aug 1979 1536-EDT
    From: EBM at MIT-DMS (J. Eliot B. Moss)
    To:   (BUG its) at MIT-DMS
    Re:   BUG its

    :linkn ml:sys2;ts nr,r;ts nr38
    	fails when the link already exists, because the directory
    is full.  This is very annoying.  MC has the same problem.  I think
    that either the system call should be fixed, or some links in those
    two directoris should be gotten rid of so the directories are no longer
    full.
The real problem here is that the directory is full.  DDT has long supported,
and MC has long had a SYS3 directory.  I think that garbage links should be
GC'd, but that if a directory is available a SYS3 directory should be created
on the other machines.





From EBM  Sat Aug 25 00:00:00 1979
From: EBM (J. Eliot B. Moss)
Date: 25 Aug 1979, 00:00
Subject: BUG its
Message-ID: <[MIT-DMS].120688>

:linkn ml:sys2;ts nr,r;ts nr38
	fails when the link already exists, because the directory
is full.  This is very annoying.  MC has the same problem.  I think
that either the system call should be fixed, or some links in those
two directoris should be gotten rid of so the directories are no longer
full.



From CFFK  Fri Aug 24 00:00:00 1979
From: CFFK (Charles F. F. Karney)
Date: 24 AUG 1979, 00:00
Subject: Support of harware tabbing on printing terminal by Plot2
Message-ID: <mailman.959.1479821122.4695.its@nocrew.org>

Most of the shortcuts taken by PLOT2 when plotting on printing
terminals are in fact done by ITS.  (E.g. the suppression of
trailing spaces on a line, and the use of backspaces instead of
return+spaces.)  Support of hardware tabs by PLOT2 would similarly
be best done by ITS (e.g. via a new TCTYP).  If this is not done
then maybe CRTSTY could do the job.  (I believe CRTSTY may have
some minimum requirements which rules this out.)  Support of
tabs by PLOT2 itself would be the least desirable because (1)
nothing else (e.g. :print) would benefit, and (2) because Plot2
would have to implement ITS's other shortcuts at the same time.
(However, I don't rule out the support of tabbing by PLOT2.)
If ITS or CRTSTY also supported abs. curdsor positioning on daisy
wheel printers, you would be able to win using Plot2 by setting
PLOTMODE:DISPLAY$
An absolute requirement for the implementation of any of this
by any system is an EXACT specification of the  commands needed
to make the tabbing/cursor positioning work.


From KDO  Fri Aug 24 00:00:00 1979
From: KDO (Ken D Olum)
Date: 24 Aug 1979, 00:00
Subject: BUG its
Message-ID: <[MIT-DMS].120603>

The tty input buffer is too small.  If you come from a site with a line
editor (SAIL) and type a full line and CR the whole line will get sent
at once and overfill your buffer.  I had a good time typing this message.



From GJC at MIT-MC  Tue Aug 21 00:00:00 1979
From: GJC at MIT-MC (GJC at MIT-MC)
Date: 21 Aug 1979 00:00
Subject: No subject
Message-ID: <mailman.960.1479821122.4695.its@nocrew.org>

I was running a peek, and the system fair-share was said to be
113% at one point. This is mighty fine if it is true!


From EAK at MIT-MC  Mon Aug 20 00:00:00 1979
From: EAK at MIT-MC (EAK at MIT-MC)
Date: 20 Aug 1979 00:00
Subject: No subject
Message-ID: <mailman.961.1479821123.4695.its@nocrew.org>

Using the .LOSE argument of .CALL DISMIS is really terribly inconvenient
when the interrupt stack pointer isn't in an AC.  You have you put it
in one to address the return PC etc., but then you've clobbered an AC
which is hard to restore...


From SKH at MIT-MC  Sat Aug 11 00:00:00 1979
From: SKH at MIT-MC (SKH at MIT-MC)
Date: 11 Aug 1979 00:00
Subject: No subject
Message-ID: <mailman.962.1479821123.4695.its@nocrew.org>

A suggestion:
Change the more handling in WHOJ, PEEK, FINGER etc. to (:PRINT)
to that of DDT'S implicit more (The one that vanishes if on
a display). Its annoying to see the --more-- thing stick
around. The vanishing more is 700% better.


From KMP at MIT-MC  Sat Aug 11 00:00:00 1979
From: KMP at MIT-MC (KMP at MIT-MC)
Date: 11 Aug 1979 00:00
Subject: No subject
Message-ID: <mailman.963.1479821123.4695.its@nocrew.org>

The system with the ARCHIV handler doing a .CALL FINISH for 13 hours
finally crashed, due to apparently related lossage.  It's dumped in
MC:CRASH;QFLDF1 H/50
The immediate cause of the crash was indexing the channel tables with
H being 1 larger than the largest channel table index!


From PAE at MIT-MC  Sat Aug 11 00:00:00 1979
From: PAE at MIT-MC (PAE at MIT-MC)
Date: 11 Aug 1979 00:00
Subject: No subject
Message-ID: <mailman.964.1479821123.4695.its@nocrew.org>

Look at MC:CHANNA;_DRGN_ TIMES
(and MC:CHANNA;_DRGN_ TIMES, and MC:CHANNA;_DRGN_ TIMES,
and MC:CHANNA;_DRGN_ TIMES, and MC:CHANNA;_DRGN_ TIMES, and...

From ___021 at MIT-MC  Sat Aug 11 00:00:00 1979
From: ___021 at MIT-MC (___021 at MIT-MC)
Date: 11 Aug 1979 00:00
Subject: .CALL FINISH won't
Message-ID: <mailman.965.1479821123.4695.its@nocrew.org>

There's an archive device handler here, hung in a .CALL FINISH on its disk
output channel.  The channel is in REAI mode according to PEEK's C mode.
It's definately an output channel, so I guess PEEK must display append-mode
channel's oddly.  Claims its 100% read.

The .CALL FINISH is at OPNOUT+16

The job's flush instruction is SKIPE QSBFS+5
The PUSHJ P,UFLS is at QOCL2+1/ SKIPE QSBFS(A)
A/ 1,,5
QSBFS+5/	1
QSCRW+5/	0	;Read
QSRAC+5/	%QAEFR+%QAACC+%QALBK+%QAMWO,,0
QSMPRC+5/	0		;No bytes left in buffer


I don't know what else might be relevant.  I leave the job KMP JOB.06
still hanging for your inspection.  KMP HACTRN is still hanging on the job
to finish.


From KMP at MIT-MC  Sat Aug 11 00:00:00 1979
From: KMP at MIT-MC (KMP at MIT-MC)
Date: 11 Aug 1979 00:00
Subject: No subject
Message-ID: <mailman.966.1479821123.4695.its@nocrew.org>

If I have a file name
FOO .EXP99
and write out a new file called
FOO > 
it seems to write to
FOO .EX100

This would be ok if it weren't for the fact that if I then
compile FOO >, I end up compiling FOO .EXP99 ... can this be
fixed? Like maybe to open the > file, you could find all contenders
(files with max number of digits, ending in a digit), strip all trailing
digits, readlist the digits and compare them?

-kmp


From PAE  Thu Aug  9 00:00:00 1979
From: PAE (Philip A. Earnhardt)
Date: 9 AUG 1979, 00:00
Subject: Getting thrown to DDT by :SEND
Message-ID: <mailman.967.1479821123.4695.its@nocrew.org>


    RWK at MIT-MC 08/09/79 05:41:16 Re: Getting thrown to DDT by :SEND
Subject: Getting thrown to DDT by :SEND
    If you type a ^G while a SEND is printing, DDT has control of the terminal
    and you'll end up in DDT.  Was this perhaps the problem?
no, I was just typing characters...no control chars.

From RWK at MIT-MC  Thu Aug  9 00:00:00 1979
From: RWK at MIT-MC (RWK at MIT-MC)
Date: 09 Aug 1979 00:00
Subject: Getting thrown to DDT by :SEND
Message-ID: <mailman.968.1479821123.4695.its@nocrew.org>

If you type a ^G while a SEND is printing, DDT has control of the terminal
and you'll end up in DDT.  Was this perhaps the problem?


From RMS  Wed Aug  8 00:00:00 1979
From: RMS (Richard M. Stallman)
Date: 8 AUG 1979, 00:00
Subject: No subject
Message-ID: <mailman.969.1479821123.4695.its@nocrew.org>


Date: 08 Aug 1979 00:00
From: ___076 at MIT-MC
    It would seem that NO SUCH DEVICE is not really what's wanted.
    Note that if you are WRITING a file, that you want normally to
    go on the secondary pack, it also says "NO SUCH DEVICE".  In
    actual fact, there IS such a device, sitting broken and unavailable.

I agree.  "No such device" says "what you want makes no sense", which
is not true in this case.

From PAE at MIT-MC  Wed Aug  8 00:00:00 1979
From: PAE at MIT-MC (PAE at MIT-MC)
Date: 08 Aug 1979 00:00
Subject: No subject
Message-ID: <mailman.970.1479821123.4695.its@nocrew.org>

I received a message while replying to mail (using emacs rmail),
kept typing at the time, and somehow got kicked out of emacs back to
ddt.  I didn't think there was anything that would quit an emacs
like that.

From ___076 at MIT-MC  Wed Aug  8 00:00:00 1979
From: ___076 at MIT-MC (___076 at MIT-MC)
Date: 08 Aug 1979 00:00
Subject: No subject
Message-ID: <mailman.971.1479821123.4695.its@nocrew.org>

It would seem that NO SUCH DEVICE is not really what's wanted.
Note that if you are WRITING a file, that you want normally to
go on the secondary pack, it also says "NO SUCH DEVICE".  In
actual fact, there IS such a device, sitting broken and unavailable.


From MOON at MIT-MC  Wed Aug  8 00:00:00 1979
From: MOON at MIT-MC (MOON at MIT-MC)
Date: 08 Aug 1979 00:00
Subject: SECOND:
Message-ID: <mailman.972.1479821123.4695.its@nocrew.org>

It does give you pack not mounted.  You were probably typing SECOND:
and indeed there is no such device if the pack isn't mounted.  But you don't
need to, and usually don't, give the device name if you're just printing a file.

From ED  Wed Aug  8 00:00:00 1979
From: ED (Ed Schwalenberg)
Date: 8 AUG 1979, 00:00
Subject: SECOND:
Message-ID: <mailman.973.1479821123.4695.its@nocrew.org>

Printing a file on SECOND: on AI these days results in NO SUCH DEVICE,
when one would expect a PACK NOT MOUNTED.  Is this a bug or a feature?

From BH  Sun Aug  5 00:00:00 1979
From: BH (Brian Harvey)
Date: 5 AUG 1979, 00:00
Subject: No subject
Message-ID: <mailman.974.1479821123.4695.its@nocrew.org>

How come top-/ is infinity, but shift-/ is N ?  (Of course
I mean the blue slash key, not the grey one.)  I realize that
infinity is 016 octal and so is N, but the difference seems
weird to me, e.g. when typing in EMACS and getting to the next
line when one wanted an infinity.

From MRC  Fri Aug  3 00:00:00 1979
From: MRC (Mark Crispin)
Date: 3 AUG 1979, 00:00
Subject: No subject
Message-ID: <mailman.975.1479821123.4695.its@nocrew.org>

Padding on Telerays seems to lose in EMACS with i/d mode.  Are you using
Pentti's algorithm yet?  Telerays require lots of padding!