The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: johnl@johnlabovitz.com (John Labovitz)
Subject: [TUHS] SunOS 4 documentation
Date: Thu, 13 Apr 2017 09:28:12 -0400	[thread overview]
Message-ID: <7A44F035-601A-40AD-ACC3-E69AEE7A2F6E@johnlabovitz.com> (raw)
In-Reply-To: <08eb864b-784b-28e5-63b3-420cfbc5f684@telegraphics.com.au>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

On 2017-04-12 7:31 PM, Larry McVoy wrote:

> I love me
> some troff, even to this day.  I really really really wish that someone
> had done framemaker, word, whatever, that was the GUI interface that had
> troff under the covers.  Why?  Because you can version control the source


A bit off topic, but…

I’ve been researching modern macOS writing apps over the last few days. I was very surprised to find that almost all of them use Markdown as their primary format — not just for import/export, but as a storage format as well as a user interface. (Examples: Ulysses, Scrivener, ByWord.) It seems that Markdown and text files has become the gold standard in this particular class of app, even for folks who’d never use the command line. Granted, not all those apps expose the documents as normal, version-controllable files, but still, it’s pretty wild to see text formats be accepted again, at least in a narrow class of documentation-related tools.

—John


      parent reply	other threads:[~2017-04-13 13:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 21:54 Cory Smelosky
2017-04-12 22:55 ` Cory Smelosky
2017-04-12 23:31   ` Larry McVoy
2017-04-13  2:13     ` Toby Thain
2017-04-13  2:16       ` Steve Nickolas
2017-04-13  2:25         ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 14:25           ` Nemo
2017-04-13 15:41           ` Andreas Kusalananda Kähäri
2017-04-13 16:35           ` Toby Thain
2017-04-13  2:20       ` [TUHS] " Larry McVoy
2017-04-13 13:41         ` Steffen Nurpmeso
2017-04-13 15:40           ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 23:22             ` Steffen Nurpmeso
2017-04-14  0:40               ` Greg 'groggy' Lehey
2017-04-14  1:59                 ` Nemo
2017-04-14  3:00                   ` Toby Thain
2017-04-14  2:59                 ` Toby Thain
2017-04-14 13:38                 ` Steffen Nurpmeso
2017-04-14 13:56                   ` Michael Kerpan
2017-04-14 16:55                     ` Steffen Nurpmeso
2017-04-14 22:24                     ` Toby Thain
     [not found]                       ` <CAHfSdrVAnPn3hwFR0ie0o-yuqGX0hu+LWweNZngpoY4=efTSaA@mail.gmail.com>
2017-04-15 14:23                         ` Michael Kerpan
2017-04-15 15:09                           ` Toby Thain
2017-04-15 16:07                           ` [TUHS] TeX/troff/typesetting markups - " Mutiny 
2017-04-15 21:48                             ` Dave Horsfall
2017-04-15 22:12                               ` ron minnich
2017-04-16  0:02                                 ` Dave Horsfall
2017-04-15 15:27                       ` [TUHS] TeX/troff/typesetting markups - " Clem Cole
2017-04-15 17:05                         ` Toby Thain
2017-04-15 17:10                         ` Toby Thain
2017-04-18  4:49                         ` Greg 'groggy' Lehey
2017-04-14 13:07             ` Wolfgang Helbig
2017-04-14 20:56               ` Clem Cole
2017-04-16 13:42               ` Tim Bradshaw
2017-04-13 14:14         ` [TUHS] " Nemo
2017-04-13 16:34           ` Steve Simon
2017-04-13 23:14             ` Steffen Nurpmeso
2017-04-14  8:30               ` Steve Simon
2017-04-14 13:21                 ` Steffen Nurpmeso
2017-04-13 13:28       ` John Labovitz [this message]

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=7A44F035-601A-40AD-ACC3-E69AEE7A2F6E@johnlabovitz.com \
    --to=johnl@johnlabovitz.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).