Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc,comp.unix.shell
Subject: Re: [OT] Punch card times (was Re: Taking Speedy too seriously)
Date: 3 Nov 2026 02:17:15 GMT
Lines: 47
Message-ID: <nksuhbF2rmsU10@mid.individual.net>
References: <18dee4b6cab427fa$865$2574533$802601b3@news.usenetexpress.com> <RH-dnS_Dp6SSsEH3nZ2dnZfqnPednZ2d@giganews.com> <11bhv61$1bjd2$2@dont-email.me> <11bi77v$20c1p$1@news.xmission.com> <11binqk$1bjd2$3@dont-email.me> <pLicnUOiRttbS0P3nZ2dnZfqn_GdnZ2d@giganews.com> <11bmnvg$36mvk$1@dont-email.me> <pLicnX-iRtvwnkL3nZ2dnZfqn_GdnZ2d@giganews.com> <11bp7nd$139t9$2@dont-email.me> <1omdnboFafC6TX33nZ2dnZfqn_GdnZ2d@giganews.com> <11brekh$139ta$4@dont-email.me> <zyidnfr4e4AiInz3nZ2dnZfqnPidnZ2d@giganews.com> <76sES.99248$xwD5.81928@fx47.iad> <nkfho2F6rc9U5@mid.individual.net> <11bvs57$3gfju$3@dont-email.me> <VMSdnS91V7mP13n3nZ2dnZfqnPadnZ2d@giganews.com> <fa6FS.16031$WY1.1843@fx06.iad> <nkluscFas32U2@mid.individual.net> <11c5356$n1fl$1@dont-email.me> <nkmruhFftpsU6@mid.individual.net> <11c5lhs$nak9$3@dont-email.me> <nkontqFp0edU3@mid.individual.net> <11c7ql0$nak9$5@dont-email.me> <nkshcgF3cbcU4@mid.individual.net> <11cb66d$2e740$5@dont-email.me> <nkstc7F3cbcU9@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net BdowG0L/QvuAlIbiL1aZWA0jHTitFpeUhyPRyN6+t8thx2PCri
Cancel-Lock: sha1:pALseykGkiFPGIe2U3jPvCAu6Cc= sha256:QoA0Himfc1CfiINxMqHjnP6mhLmvi8CacRj0aonQP+E=
User-Agent: Pan/0.165 (Kostiantynivka)
Xref: csiph.com comp.os.linux.misc:94976 comp.unix.shell:27147

On Tue, 3 Nov 2026 02:57:27 +0100, Carlos E. R. wrote:
> Heck, Borland in the 90's had an IDE with integrated help that could
> find the proper help paragraph by clicking on a keyword in your text.
> Seems too difficult to replicate. Not even Lazarus has it.

I happen to have a html document open in VS Code at the moment. If the 
mouse hovers over 'charset' it pops up a dialog:

"This attribute declares the page's character encoding. It must contain a 
standard IANA MIME name for character encodings. Although the standard 
doesn't request a specific encoding, it suggests:

Authors are encouraged to use UTF-8.
Authors should not use ASCII-incompatible encodings to avoid security 
risk: browsers not supporting them may interpret harmful content as HTML. 
This happens with the JIS_C6226-1983, JIS_X0212-1990, HZ-GB-2312, JOHAB, 
the ISO-2022 family and the EBCDIC family.
Note: ASCII-incompatible encodings are those that don't map the 8-bit code 
points 0x20 to 0x7E to the 0x0020 to 0x007E Unicode code points)

Authors must not use CESU-8, UTF-7, BOCU-1 and/or SCSU as cross-site 
scripting attacks with these encodings have been demonstrated.
Authors should not use UTF-32 because not all HTML5 encoding algorithms 
can distinguish it from UTF-16."

html itself is shorter

"The html element represents the root of an HTML document.

 Widely available across major browsers (Baseline since 2015)

MDN Reference"

'MDN Reference' is a link that will open
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/html

in the browser.  For C code, hovering over 'strcmp' pops

"int strcmp(const char *__s1, const char *__s2)
Compare S1 and S2."

That isn't as detailed but it can be helpful. After all these years I 
sometimes forget which end of the parameter list the FILE* or fd goes on 
for fopen() versus open(). I suppose in the mists of time there was some 
reason why they are inconsistent.