The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] B-news source code
Date: Fri, 10 Mar 2017 23:20:24 -0500	[thread overview]
Message-ID: <CAEoi9W45m2coeGoWCf6o7TXPAjb+rnLPgZtoOOEEXHJaTkQ0Rw@mail.gmail.com> (raw)
In-Reply-To: <eb351ba3-7031-aede-7036-034c14523a3f@mhorton.net>

On Fri, Mar 10, 2017 at 9:21 PM, Mary Ann Horton <mah at mhorton.net> wrote:

> So you'd think, but it appears it came first in netnews. Mail/mailx has ~m
> which indents with a tab, not a ">".  Most likely in summer of 1983,
> between 2.10 and 2.10.1.


Wasn't it possible to customize this in .mailrc? Something like, `set
indentprefix="> "`? I'm afraid that doesn't answer the question, but I'm
not sure mailx/Mail as the vector is unreasonable. Is it possible someone
coming from the ARPAnet mailing list world found Unix and brought the
practice in? I'm curious what the standard was on ITS or TOPS-20, for
instance.

        - Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170310/bd999f76/attachment.html>


  reply	other threads:[~2017-03-11  4:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  9:49 [TUHS] C-news is built Warren Toomey
2017-03-10 10:29 ` [TUHS] pathalias and mail maps Warren Toomey
2017-03-10 10:49   ` Jacob Goense
2017-03-10 15:45   ` Erik E. Fair
2017-03-10 17:52 ` [TUHS] C-news is built John Floren
2017-03-10 21:14   ` Nick Downing
2017-03-10 21:30     ` Henry Bent
2017-03-10 21:51       ` Nick Downing
2017-03-11  4:57     ` Jason Stevens
2017-03-10 21:34   ` Warren Toomey
2017-03-10 22:48     ` John Floren
2017-03-11  0:05 ` [TUHS] B-news source code Mary Ann Horton
2017-03-11  0:15   ` Larry McVoy
2017-03-11  2:21     ` Mary Ann Horton
2017-03-11  4:20       ` Dan Cross [this message]
2017-03-11  3:01   ` Warren Toomey
2017-03-11  3:13 Doug McIlroy
2017-03-11 13:13 ` Steffen Nurpmeso

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=CAEoi9W45m2coeGoWCf6o7TXPAjb+rnLPgZtoOOEEXHJaTkQ0Rw@mail.gmail.com \
    --to=crossd@gmail.com \
    /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).