The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Michael Stiller via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] fmt(1): history, POSIX, -t, -c
Date: Fri, 29 May 2020 07:10:50 +0200	[thread overview]
Message-ID: <A6AE3168-5D7D-4044-922A-B667B5A544A2@me.com> (raw)
In-Reply-To: <20200529001853.GB27423@eureka.lemis.com>

It is also included in 2.9BSD, or was it backported:

FMT(1)              UNIX Programmer's Manual               FMT(1)

NAME
     fmt - simple text formatter

SYNOPSIS
     fmt [ name ...  ]

DESCRIPTION
     Fmt is a simple text formatter which reads the concatenation
     of input files (or standard input if none are given) and
     produces on standard output a version of its input with
     lines as close to 72 characters long as possible.  The spac-
     ing at the beginning of the input lines is preserved in the
     output, as are blank lines and interword spacing.

     Fmt is meant to format mail messages prior to sending, but
     may also be useful for other simple tasks.

SEE ALSO
     Mail(1), nroff(1), roff(1)

AUTHOR
     Kurt Shoens

BUGS
     The program was designed to be simple and fast - for more
     complex operations, the standard text processors are likely
     to be more appropriate.



> On 29. May 2020, at 02:18, Greg 'groggy' Lehey <grog@lemis.com> wrote:
> 
> On Thursday, 28 May 2020 at  9:30:09 -0400, Clem Cole wrote:
>> fmt was originally written by Kurt Shoens at UCB when he worked in Mail and
>> delivermail.
> 
> That agrees with the FreeBSD man page:
> 
> HISTORY
>     The fmt command appeared in 3BSD.
> 
>     The version described herein is a complete rewrite and appeared in
>     FreeBSD 4.4.
> 
> AUTHORS
>     Kurt Shoens
>     Liz Allen (added goal length concept)
>     Gareth McCaughan
> 
> Greg
> --
> Sent from my desktop computer.
> Finger grog@lemis.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed.  If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA


  reply	other threads:[~2020-05-29  5:11 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
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 [this message]
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=A6AE3168-5D7D-4044-922A-B667B5A544A2@me.com \
    --to=tuhs@minnie.tuhs.org \
    --cc=mstiller@me.com \
    --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).