From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme mail "fmt"
Date: Mon, 5 Mar 2001 20:33:50 +0000 [thread overview]
Message-ID: <E14a1gA-000GGt-0U@anchor-post-30.mail.demon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
It helps you format very long lines like this one into a paragraph of more reasonable width. Just select the text and execute |fmt.
e.g.
IIt helps you format very long lines like this one into a paragraph of
more reasonable width. Just select the text and execute |fmt.
[-- Attachment #2: Type: message/rfc822, Size: 1293 bytes --]
From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] Acme mail "fmt"
Date: Mon, 5 Mar 2001 21:22:05 -0500
Message-ID: <20010305202603.C7BF219A0B@mail.cse.psu.edu>
I have been using Acme mail almost exclusively for all
my email. One thing I haven't used is the "fmt"
command in the taskbar of outbound mail... mainly
because I don't know what it does.
What does it do?
-Bill
next reply other threads:[~2001-03-05 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 20:33 nigel [this message]
2001-03-05 21:55 rog
2001-03-05 21:55 rog
2001-03-06 2:22 William Staniewicz
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=E14a1gA-000GGt-0U@anchor-post-30.mail.demon.net \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.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).