From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
Cc: Alan Braslau <alan.braslau@icloud.com>
Subject: Re: [NTG-context] new units
Date: Sun, 7 May 2023 09:58:32 -0600 [thread overview]
Message-ID: <20230507095832.65e714ba@boo.my.domain> (raw)
In-Reply-To: <A135014F-09BF-4370-AD2A-5F8A3E3ACC1B@scorecrow.com>
On Sun, 7 May 2023 13:00:18 +0100
Bruce Horrocks via ntg-context <ntg-context@ntg.nl> wrote:
> Will there be new units to represent the amount of alcohol that has
> to be imbibed in order to (a) create the joke and (b) understand it?
>
> I'm not sure which of these needs to be the larger. Perhaps that
> could be the subject of the next research?
The moral of the story is that we all missed something by not attending
BachoTeX - as is the case every year. One should note Hans' reference
to the gala dinner, which is better characterized by an excess of
dishes of food than by an excess of alcohol.
We have an opportunity to make up for this missed occasion this year by
attending the annual ConTeXt meeting. Of course, these two meetings are
complementary and ideally one should aim at attending *both*.
As to the Dutch left and right thumbs, the French word is also "pouce"
for the length of an inchworm. My question is, what is the appropriate
unit for inching forward or inching along? Would this be one inch per
fortnight?
Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-05-07 16:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 8:01 Hans Hagen via ntg-context
2023-05-06 16:45 ` Alan Braslau via ntg-context
2023-05-06 19:40 ` Hans Hagen via ntg-context
2023-05-06 21:53 ` Arthur Rosendahl via ntg-context
2023-05-06 23:29 ` Hans Hagen via ntg-context
2023-05-07 9:10 ` Henning Hraban Ramm via ntg-context
2023-05-07 9:29 ` Mojca Miklavec via ntg-context
2023-05-07 10:04 ` Hans Hagen via ntg-context
2023-05-07 10:06 ` Hans Hagen via ntg-context
2023-05-07 9:45 ` Hans Hagen via ntg-context
2023-05-07 10:09 ` Henning Hraban Ramm via ntg-context
2023-05-07 10:29 ` Hans Hagen via ntg-context
2023-05-07 15:56 ` Henning Hraban Ramm via ntg-context
2023-05-07 14:56 ` Hans Hagen via ntg-context
2023-05-07 12:00 ` Bruce Horrocks via ntg-context
2023-05-07 13:07 ` Hans Hagen via ntg-context
2023-05-07 15:58 ` Alan Braslau via ntg-context [this message]
2023-05-07 0:10 skyhorse--- via ntg-context
2023-05-07 2:43 ` Michael Urban via ntg-context
2023-05-07 6:09 ` Mikael Sundqvist via ntg-context
2023-05-07 8:15 ` Hans Hagen via ntg-context
2023-05-07 2:51 ` Alan Braslau via ntg-context
2023-05-07 8:22 ` Hans Hagen via ntg-context
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=20230507095832.65e714ba@boo.my.domain \
--to=ntg-context@ntg.nl \
--cc=alan.braslau@icloud.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).