Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Tomasz Rola <rtomek@ceti.pl>
To: TUHS <tuhs@tuhs.org>
Cc: coff@tuhs.org
Subject: [COFF] Re: [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler)
Date: Sat, 4 Feb 2023 23:38:26 +0100	[thread overview]
Message-ID: <Y97eYk5rKUS68+Mc@tau1.ceti.pl> (raw)
In-Reply-To: <7wv8kj6yrx.fsf@junk.nocrew.org>

On Fri, Feb 03, 2023 at 06:36:34AM +0000, Lars Brinkhoff wrote:
> Dan Cross wrote:
> > So, the question becomes: what _is_ that forum, if such a thing
> > exists at all?
> 
> Some options:
> 
> - Cctalk email list.

(cc-ed to coff, of coffse...)

I use to hang out on IBM-MAIN mailing list, too. While they are,
mostly, dealing with modern mainframes and current problems, they also
occasionally mention old story or two. Actually, since mainframe is
such a living fossil thing, the whole talk sometimes feels as if it
was about something upgraded continuously from the 1960-ties. Most of
it is uncomprehensible to me (never had proper mainframe training, or
unproper one, and they deal with stuff in unique way, have their own
acronyms for things, there are some intro books but there is not
enough time*energy), but also a bit educating - a bit today, a bit
next week etc.

> - ClassicCMP Discord.
> - Retrocomputingforum.com.
> - Various Facebook groups.

Web stuff, requiring Javascript to work, ugh, ugh-oh. Mostly, it boils
down to the fact that one cannot easily curl the text from those other
places (AFAICT). So it is hard to awk this text into mbox format and
read it comfortably.

-- 
Regards,
Tomasz Rola

--
** A C programmer asked whether computer had Buddha's nature.      **
** As the answer, master did "rm -rif" on the programmer's home    **
** directory. And then the C programmer became enlightened...      **
**                                                                 **
** Tomasz Rola          mailto:tomasz_rola@bigfoot.com             **

      parent reply	other threads:[~2023-02-04 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230202190232.C79D118C073@mercury.lcs.mit.edu>
     [not found] ` <CAEoi9W7BfO+CZNjPQvZFE-YgjLf75GEumgoZZQot=RnGL2kF6w@mail.gmail.com>
     [not found]   ` <alpine.BSF.2.21.9999.2302031236570.82487@aneurin.horsfall.org>
     [not found]     ` <73d0b98b-ae3f-428d-1b2e-feada7fc98a1@case.edu>
     [not found]       ` <20230203141540.GS30555@mcvoy.com>
     [not found]         ` <CAEoi9W4x2wX3zTCgRKEoQ+qG=QiqR1piqeszh8_L6py0aAAm+g@mail.gmail.com>
     [not found]           ` <20230203165420.GB19745@mcvoy.com>
     [not found]             ` <alpine.DEB.2.21.2302031206500.1148@sd-119843.dedibox.fr>
     [not found]               ` <057be760-5f24-6274-c4b4-97ee8c439615@gmail.com>
2023-02-03 17:31                 ` [COFF] Re: move to COFF " Will Senn
     [not found]   ` <7wv8kj6yrx.fsf@junk.nocrew.org>
2023-02-04 22:38     ` Tomasz Rola [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=Y97eYk5rKUS68+Mc@tau1.ceti.pl \
    --to=rtomek@ceti.pl \
    --cc=coff@tuhs.org \
    --cc=tuhs@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).