From: Clem Cole <clemc@ccc.com>
To: Bakul Shah <bakul@bitblocks.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
Doug McIlroy <doug@cs.dartmouth.edu>
Subject: Re: [TUHS] V9 shell [was Re: Warner's Early Unix Presentation]
Date: Tue, 11 Feb 2020 12:12:10 -0500 [thread overview]
Message-ID: <CAC20D2O1P-U7yRHAX=DF1b9X+qjnWARY=U5LOa3WaY2i-w8GaQ@mail.gmail.com> (raw)
In-Reply-To: <9F0C266C-4311-4984-A2FA-85DAEF1207E1@bitblocks.com>
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
On Tue, Feb 11, 2020 at 11:03 AM Bakul Shah <bakul@bitblocks.com> 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 then
> 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 subset
> 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 “PL/C uses
> ....”. This was confusing to many students as they would do exactly what
> PL/C said it used and yet their program didn’t 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
[-- Attachment #2: Type: text/html, Size: 4813 bytes --]
next prev parent reply other threads:[~2020-02-11 17:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 3:32 Doug McIlroy
2020-02-11 3:53 ` Larry McVoy
2020-02-11 11:24 ` Ralph Corderoy
2020-02-11 15:51 ` Larry McVoy
2020-02-11 4:46 ` Warren Toomey
2020-02-11 5:12 ` Steve Nickolas
2020-02-11 6:33 ` Rob Pike
2020-02-11 9:40 ` arnold
2020-02-11 15:06 ` Chet Ramey
2020-02-11 14:36 ` Clem Cole
2020-02-11 15:29 ` Mike Markowski
2020-02-11 16:03 ` Bakul Shah
2020-02-11 17:12 ` Clem Cole [this message]
2020-02-11 17:17 ` Steve Nickolas
2020-02-11 17:21 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2020-02-07 22:25 [TUHS] Warner's Early Unix Presentation Warren Toomey
2020-02-07 23:57 ` Rob Pike
2020-02-08 15:15 ` Warner Losh
2020-02-08 21:50 ` Rob Pike
2020-02-10 15:05 ` Dan Cross
2020-02-10 15:46 ` [TUHS] V9 shell [was Re: Warner's Early Unix Presentation] arnold
2020-02-10 18:39 ` Rob Pike
2020-02-10 18:59 ` Bakul Shah
2020-02-10 19:58 ` Angelo Papenhoff
2020-02-10 20:11 ` Chet Ramey
2020-02-11 9:33 ` arnold
2020-02-11 9:47 ` Noel Hunt
2020-02-11 9:47 ` Rob Pike
2020-02-11 9:59 ` Rob Pike
2020-02-11 17:05 ` Steffen Nurpmeso
2020-02-11 17:18 ` Arthur Krewat
2020-02-11 18:22 ` Kurt H Maier
2020-02-16 21:34 ` Wesley Parish
2020-02-11 18:26 ` Jon Steinhart
2020-02-11 23:56 ` Steffen Nurpmeso
2020-02-12 0:12 ` Jon Steinhart
2020-02-12 5:54 ` Rob Pike
2020-02-11 17:36 ` Dan Cross
2020-02-11 18:35 ` Christopher Browne
2020-02-11 18:54 ` Rob Pike
2020-02-11 21:36 ` Harald Arnesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC20D2O1P-U7yRHAX=DF1b9X+qjnWARY=U5LOa3WaY2i-w8GaQ@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=bakul@bitblocks.com \
--cc=doug@cs.dartmouth.edu \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).