From: Valdis.Kletnieks@vt.edu
To: Jonathan Lundell <linux@lundell-bros.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] 'the the' in mails ...
Date: Tue, 19 Aug 2003 12:19:05 -0400 [thread overview]
Message-ID: <200308191619.h7JGJ5Vq000449@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 19 Aug 2003 09:10:12 PDT." <p06001a95bb67fbc38747@[207.213.214.37]>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Tue, 19 Aug 2003 09:10:12 PDT, Jonathan Lundell <linux@lundell-bros.com> said:
> At 2:32pm +0100 8/19/03, Alan Cox wrote:
> >On Maw, 2003-08-19 at 02:24, Herbert Pötzl wrote:
> >> I know this is absolutely off topic, but
> >> about 30 threads, in the last two months,
> >> on lkml contain this strange construct,
> >> and I'm worried that I miss something very
> >> important ...
> >
> >Its a very common typo, especially at the end of a line.
>
> ...where for some reason it tends to be invisible.
Darn, my reply to this to Dave didn't go to the list, soo...
The field of "cognitive perception" deals with issues like this..
http://www.geocities.com/woras.geo/TASK.htm
http://ibs.derby.ac.uk/~kpat/Israel_cognitive/introduction.shtml
Basically, the average human mind is *very* good at discarding/altering
input that "doesn't make sense", and preconceived notions will over-ride what
you actually see. This is why good proofreaders are so hard to find - most
of us will simply ignore that second "the" because it doesn't parse.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-08-19 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 1:24 [OT] 'the the' in mails Herbert Pötzl
2003-08-19 1:50 ` Dave Jones
2003-08-19 2:29 ` Kurt Wall
2003-08-19 2:50 ` Randy.Dunlap
2003-08-19 13:32 ` Alan Cox
2003-08-19 16:10 ` Jonathan Lundell
2003-08-19 16:19 ` Valdis.Kletnieks [this message]
2003-08-20 1:59 ` Herbert Pötzl
2003-08-19 17:11 John Bradford
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=200308191619.h7JGJ5Vq000449@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@lundell-bros.com \
/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).