From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] OT: Need help from a *BSD guru
Date: Mon, 22 Jan 2018 12:07:43 -0700 [thread overview]
Message-ID: <201801221907.w0MJ7hMb013984@freefriends.org> (raw)
In-Reply-To: <20180122180327.njqe3z4f7bwfytln@matica.foolinux.mooo.com>
Ian Zimmerman <itz at very.loosely.org> wrote:
> On 2018-01-22 07:36, arnold at skeeve.com wrote:
>
> > Looks like I solved my problem on my own; thanks to everyone who
> > replied privately. I will send a short note detailing the issue
> > a little later.
>
> Probably an unnecessary reminder, but could you post about it (the
> problem and the solution) to the Usenet newsgroup comp.lang.awk as well?
> Thanks.
It's totally a C issue; it merely came up in the context of gawk.
And I unsubscribed from comp.lang.awk a year or so ago. My blood
pressure has been considerably lower since doing so. :-)
Thanks,
Arnold
next prev parent reply other threads:[~2018-01-22 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 8:10 arnold
2018-01-22 14:36 ` arnold
2018-01-22 18:03 ` Ian Zimmerman
2018-01-22 19:07 ` arnold [this message]
2018-01-22 19:36 ` arnold
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=201801221907.w0MJ7hMb013984@freefriends.org \
--to=arnold@skeeve.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).