From: alec.muffett@gmail.com (Alec Muffett)
Subject: [TUHS] Anyone know what a LANTERN is
Date: Sun, 30 Jul 2017 12:17:52 +0100 [thread overview]
Message-ID: <CAFWeb9LFZ8t7Gzu1AS-joJ8MZsbbTb-vz2mKRunA1_mFESvizA@mail.gmail.com> (raw)
In-Reply-To: <201707301114.v6UBEEmc029284@coolidge.cs.Dartmouth.EDU>
Dumb question: is there any chance that just as BEL goes <beep>, perhaps
LAMP illuminated a red warning light or similar?
On 30 Jul 2017 12:14 pm, "Doug McIlroy" <doug at cs.dartmouth.edu> wrote:
> I have no actual information about the lantern character, but
> a tapered "storm lantern" would be far down my list of guesses.
> The tapered chmney would much more likely be called a "lamp",
> for it's a standard shape for the oil (kerosene) lamps
> that everyone had before electricity.
>
> My top guess would be a carriage lantern with a Japanese
> garden ornament as a distant second. The carriage lantern
> would be an unfilled circle superimposed on a vertical
> rectangle, filled or unfilled. The rectangle might be
> simplified to two (interrupted) vertical sides.
>
> An alternate form of lantern would be a side view of
> a carriage (or picture-projection) lantern, schematized
> as a box, with a flaring projection to the right--an
> icon for shining light on a subject, also interpretable
> as a movie camera.
>
> A Japanese lantern would be tripartite: cap, body, and
> feet.
>
> Do any of these possibilities ring a bell?
>
> Doug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170730/c9c92ec2/attachment.html>
next prev parent reply other threads:[~2017-07-30 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 11:14 Doug McIlroy
2017-07-30 11:17 ` Alec Muffett [this message]
2017-07-31 16:50 ` Paul Winalski
2017-07-31 17:52 ` ron minnich
2017-07-31 20:01 ` Warner Losh
2017-07-31 20:04 ` Warner Losh
2017-07-31 21:25 ` Earl Baugh
2017-07-31 23:46 ` Kevin Schoedel
2017-07-30 17:43 ` Lyndon Nerenberg
2017-07-30 22:33 Norman Wilson
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=CAFWeb9LFZ8t7Gzu1AS-joJ8MZsbbTb-vz2mKRunA1_mFESvizA@mail.gmail.com \
--to=alec.muffett@gmail.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).