From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] [groff] [UTROFF] references, summary, index
Date: Wed, 06 Dec 2017 19:45:17 -0500 [thread overview]
Message-ID: <201712070045.vB70jHKP004480@coolidge.cs.Dartmouth.EDU> (raw)
Ralph,
> > On unjustified text, fmt (which uses an algorithm purported to be like
> > Knuth-Plass)
>
> I wonder if that accounts for modern, coreutils 8.28-1, fmt's weirdness
> that I've seen for a while but never got around to investigating?
>
> $ yes x | fmt | awk '{print length, $0}' | uniq -c | sed 5q
You threw it something of a curve ball--an infinite paragraph.
At some point I suppose it chokes, and tries its best to make
a semiparagraph of equal-length lines. (Since the real paragraph
is not yet complete, it would be wrong to make the last line of
the semiparagraph short.)
Equilibrating apparently led to the split between 69- and 71-letter lines.
Whether the alternation of 11 of one and 16 of the other is an infinite
pattern or a subpattern is not clear. It could be part of a continued-fraction
approximation, related to the staircse appearance of a bitmap "straight line".
Doug
next reply other threads:[~2017-12-07 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 0:45 Doug McIlroy [this message]
2017-12-07 1:17 ` George Michaelson
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=201712070045.vB70jHKP004480@coolidge.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
/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).