From: Mike Markowski <mike.ab3ap@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] V9 shell [was Re: Warner's Early Unix Presentation]
Date: Tue, 11 Feb 2020 10:29:53 -0500 [thread overview]
Message-ID: <CANq1pf=EY9ObUPdkY5pFGCgeQ1xZd3XWSVWH1KWRWR2JKRqgWw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PE6Jh5dwc=aVvdu_Ft3A-=OWV=Cgxq6zrFG104=7m8_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
My favorite example is a business trip my wife took. Her surname is Hsi
which was "corrected" to His at the site she visited. Upon arrival it took
her several *hours* to work out with the security folks that Ms Hsi was not
impersonating Ms His. (That says as much about the security group as it
does about autocorrect, I suppose.)
Mike Markowski
On Tue, Feb 11, 2020 at 9: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
>
>
[-- Attachment #2: Type: text/html, Size: 2857 bytes --]
next prev parent reply other threads:[~2020-02-11 15:30 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 [this message]
2020-02-11 16:03 ` Bakul Shah
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='CANq1pf=EY9ObUPdkY5pFGCgeQ1xZd3XWSVWH1KWRWR2JKRqgWw@mail.gmail.com' \
--to=mike.ab3ap@gmail.com \
--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).