From: Rob Pike <robpike@gmail.com>
To: markus schnalke <meillo@marmaro.de>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] fmt(1): history, POSIX, -t, -c
Date: Thu, 28 May 2020 23:08:39 +1000 [thread overview]
Message-ID: <CAKzdPgzyqu5ofQ033tAxj9Db8awMVPvnvpkJFMFMV5Ko7akwsg@mail.gmail.com> (raw)
In-Reply-To: <1jeHk5-5LM-00@marmaro.de>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
I looked in my manuals. Fmt(1) first appears in Research 9th edition. I
have vague memories that it was written by Tom Duff, but a) I could
misremember and b) I also have vague memories it was not original. If both
memories are accurate, it's just a simple command written in two different
places, one being a distorted echo of another. Much like the make td wrote
at UofT after hearing about Stu's.
Nothing nefarious.
-rob
On Thu, May 28, 2020 at 10:41 PM markus schnalke <meillo@marmaro.de> wrote:
> Hoi,
>
> personally I use fmt(1) a lot for email formatting and such.
> Typically I only use the `-w' parameter. Now someone asked me about
> `-t' and `-c' of *GNU* fmt(1). I wasn't able to find good documentation
> on them. The manpage only tells that they have to do with different
> indentation for the first or first two lines. But what are the use
> cases? How would source text for these parameters look like?
>
> A look into the description and rationale sections of POSIX, which
> often provides helpful information, was not possible because fmt(1)
> is not part of POSIX (only fold(1) is). Why's that? Is it because
> fmt(1) differs so much between Unix implementations? On BSD `-c'
> centers text and `-t' sets tab widths. Plan 9 has none of these
> options. But still, `-w' could have been standardized. Or was the
> line filling algorithm different as well? How does fold(1) fit into
> the picture?
>
> Maybe you can answer some of these questions or give hints on where
> I could find answers myself.
>
>
> meillo
>
[-- Attachment #2: Type: text/html, Size: 1991 bytes --]
next prev parent reply other threads:[~2020-05-28 13:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 12:34 markus schnalke
2020-05-28 13:08 ` Rob Pike [this message]
2020-05-28 13:30 ` Clem Cole
2020-05-28 13:47 ` Clem Cole
2020-05-28 16:08 ` Mary Ann Horton
2020-05-28 18:00 ` Clem Cole
2020-05-28 18:35 ` Richard Salz
2020-05-28 18:51 ` Clem Cole
2020-05-29 0:18 ` Greg 'groggy' Lehey
2020-05-29 5:10 ` Michael Stiller via TUHS
2020-05-29 5:19 ` Greg 'groggy' Lehey
2020-05-29 13:39 ` Clem Cole
2020-05-29 15:43 ` Warner Losh
2020-05-29 16:12 ` Clem Cole
2020-05-29 17:14 ` Mary Ann Horton
2020-05-28 13:46 ` Clem Cole
2020-05-31 13:01 ` [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c) markus schnalke
2020-05-31 14:53 ` Clem Cole
2020-05-31 16:25 ` Richard Salz
2020-05-31 16:50 ` Larry McVoy
2020-05-31 17:09 ` Ralph Corderoy
2020-05-31 17:25 ` Jon Steinhart
2020-05-31 17:28 ` [TUHS] mh/hm, mmh Mary Ann Horton
2020-05-31 18:56 ` Eric Allman
2020-05-31 19:49 ` Clem Cole
2020-05-31 21:31 ` Mary Ann Horton
2020-06-01 6:32 ` Caipenghui
2020-06-01 7:14 ` markus schnalke
2020-05-31 12:35 ` [TUHS] fmt(1): history, POSIX, -t, -c markus schnalke
2020-05-29 1:25 Doug McIlroy
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=CAKzdPgzyqu5ofQ033tAxj9Db8awMVPvnvpkJFMFMV5Ko7akwsg@mail.gmail.com \
--to=robpike@gmail.com \
--cc=meillo@marmaro.de \
--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).