The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] Another "craft" discussion topic - mindless tool proliferation
Date: Tue, 19 Sep 2017 22:29:29 -0600	[thread overview]
Message-ID: <1167a64e-97be-b5c6-4025-e7a0c5c7533c@tnetconsulting.net> (raw)
In-Reply-To: <CA75D988-DD10-415A-AF0A-EC027C01D13C@orthanc.ca>

On 09/19/2017 07:09 PM, Lyndon Nerenberg wrote:
> My main gripe about that is that I can't read the web when the router I'm trying to install won't work, keeping me from the needed web documentation ...

*SO* *MUCH* *THIS*!!!

> *Please* write your documentation in a way that allows you to generate (useful, readable!) PDF documents that I can download for offline viewing.  Believe it or not, I don't haul along a 300 mile cat-5 cable when I go sailing.  I still like to write code on the boat.  So much for Go :-P

I have a personal bias against PDF and prefer single (or few) page text 
/ HTML files that I can easily consume offline.

> And $GOD help everyone in the Caribbean trying to bootstrap their infrastructure right now.  How is your https://... documentation going to help them out?

*LOL*

#truth



-- 
Grant. . . .
unix || die


  parent reply	other threads:[~2017-09-20  4:29 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 17:01 Jon Steinhart
2017-09-19 17:05 ` Steve Nickolas
2017-09-19 20:31   ` Pete Turnbull
2017-09-19 20:37     ` Warner Losh
2017-09-19 23:35 ` Theodore Ts'o
2017-09-20  0:47   ` Lyndon Nerenberg
2017-09-20  1:02     ` Larry McVoy
2017-09-20  1:09       ` Lyndon Nerenberg
2017-09-20  1:13         ` Larry McVoy
2017-09-20  1:22           ` Larry McVoy
2017-09-20  2:01             ` Larry McVoy
2017-09-20  2:34               ` Bakul Shah
2017-09-20  2:47                 ` Larry McVoy
2017-09-20  6:18                   ` Bakul Shah
2017-09-20  4:35                 ` Grant Taylor
2017-09-20  5:54                   ` Ian Zimmerman
2017-09-24 23:03                 ` Ralph Corderoy
2017-09-24 23:35                   ` Bakul Shah
2017-09-20 16:49             ` Steffen Nurpmeso
2017-09-20  4:29         ` Grant Taylor [this message]
2017-09-20  6:43         ` Peter Jeremy
2017-09-20  8:25           ` Bakul Shah
2017-09-20  9:12             ` Steve Nickolas
2017-09-20  9:34               ` Bakul Shah
2017-09-20 16:48         ` Steffen Nurpmeso
2017-09-20  2:07       ` Theodore Ts'o
2017-09-24 22:58         ` Ralph Corderoy
2017-09-20  4:26       ` Grant Taylor
2017-09-20 16:45     ` Steffen Nurpmeso
2017-09-21 17:33     ` Tony Finch
2017-09-21 18:39       ` Steffen Nurpmeso
2017-09-22  0:02         ` Greg 'groggy' Lehey
2017-09-22  0:30           ` Lyndon Nerenberg
2017-09-22  0:38             ` Larry McVoy
2017-09-22  0:39               ` Lyndon Nerenberg
2017-09-22  0:50                 ` Larry McVoy
2017-09-22  1:01                   ` Lyndon Nerenberg
2017-09-22  1:08                     ` Larry McVoy
2017-09-22 20:09                       ` [TUHS] remaking make (Re: " Bakul Shah
2017-09-22  2:25                   ` [TUHS] " Warner Losh
2017-09-22  3:26               ` Greg 'groggy' Lehey
2017-09-22  4:09                 ` ron minnich
2017-09-22  2:20             ` Warner Losh
2017-09-22  0:36           ` Larry McVoy
2017-09-22  0:40             ` Lyndon Nerenberg
2017-09-22  1:53             ` Michael Parson
2017-09-22  3:25       ` Grant Taylor
2017-09-20  6:20   ` Lars Brinkhoff
2017-09-20 16:39   ` Steffen Nurpmeso
2017-09-24 22:54   ` Ralph Corderoy
2017-09-25  0:16     ` Steve Johnson
2017-09-25 11:30       ` Ralph Corderoy
2017-09-20 18:15 ` Clem Cole
2017-09-20 18:35   ` Jon Steinhart

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=1167a64e-97be-b5c6-4025-e7a0c5c7533c@tnetconsulting.net \
    --to=gtaylor@tnetconsulting.net \
    /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).