From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Origin of "bug" (was: Grace Hopper)
Date: Sun, 10 Dec 2017 14:20:09 +1100 [thread overview]
Message-ID: <20171210032009.GJ78437@eureka.lemis.com> (raw)
In-Reply-To: <C1637218-7D46-4404-86BC-F6ACD51AA5B3@bitblocks.com>
On Saturday, 9 December 2017 at 16:30:57 -0800, Bakul Shah wrote:
> May be it is derived from ???bugbear???? As per Merriam-Webster:
> 1) an imaginary goblin or specter used to excite fear
> 2) a source of dread, a continuing source of irritation: a problem.
> First known use 1552.
OED suggests that both our "bug" and "bugbear" are derived from "bug"
(An insect or other arthropod). It agrees with the 1552 date:
1552 R. King Funerall Serm. sig. F.iiiiv Momishe mopers whiche can do
none other thyng else, but mope vppon ther bookes, to make vs
afraied of shadowes and buggeberes.
Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171210/1353652c/attachment.sig>
prev parent reply other threads:[~2017-12-10 3:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 23:26 [TUHS] Grace Hopper Dave Horsfall
2017-12-09 0:05 ` Larry McVoy
2017-12-09 0:39 ` Mike Markowski
2017-12-09 3:21 ` Dave Horsfall
2017-12-09 10:04 ` Jason Stevens
2017-12-09 17:31 ` Paul Winalski
2017-12-09 20:03 ` Lyndon Nerenberg
2017-12-09 18:03 ` arnold
2017-12-09 23:17 ` Dave Horsfall
2017-12-09 23:41 ` [TUHS] Origin of "bug" (was: Grace Hopper) Greg 'groggy' Lehey
2017-12-10 0:30 ` Bakul Shah
2017-12-10 3:20 ` Greg 'groggy' Lehey [this message]
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=20171210032009.GJ78437@eureka.lemis.com \
--to=grog@lemis.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).