The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Clem Cole <clemc@ccc.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 08:03:06 -0800	[thread overview]
Message-ID: <9F0C266C-4311-4984-A2FA-85DAEF1207E1@bitblocks.com> (raw)
In-Reply-To: <CAC20D2PE6Jh5dwc=aVvdu_Ft3A-=OWV=Cgxq6zrFG104=7m8_Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2653 bytes --]

I call it automiscorrect. First, it is very easy to mistype on these touch based interfaces and then they miscorrect using too large a vocabulary.

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.

> On Feb 11, 2020, at 6:38 AM, Clem Cole <clemc@ccc.com> wrote:
> 
> 
> Amen.  As a dyslexic (which most often shows when I'm typing as you folks have experienced) autocorrect generally is a PITA.   FWIW: Grammerly works well for me.  It underlines in dotted red and lets me look at what it thinks it should be - where I can accept it or not.   
> 
> Doug -- I agree DWIM was just silly.... UCB's Pascal system (pix) tried it also and let's just say it failed as I explain in a comment /answer on quora (https://www.quora.com/When-you-are-programming-and-commit-a-minor-error-such-as-forgetting-a-semicolon-the-compiler-throws-an-error-and-makes-you-fix-it-for-yourself-Why-doesn-t-it-just-fix-it-by-itself-and-notify-you-of-the-fix-instead). 
> 
> Clem
> 
> 
> 
>> On Mon, Feb 10, 2020 at 10:33 PM Doug McIlroy <doug@cs.dartmouth.edu> wrote:
>> > What i like is the autocorrect feature in v8:
>> >
>> > $ cd /usr/blot
>> > /usr/blit
>> > $ pwd
>> > /usr/blit
>> 
>> Here I am, editor of the v8 manual and unaware of the feature.
>> We now know that silent correction is a terrible idea.
>> 
>> Postel's principle: "be conservative in what you do, be liberal
>> in what you accept from others" was doctrine in early HTML
>> specs, and led to disastrous disagreement among browsers'
>> interpretation of web pages. Sadly, the "principle" lives on 
>> despite its having been expunged from the HTML spec.
>> 
>> Today's "langsec" movement grew out of bitter experience
>> with malicious inputs exploiting "liberal" interpretation of
>> nonconforming data.
>> 
>> Today's NYT has an article about fake knockoffs of George Orwell
>> for sale on Amazon.  It cites an edition of "Animal Farm"
>> apparently pirated by lowgrade OCR autocorrected and never
>> proofread. One of the many gaffes is that every instance of
>> "iv" beame ChapterIV, as in "prChapterIVacy".
>> 
>> I didn't like some Lisp systems' DWIM (do what I mean) when I
>> first heard about the feature, and I like it even less 40-some
>> years on. I would probably have remonstrated with Rob had I
>> realized the shell was doing it.
>> 
>> Doug

[-- Attachment #2: Type: text/html, Size: 4755 bytes --]

  parent reply	other threads:[~2020-02-11 16:03 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 [this message]
2020-02-11 17:12     ` Clem Cole
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=9F0C266C-4311-4984-A2FA-85DAEF1207E1@bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=clemc@ccc.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).