The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: GNU eqn clarifications and reforms
Date: Thu, 15 Jun 2023 22:20:55 -0500	[thread overview]
Message-ID: <20230616032055.ixdg6ubvfxgjhsmb@illithid> (raw)
In-Reply-To: <CAKH6PiWccCuoiWpV7dbt-pMHKtZXEvRa1VgJU5JixpsY0-VXLQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

[looping groff list back in]

At 2023-06-15T22:18:08-0400, Douglas McIlroy wrote:
> I am not convinced that using special characters rather than in-line
> eqn is a good thing. It means learning a whole new vocabulary.  Quick,
> what's the special character for Greek psi?

\[*q] !

But I may suffer from an excessive familiarity with this material.

(Checking myself, I got it right!  Part of my mnemonic is that there are
24 letters to map from our Latin alphabet to Greek, drop 'j' and 'v' as
"Late Latin" variants of 'i' and 'u'[1], and then most of the rest map
intuitively with a handful of exceptions that have to be memorized, psi
being one of them.)

> I have found that, for a sequence of displayed equations as in an
> algebraic derivation, a pile often looks more coherent than a sequence
> of EQ-EN pairs. The pile can even contain interleaved comments, as in
> Hoare-style proofs.

Yes.  I suspect there is a widely held misconception that eqn
distinguishes displayed equations from inline ones.  It doesn't--a macro
package might, but even then, nothing internal to the equation's
typography is different.  I guess this is a hangover from TeX?  You need
one rule: use "smallover" instead of "over" if you're trying to pack a
fraction into running text.

Regards,
Branden

[1] Which isn't _quite_ correct but works for this purpose.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-06-16  3:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  2:18 Douglas McIlroy
2023-06-16  3:20 ` G. Branden Robinson [this message]
     [not found]   ` <37ea7f2b-e8f7-3cfe-a27d-ece47c5dc0f7@esi.com.au>
2023-06-16  5:07     ` G. Branden Robinson
2023-06-16  7:43       ` [TUHS] Re: end-S/long-S (was: Re: GNU eqn clarifications and reforms) markus schnalke
2023-06-16  9:39         ` Wesley Parish
2023-06-16 16:18         ` Paul Winalski
2023-06-16 17:46           ` John Cowan
2023-06-16 17:51             ` Steve Nickolas
2023-06-16 18:19               ` Angelo Papenhoff
     [not found]           ` <1da83cf3-7fac-b5fd-dec-e4b4313d3a@esi.com.au>
2023-06-16 19:38             ` [TUHS] Re: GNU eqn clarifications and reforms G. Branden Robinson

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=20230616032055.ixdg6ubvfxgjhsmb@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --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).