From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id fa24fa25 for ; Tue, 11 Feb 2020 17:12:57 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 7CF3B9BCFE; Wed, 12 Feb 2020 03:12:56 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 987519BCE8; Wed, 12 Feb 2020 03:12:39 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="FlXPBJ5Q"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id CBDA49BCE8; Wed, 12 Feb 2020 03:12:37 +1000 (AEST) Received: from mail-qt1-f171.google.com (mail-qt1-f171.google.com [209.85.160.171]) by minnie.tuhs.org (Postfix) with ESMTPS id 3FE049BCE3 for ; Wed, 12 Feb 2020 03:12:37 +1000 (AEST) Received: by mail-qt1-f171.google.com with SMTP id r5so7152309qtt.9 for ; Tue, 11 Feb 2020 09:12:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Kw53SCw7uRx/xjMk7GQp9f/heGqsB7A1g3zhgXpFPgI=; b=FlXPBJ5Q6R4x3Yirc8GZdbBFwNzXljWTc6WGIYqbegjYRZWz8Se+3oR3Sj6legN0JS ID7HZlHBL8Ou55oMh/39oHwTqYvHrSxhoJszG4cMvUF7gEwuDj5Cz7bGKcg60gQ6Dceu Ojn/sro0g5tt6f4PFXwOvZh4puJMcJkPd0T/A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Kw53SCw7uRx/xjMk7GQp9f/heGqsB7A1g3zhgXpFPgI=; b=olG4LLoXOI5pV59vD02fntUwev6EcK++yh0Nc+xaoa5m44tS+3a6cS5BlvtYMoaWBi 4voo81SHmtavqmdjIGMVAiwPgJtr76J63PTn+NSynU6WJ6e5qxZfVg7AnvEVzXECzbeW mYd/Nb6ye+SVdHVluoGd+QHHGsLS0F/LfLQI3AWnwEYL8OLs5IlBSxK+FB90cLOeti1+ MDknLQpt8exy4TwW1wlYT/oa+P0xxDJeW+he2xk16IWNHt1c5Fo5HGFOvcwds0K+fD86 o04GtOki45p3/bLR3F6rglpF9PEEE25x1eKmVKCUf5xfbbS0axv1g8c47n/PVdloDJnZ nKRQ== X-Gm-Message-State: APjAAAW3kkfSpxMdKeGcOU3jCWFtKmVcTfwG4Jt21EDij/UoQKqFw2Pq 0oHa9NekuUtg9I3f35e9f8HL7XfsxHDnMYvF02Vj2g== X-Google-Smtp-Source: APXvYqxZSjKggl7fql55N5xDrU9JVYw+6VqeCf4ZyVdmX8DEerFcI9EEBqeR9zM9NEbESWVN7Ko0PpNz+spE2i3Zz3s= X-Received: by 2002:aed:3eee:: with SMTP id o43mr3418040qtf.33.1581441156237; Tue, 11 Feb 2020 09:12:36 -0800 (PST) MIME-Version: 1.0 References: <9F0C266C-4311-4984-A2FA-85DAEF1207E1@bitblocks.com> In-Reply-To: <9F0C266C-4311-4984-A2FA-85DAEF1207E1@bitblocks.com> From: Clem Cole Date: Tue, 11 Feb 2020 12:12:10 -0500 Message-ID: To: Bakul Shah Content-Type: multipart/alternative; boundary="00000000000059e238059e4ff651" Subject: Re: [TUHS] V9 shell [was Re: Warner's Early Unix Presentation] X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society , Doug McIlroy Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000059e238059e4ff651 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Feb 11, 2020 at 11:03 AM Bakul Shah wrote: > I call it automiscorrect. > I've been known to same something similar. Usually with a #$%^& before it. > First, it is very easy to mistype on these touch based interfaces and the= n > they miscorrect using too large a vocabulary. > +1, amen brother Shah, amen, > > At USC, back when I was a student, they started us off with PL/C, a subse= t > of PL/I. The PL/C compiler tried its level best to make sense of the > student programs it was given, with error messages such as =E2=80=9CPL/C = uses > ....=E2=80=9D. This was confusing to many students as they would do exact= ly what > PL/C said it used and yet their program didn=E2=80=99t work. > FWIW: I referenced both PL/C and IBM PL/1 compiler in my quora answer. In an interactive world, offering a note like Grammerly's underline, seems reasonable to me - because it forces me to accept it. The automatic doing it for me, is what I dislike - as you said, on touch interfaces it's twice as bad. I remember having a conversation with Doug Cooper when we all were teaching the intro to CS course and I we were getting students turning in 'auto-corrected' code for assignments and wondering why the TAs were not amused. I had thought that having the compiler tell you what was in error and then maybe offering a suggestion, might make sense, but there needed to be some action on the student's part to accept >>and<< repair to code before the compiler would produce something that 'ran.' Anyway, I still think "*Damn Warren's Infernal Machine*" was always well named. Clem --00000000000059e238059e4ff651 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On T= ue, Feb 11, 2020 at 11:03 AM Bakul Shah <bakul@bitblocks.com> wrote:
I call it automiscorrect.
<= /div>
I've been known to s= ame something similar.=C2=A0 Usually with a #$%^& before it.
=C2=A0
Fir= st, it is very easy to mistype on these touch based interfaces and then the= y miscorrect using too large a vocabulary.
<= div>+1, amen brother Shah, amen,<= /div>

At USC, back when I was a student, they started us of= f with PL/C, a subset of PL/I. The PL/C compiler tried its level best to ma= ke sense of the student programs it was given, with error messages such as = =E2=80=9CPL/C uses ....=E2=80=9D. This was confusing to many students as th= ey would do exactly what PL/C said it used and yet their program didn=E2=80= =99t work.
= FWIW: I referenced both PL/C and IBM PL/1 compiler in my quora answer.=C2= =A0
In an interactive w= orld, offering a note like Grammerly's underline, seems reasonable to m= e - because it forces me to accept it.=C2=A0 =C2=A0The automatic doing it f= or me, is what I dislike - as you said, on touch interfaces it's twice= =C2=A0as bad.

I remember having a conversation with Doug Cooper when w= e all were teaching the intro to CS course and I we were getting students= =C2=A0turning in 'auto-corrected' code for assignments and wonderin= g why the TAs were not amused.=C2=A0 I had thought that having the compiler= tell you what was in error and then maybe offering a suggestion, might mak= e sense, but there needed to be some action on the student's part to ac= cept >>and<< repair to code before the compiler would produce s= omething that 'ran.'

Anyway, I st= ill think=C2=A0"Damn Warren's Infernal Machine" was= always well named.

Clem

--00000000000059e238059e4ff651--