From: Clem Cole <clemc@ccc.com>
To: John Cowan <cowan@ccil.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>,
Grant Taylor <gtaylor@tnetconsulting.net>
Subject: Re: [TUHS] Groff on Windows (for PDF output)?
Date: Sat, 25 Jul 2020 10:55:44 -0400 [thread overview]
Message-ID: <CAC20D2MyAAcPdgaNm7DF_FSZgR-VSjw4j=So1nEFzB+xFSBcWQ@mail.gmail.com> (raw)
In-Reply-To: <CAD2gp_RBNq6vfQDbm9Ky8MR7B4QsoYWZ-Nov5b9PgYgvV1v7_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
On Sat, Jul 25, 2020 at 10:45 AM John Cowan <cowan@ccil.org> wrote:
>
>
> BTW, when you say "Win32S" you mean "Win32". Win32S was a long-obsolete
> package to let 32-bit Windows apps run on 16-bit Windows if they didn't try
> to do too much.
>
Can't speak for today. At one point the S stood for Standard/Stable. That
used to be a Culter-ism IIRC -- it was what was guaranteed to ISVs to be
there. If you used anything else, Microsoft could (and did) pull the rug
out from under you.
They added a bunch of new APIs and new stuff from 64 bits to et al. When
Interix was done, all that they could guarantee was Cutler's interface.
I agree. However, I have spent much of my career on corporate Windows
> boxen, which are often locked down to prevent you from installing
> things, including WSL. Because Cygwin bypasses the regular Windows install
> system, it flies under the radar.
>
WSL should not have that problem these days for the exact reasons you
mentioned, as you were correct that SFU/SUA did tend to be something that
IT depts did not understand like (it was free but it was separate
install). But WSL is just one of the standard options in Windows10 ever
system can have it. You just have to enable it in the control panel and it
will automatically do everything in a manner that should not be an issue to
IT folks. Although it does require >>local<< admin privileges on the
machines to enable.; IIRC.
[-- Attachment #2: Type: text/html, Size: 2725 bytes --]
prev parent reply other threads:[~2020-07-25 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 18:33 Doug McIlroy
2020-07-23 20:51 ` Grant Taylor via TUHS
2020-07-23 22:35 ` John Cowan
2020-07-24 0:13 ` Clem Cole
2020-07-25 14:45 ` John Cowan
2020-07-25 14:55 ` Clem Cole [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='CAC20D2MyAAcPdgaNm7DF_FSZgR-VSjw4j=So1nEFzB+xFSBcWQ@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=cowan@ccil.org \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@minnie.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).