• Re: Emacs Turns 50

    From Aidan Kehoe@kehoea@parhasard.net to alt.folklore.computers,comp.emacs on Wed Nov 4 07:14:02 2026
    From Newsgroup: alt.folklore.computers


    Ar an tri|| l|i de m|! na Samhna, scr|!obh Lawrence DrCOOliveiro:

    On Tue, 3 Nov 2026 21:16:21 -0000 (UTC), John McCue wrote:

    Coherent OS took the "original" microEMACS and added logic to
    compile a program and position the cursor to the error line in the
    editor.

    ThatrCOs the kind of thing that can be done with a few lines of Lisp by the user in *proper* Emacs. Efn!

    M-x compile RET , you donrCOt need to write any Lisp.

    The point of a minmal emacs is to be minimal. To their credit, I suppose, they havenrCOt expanded it to be able to read email.
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers,comp.emacs on Wed Nov 4 08:24:47 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 04 Nov 2026 07:14:02 +0000, Aidan Kehoe wrote:

    The point of a minmal emacs is to be minimal. To their credit, I
    suppose, they havenrCOt expanded it to be able to read email.

    Again, thatrCOs done with separate Lisp code, that you donrCOt even have
    to have installed if you donrCOt want to.

    Emacs is modular and extensible. ThatrCOs what makes it so powerful: not
    that it has every feature built-in, but it has the potential to have
    features added as the user wants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Tapiro Ubriaco@interwebs.dude@gmail.com to alt.folklore.computers,comp.emacs on Wed Nov 4 12:14:29 2026
    From Newsgroup: alt.folklore.computers

    On Sun, 01 Nov 2026 01:17:07 +0000, Nuno Silva wrote:

    On 2026-10-31, Tapiro Ubriaco wrote:

    On Fri, 30 Oct 2026 17:49:16 -0000 (UTC), John Levine wrote:


    Apple signs the software they distribute. As I read the GPLv3, if they
    ever signed a piece of GPLv3 software, they'd be required to sign
    every modified version of it, no matter how full of malware it was.
    That's nuts.

    I'm sorry, I'm not following.
    Would you you explain?

    Much appreciated.

    This probably means you can only install bash packages that have been
    signed with prcivate keys of Apple, at least as part of the operating system's install.

    Yes, fine, but what about "being required to sign every modified version
    of it"?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Geoff Clare@geoff@clare.See-My-Signature.invalid to alt.folklore.computers on Wed Nov 4 14:00:15 2026
    From Newsgroup: alt.folklore.computers

    Lawrence DrCOOliveiro wrote:

    On Tue, 3 Nov 2026 13:17:46 +0000, Geoff Clare wrote:

    Lawrence DrCOOliveiro wrote:

    Then why mention bash specifically in the requirements?

    Bash is not mentioned specifically in UNIX03 / SUSv3 requirements.
    (It is mentioned in non-normative rationale, as is ksh.)

    Then why did you say rCLI think it needs to execute bash in order for
    the system to conform to UNIX03rCY? You were the one who mentioned bash specifically.

    I already explained that earlier in the thread, as Nuno has pointed out.

    You do know that POSIX.1 and (the Base volumes of) SUS are one and
    the same standard, right?

    If the two specs were one and the same, there would not be separate certification for both.

    They *are* one and the same, as you can easily verify for yourself
    from the front page of SUSv5:

    https://pubs.opengroup.org/onlinepubs/9799919799/

    "POSIX.1-2024 is simultaneously IEEE Std 1003.1rao-2024 and The Open
    Group Standard Base Specifications, Issue 8."

    POSIX.1-2017/SUSv4 had the same wording (ending "Issue 7").

    POSIX.1-2001/SUSv3 worded it a little differently, as it was the first
    merged standard:

    "This standard has been jointly developed by the IEEE and The Open
    Group. It is both an IEEE Standard and an Open Group Technical Standard.
    [...]
    This standard is the single common revision to IEEE Std 1003.1-1996,
    IEEE Std 1003.2-1992, and the Base Specifications of The Open Group
    Single UNIX Specification, Version 2."

    There are separate certifications for POSIX and UNIX because, as I
    explained in my previous post (but you snipped), UNIX conformance
    requires some POSIX options to be supported that POSIX conformance
    does not. The details are in the "Conformance" chapter:

    https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap02.html

    Specifically, UNIX certification requires "XSI Conformance" (see
    section 2.1.4).

    And why does The Open Group allow this?

    You would have to ask them that.

    Because theyrCOre just out for the money, thatrCOs why. The rCLUnixrCY
    trademark doesnrCOt mean that much any more, if itrCOs just a commodity
    that can be bought.

    Obtaining UNIX certification requires passing tens of thousands of
    tests.

    And the ability to handwave those you didnrCOt pass. You *do* know,
    donrCOt you, that macOS, as shipped by Apple, is not actually
    SUS-compliant?

    Some of the macOS certifications in the past had "temporary waivers"
    which are granted for minor non-compliances and last 12 months.
    They were always corrected before the next certification.

    As it happens, Tahoe had no temporary waivers:

    https://www.opengroup.org/csq/repository/noreferences=1&RID=apple%252FCX1%25252F21.html
    https://www.opengroup.org/csq/repository/noreferences=1&RID=apple%25252FSD1%25252F23.html

    Or are you referring to the waivers granted for dbm_open() because
    on macOS it opens a single ".db" file instead of separate ".pag" and
    ".dir" files? The standard was relaxed between SUSv3 and SUSv4 to
    allow this and it is common in such situations for The Open Group
    to grant waivers for "following a future direction", i.e. they waive
    test failures for tests that fail when testing against SUSv3 but
    would not have failed when testing against SUSv4.
    --
    Geoff Clare <netnews@gclare.org.uk>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to alt.folklore.computers,comp.emacs on Wed Nov 4 15:12:00 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-04, Tapiro Ubriaco wrote:

    On Sun, 01 Nov 2026 01:17:07 +0000, Nuno Silva wrote:

    On 2026-10-31, Tapiro Ubriaco wrote:

    On Fri, 30 Oct 2026 17:49:16 -0000 (UTC), John Levine wrote:


    Apple signs the software they distribute. As I read the GPLv3, if they >>>> ever signed a piece of GPLv3 software, they'd be required to sign
    every modified version of it, no matter how full of malware it was.
    That's nuts.

    I'm sorry, I'm not following.
    Would you you explain?

    Much appreciated.

    This probably means you can only install bash packages that have been
    signed with prcivate keys of Apple, at least as part of the operating
    system's install.

    Yes, fine, but what about "being required to sign every modified version
    of it"?

    If they only allow their own keys to sign software to install at that
    level, then that's what they have to do in order to ensure users can
    exercise their right to modify the free software, otherwise they're
    basically trying to get away with GPL violation. GPLv3 made this more
    explicit.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers on Wed Nov 4 21:41:22 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 4 Nov 2026 14:00:15 +0000, Geoff Clare wrote:

    Lawrence DrCOOliveiro wrote:

    On Tue, 3 Nov 2026 13:17:46 +0000, Geoff Clare wrote:

    Lawrence DrCOOliveiro wrote:

    Then why mention bash specifically in the requirements?

    Bash is not mentioned specifically in UNIX03 / SUSv3 requirements.
    (It is mentioned in non-normative rationale, as is ksh.)

    Then why did you say rCLI think it needs to execute bash in order for
    the system to conform to UNIX03rCY? You were the one who mentioned bash
    specifically.

    I already explained that earlier in the thread ...

    You mean, the part where you started talking about ksh as well?

    You do know that POSIX.1 and (the Base volumes of) SUS are one and
    the same standard, right?

    If the two specs were one and the same, there would not be separate
    certification for both.

    They *are* one and the same ...

    Well, POSIX doesnrCOt mention bash, so why should SUS?

    Obtaining UNIX certification requires passing tens of thousands of
    tests.

    And the ability to handwave those you didnrCOt pass. You *do* know,
    donrCOt you, that macOS, as shipped by Apple, is not actually
    SUS-compliant?

    Some of the macOS certifications in the past had "temporary waivers"
    which are granted for minor non-compliances and last 12 months.
    They were always corrected before the next certification.

    As it happens, Tahoe had no temporary waivers:

    I just rechecked the compliance register for UNIX v03

    <https://www.opengroup.org//openbrand/register/xy.htm>

    YourCOll notice Apple is no longer listed ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Daniel@me@fuhgitabutit.com to alt.folklore.computers,comp.emacs on Wed Nov 4 19:19:28 2026
    From Newsgroup: alt.folklore.computers

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    A brief little retrospective on the history of Emacs, on the occasion
    of its 50th birthday <https://www.technologyreview.com/2026/10/20/1145399/emacs-turns-50/>.
    Before it was reimplemented in Lisp, the original version was written
    in TECO, a language that I once heard characterized as bearing a
    remarkable resemblance to transmission line noise.

    Fifty years of amazing software, wow. There aren't many packages in the
    wild today that can claim such longevity and success. It was roughly
    twenty years old when I began using it - and even then it was mature.

    Mind blown.
    --
    Daniel
    sysop | air & wave bbs
    finger | info@bbs.airandwave.net
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ted@loft.tnolan.com (Ted Nolan@tednolan to alt.folklore.computers,comp.emacs on Thu Nov 5 03:21:56 2026
    From Newsgroup: alt.folklore.computers

    In article <87mrroj77j.fsf@fuhgitabutit.com>,
    Daniel <me@fuhgitabutit.com> wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    A brief little retrospective on the history of Emacs, on the occasion
    of its 50th birthday
    <https://www.technologyreview.com/2026/10/20/1145399/emacs-turns-50/>.
    Before it was reimplemented in Lisp, the original version was written
    in TECO, a language that I once heard characterized as bearing a
    remarkable resemblance to transmission line noise.

    Fifty years of amazing software, wow. There aren't many packages in the
    wild today that can claim such longevity and success. It was roughly
    twenty years old when I began using it - and even then it was mature.

    Mind blown.


    Well, Unix, of course.
    --
    columbiaclosings.com
    What's not in Columbia anymore..
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to alt.folklore.computers,comp.emacs on Thu Nov 5 03:26:54 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 04 Nov 2026 19:19:28 -0800, Daniel wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    A brief little retrospective on the history of Emacs, on the occasion
    of its 50th birthday
    <https://www.technologyreview.com/2026/10/20/1145399/emacs-turns-50/>.
    Before it was reimplemented in Lisp, the original version was written
    in TECO, a language that I once heard characterized as bearing a
    remarkable resemblance to transmission line noise.

    Fifty years of amazing software, wow. There aren't many packages in the
    wild today that can claim such longevity and success. It was roughly
    twenty years old when I began using it - and even then it was mature.

    Mind blown.

    Yeah, emacs blew my mind when I tried to use it. Then I deleted it and
    install vim.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers,comp.emacs on Thu Nov 5 03:33:13 2026
    From Newsgroup: alt.folklore.computers

    On 5 Nov 2026 03:21:56 GMT, Ted Nolan <tednolan> wrote:

    There aren't many packages in the wild today that can claim such
    longevity and success.

    Well, Unix, of course.

    There is not a single line of original Bell Labs/AT&T code in any
    current Free software *nix system (BSD or Linux).

    AT&T launched a lawsuit to make sure of that.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Don_from_AZ@djatechNOSPAM@comcast.net.invalid to alt.folklore.computers,comp.emacs on Wed Nov 4 21:09:32 2026
    From Newsgroup: alt.folklore.computers

    rbowman <bowman@montana.com> writes:

    On Wed, 04 Nov 2026 19:19:28 -0800, Daniel wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    A brief little retrospective on the history of Emacs, on the occasion
    of its 50th birthday
    <https://www.technologyreview.com/2026/10/20/1145399/emacs-turns-50/>.
    Before it was reimplemented in Lisp, the original version was written
    in TECO, a language that I once heard characterized as bearing a
    remarkable resemblance to transmission line noise.

    Fifty years of amazing software, wow. There aren't many packages in the
    wild today that can claim such longevity and success. It was roughly
    twenty years old when I began using it - and even then it was mature.

    Mind blown.

    Yeah, emacs blew my mind when I tried to use it. Then I deleted it and install vim.

    I first learned to use Emacs on a Honeywell Multics machine in Phoenix
    circa 1980, so apparently only 4 years after it was born. I use it
    primarily as an editor, and for some of its packages like "Org
    Mode". This post is being written with "Gnus" under Emacs. I have not
    yet needed or had occasion to write any Lisp code myself.
    --
    -Don_from_AZ-
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to alt.folklore.computers,comp.emacs on Thu Nov 5 06:51:20 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 04 Nov 2026 21:09:32 -0700, Don_from_AZ wrote:

    I first learned to use Emacs on a Honeywell Multics machine in Phoenix
    circa 1980, so apparently only 4 years after it was born. I use it
    primarily as an editor, and for some of its packages like "Org Mode".
    This post is being written with "Gnus" under Emacs. I have not yet
    needed or had occasion to write any Lisp code myself.

    I was introduced to it much later in '99 when I started work at a new
    company and some of the programmers used it. The numbers a laughingly
    small today but iirc the emacs installation required about 10 times more
    disk space than vim. It was an easy decision when you were scrambling for every last MB. True, vim didn't tell fortunes or play go.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob Eager@throwaway0008@eager.cx to alt.folklore.computers,comp.emacs on Thu Nov 5 09:23:17 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 04 Nov 2026 19:19:28 -0800, Daniel wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    A brief little retrospective on the history of Emacs, on the occasion
    of its 50th birthday
    <https://www.technologyreview.com/2026/10/20/1145399/emacs-turns-50/>.
    Before it was reimplemented in Lisp, the original version was written
    in TECO, a language that I once heard characterized as bearing a
    remarkable resemblance to transmission line noise.

    Fifty years of amazing software, wow. There aren't many packages in the
    wild today that can claim such longevity and success. It was roughly
    twenty years old when I began using it - and even then it was mature.

    TECO is still around. I learned it in the early 1970s. Remarkably easy to
    use, and really no different to most other editors with single character commands.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Geoff Clare@geoff@clare.See-My-Signature.invalid to alt.folklore.computers on Thu Nov 5 13:53:50 2026
    From Newsgroup: alt.folklore.computers

    Lawrence DrCOOliveiro wrote:

    On Wed, 4 Nov 2026 14:00:15 +0000, Geoff Clare wrote:

    Lawrence DrCOOliveiro wrote:

    On Tue, 3 Nov 2026 13:17:46 +0000, Geoff Clare wrote:

    Lawrence DrCOOliveiro wrote:

    Then why mention bash specifically in the requirements?

    Bash is not mentioned specifically in UNIX03 / SUSv3 requirements.
    (It is mentioned in non-normative rationale, as is ksh.)

    Then why did you say rCLI think it needs to execute bash in order for
    the system to conform to UNIX03rCY? You were the one who mentioned bash
    specifically.

    I already explained that earlier in the thread ...

    You mean, the part where you started talking about ksh as well?

    No, before that. From my post on Fri, 30 Oct 2026 13:26:19 +0000:

    My point was that of the shells that /bin/sh can be configured to
    execute (bash, dash and zsh), bash conforms to UNIX03 but I don't
    think dash and zsh do. So if you want conforming behaviour you have
    to stick with the default configuration (bash).

    You do know that POSIX.1 and (the Base volumes of) SUS are one and
    the same standard, right?

    If the two specs were one and the same, there would not be separate
    certification for both.

    They *are* one and the same ...

    Well, POSIX doesnrCOt mention bash, so why should SUS?

    POSIX.1 does mention bash, in non-normative rationale, as I said before.
    It's not possible for POSIX.1 and (the Base volumes of) SUS to say
    different things, as they are one and the same standard.

    I just searched the PDF of IEEE Std. 1003.1-2024 for "bash" and the first
    hit is on page 3868, from some text in XRAT C.2.2.4 Dollar-Single-Quotes
    that explains how escape sequences in C string literals compare to their
    use in $'...' in the shell:

    The \x escape sequence in C can be followed by an arbitrary number
    of hexadecimal digits. The ksh93 implementation of $'...' also
    consumes an arbitrary number of hexadecimal digits; bash consumes
    at most two hexadecimal digits in this case. This standard leaves
    the result unspecified if more than two hexadecimal digits follow \x.

    The same text can be found in SUSv5 here:

    https://pubs.opengroup.org/onlinepubs/9799919799/xrat/V4_xcu_chap01.html#tag_23_02_02_04

    I just rechecked the compliance register for UNIX v03

    <https://www.opengroup.org//openbrand/register/xy.htm>

    YourCOll notice Apple is no longer listed ...

    That's strange. Looks like a glitch on their web site, as it's
    only missing from the "umbrella" UNIX03 product standard listing;
    it's still there for the individual product standards that comprise
    UNIX03:

    Internationalized System Calls and Libraries Extd V3
    https://www.opengroup.org/openbrand/register/sd.htm

    Commands and Utilities V4
    https://www.opengroup.org/openbrand/register/cx.htm

    C Language V2
    https://www.opengroup.org/openbrand/register/lm.htm

    Internationalized Terminal Interfaces
    https://www.opengroup.org/openbrand/register/uu.htm

    and all of those plus the UNIX03 umbrella one are listed on the page
    for Apple's certifications:

    https://www.opengroup.org/openbrand/register/apple.htm
    --
    Geoff Clare <netnews@gclare.org.uk>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to alt.folklore.computers,comp.emacs on Thu Nov 5 15:04:26 2026
    From Newsgroup: alt.folklore.computers

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On 5 Nov 2026 03:21:56 GMT, Ted Nolan <tednolan> wrote:

    There aren't many packages in the wild today that can claim such
    longevity and success.

    Well, Unix, of course.

    There is not a single line of original Bell Labs/AT&T code in any
    current Free software *nix system (BSD or Linux).

    Nonsense.


    AT&T launched a lawsuit to make sure of that.

    Which they lost, handily.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to alt.folklore.computers,comp.emacs on Thu Nov 5 16:13:59 2026
    From Newsgroup: alt.folklore.computers

    scott@slp53.sl.home (Scott Lurndal) writes:
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On 5 Nov 2026 03:21:56 GMT, Ted Nolan <tednolan> wrote:

    There aren't many packages in the wild today that can claim such
    longevity and success.

    Well, Unix, of course.

    There is not a single line of original Bell Labs/AT&T code in any
    current Free software *nix system (BSD or Linux).

    Nonsense.


    AT&T launched a lawsuit to make sure of that.

    Which they lost, handily

    My bad, I was referring to the SCO lawsuit. The AT&T
    BSD lawsuit resulted in BSD adding additional copyright
    text to certain source files crediting AT&T.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to alt.folklore.computers,comp.emacs on Thu Nov 5 09:26:46 2026
    From Newsgroup: alt.folklore.computers

    On 11/5/26 09:13, Scott Lurndal wrote:
    scott@slp53.sl.home (Scott Lurndal) writes:
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On 5 Nov 2026 03:21:56 GMT, Ted Nolan <tednolan> wrote:

    There aren't many packages in the wild today that can claim such
    longevity and success.

    Well, Unix, of course.

    There is not a single line of original Bell Labs/AT&T code in any
    current Free software *nix system (BSD or Linux).

    Nonsense.


    AT&T launched a lawsuit to make sure of that.

    Which they lost, handily

    My bad, I was referring to the SCO lawsuit. The AT&T
    BSD lawsuit resulted in BSD adding additional copyright
    text to certain source files crediting AT&T.

    The problem (as I see it) is that Unix was originally distributed for basically the cost of the distribution media. I guess there were
    restrictions of re-distribution. Later on AT&T tried to convert it into
    a for-profit product, but the cat had already left the barn at that point.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers on Thu Nov 5 19:00:58 2026
    From Newsgroup: alt.folklore.computers

    On Thu, 5 Nov 2026 13:53:50 +0000, Geoff Clare wrote:

    From my post on Fri, 30 Oct 2026 13:26:19 +0000:

    My point was that of the shells that /bin/sh can be configured
    to execute (bash, dash and zsh), bash conforms to UNIX03 but I
    don't think dash and zsh do. So if you want conforming behaviour
    you have to stick with the default configuration (bash).

    Which is not true anyway <https://manpages.debian.org/dash(1)>.

    POSIX.1 does mention bash, in non-normative rationale, as I said
    before.

    No, you said rCLI think it needs to execute bash in order for the system
    to conform to UNIX03rCY. rCLNeedsrCY is hardly rCLnon-normativerCY is it? Unless
    you are now saying that UNIX03 is in fact not the same as POSIX.

    I just rechecked the compliance register for UNIX v03

    <https://www.opengroup.org//openbrand/register/xy.htm>

    YourCOll notice Apple is no longer listed ...

    That's strange. Looks like a glitch on their web site, as it's only
    missing from the "umbrella" UNIX03 product standard listing; it's
    still there for the individual product standards that comprise
    UNIX03:

    Internationalized System Calls and Libraries Extd V3
    https://www.opengroup.org/openbrand/register/sd.htm

    Commands and Utilities V4
    https://www.opengroup.org/openbrand/register/cx.htm

    C Language V2
    https://www.opengroup.org/openbrand/register/lm.htm

    Internationalized Terminal Interfaces
    https://www.opengroup.org/openbrand/register/uu.htm

    These only mention macOS 26 rCLTahoerCY, not macOS 27 rCLGolden GaterCY. WasnrCOt that released several months ago? HasnrCOt it passed UNIX
    compliance yet? (Or at all?)

    Could that be why it was dropped from the register page?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers,comp.emacs on Thu Nov 5 19:06:32 2026
    From Newsgroup: alt.folklore.computers

    On Thu, 5 Nov 2026 09:26:46 -0700, Peter Flass wrote:

    The problem (as I see it) is that Unix was originally distributed
    for basically the cost of the distribution media. I guess there were restrictions of re-distribution.

    It was always distributed under sundry restrictions on what you could
    do with it. Then with UNIX v7, the permission for study and classroom
    use was *removed*, just as the rCLLions BookrCY was becoming popular. So suddenly it was no longer legal to have that book.

    Later on AT&T tried to convert it into a for-profit product, but the
    cat had already left the barn at that point.

    Oh, IrCOm sure they did make some decent money licensing it to the UNIX
    vendors -- enough to fund continuing development of System III,
    followed by all the System V releases. (What happened to rCLSystem IVrCY
    ... ?)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to alt.folklore.computers,comp.emacs on Thu Nov 5 19:17:58 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-05, rbowman <bowman@montana.com> wrote:

    On Wed, 04 Nov 2026 21:09:32 -0700, Don_from_AZ wrote:

    I first learned to use Emacs on a Honeywell Multics machine in Phoenix
    circa 1980, so apparently only 4 years after it was born. I use it
    primarily as an editor, and for some of its packages like "Org Mode".
    This post is being written with "Gnus" under Emacs. I have not yet
    needed or had occasion to write any Lisp code myself.

    I was introduced to it much later in '99 when I started work at a new company and some of the programmers used it. The numbers a laughingly
    small today but iirc the emacs installation required about 10 times more disk space than vim. It was an easy decision when you were scrambling for every last MB. True, vim didn't tell fortunes or play go.

    Eight Megabytes And Constantly Swapping

    I looked into it a couple of times, but quickly realized
    that we aren't from the same planet.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to alt.folklore.computers,comp.emacs on Thu Nov 5 19:38:32 2026
    From Newsgroup: alt.folklore.computers

    On Thu, 5 Nov 2026 09:26:46 -0700, Peter Flass wrote:

    The problem (as I see it) is that Unix was originally distributed for basically the cost of the distribution media. I guess there were
    restrictions of re-distribution. Later on AT&T tried to convert it into
    a
    for-profit product, but the cat had already left the barn at that point.

    https://spectrum.ieee.org/the-strange-birth-and-long-life-of-unix

    AT&T's status as a monopoly came with restrictions and selling software
    wasn't included in what they could do. It was a strange situation. A
    company I worked for was running a copy that fell off the back of a truck
    in Cambridge MA on their PDP-11.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers,comp.emacs on Thu Nov 5 22:59:04 2026
    From Newsgroup: alt.folklore.computers

    On Thu, 05 Nov 2026 19:17:58 GMT, Charlie Gibbs wrote:

    I looked into [Emacs] a couple of times, but quickly realized that
    we aren't from the same planet.

    IrCOve used a bunch of different full-screen editors over the years. I
    even tried doing some work in TECO in command mode for a while (for an
    employer who was paying for the account, so I thought IrCOd try and keep
    usage costs down).

    DEC was promoting EDT as a standard editor across multiple of its
    operating systems. I found that painful. Then they introduced TPU
    on VMS, which I liked quite a lot.

    vi/vim was the standard on proprietary UNIXes, so I gritted my teeth
    and put up with that for many years. Then, once Linux wiped them all
    out, and I could be sure that just about any Linux distro a client
    might be using would at least have the option of running Emacs, I wholeheartedly switched to that.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers,comp.emacs on Thu Nov 5 23:09:11 2026
    From Newsgroup: alt.folklore.computers

    On Thu, 05 Nov 2026 10:55:28 +0000, Lars Brinkhoff wrote:

    There also is not a single line of the original Emacs in the current
    version.

    Counting from TECO-based versions? ;)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to alt.folklore.computers,comp.emacs on Fri Nov 6 00:12:43 2026
    From Newsgroup: alt.folklore.computers

    On 11/5/26 20:17, Charlie Gibbs wrote:
    On 2026-11-05, rbowman <bowman@montana.com> wrote:

    On Wed, 04 Nov 2026 21:09:32 -0700, Don_from_AZ wrote:

    I first learned to use Emacs on a Honeywell Multics machine in Phoenix
    circa 1980, so apparently only 4 years after it was born. I use it
    primarily as an editor, and for some of its packages like "Org Mode".
    This post is being written with "Gnus" under Emacs. I have not yet
    needed or had occasion to write any Lisp code myself.

    I was introduced to it much later in '99 when I started work at a new
    company and some of the programmers used it. The numbers a laughingly
    small today but iirc the emacs installation required about 10 times more
    disk space than vim. It was an easy decision when you were scrambling for
    every last MB. True, vim didn't tell fortunes or play go.

    Eight Megabytes And Constantly Swapping

    I looked into it a couple of times, but quickly realized
    that we aren't from the same planet.


    A text editor should edit text, no more. I laugh at editors
    that pretend to be 'small', like vim or even nano.

    Nano is 287kB. The text editor I've used since 39 years
    fits in just 40kB. It's a full-screen editor that can open
    multiple files at once, with cut/copy and paste between them.
    I wrote it 1987 for a system that only had a line editor
    at the time. It was modeled on the Rand editor of the era.
    No frills. It was my first C-programming attempt, and it
    shows.

    Of course, there is no syntax highlighting or functions
    like justification, spell checking etc. Those are delegated
    to standard utilities. (As they should be!)

    I've taken it with me on every new system since and still
    use it every day.

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers,comp.emacs on Thu Nov 5 23:24:38 2026
    From Newsgroup: alt.folklore.computers

    On Fri, 6 Nov 2026 00:12:43 +0100, Jeroen Belleman wrote:

    A text editor should edit text, no more.

    Emacs is an editor, not just a text editor.

    I have successfully used it to patch binary files.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John McCue@jmclnx@gmail.com.invalid to alt.folklore.computers,comp.emacs on Fri Nov 6 01:27:25 2026
    From Newsgroup: alt.folklore.computers

    Followups trimmed to: comp.emacs

    In comp.emacs Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
    On Tue, 3 Nov 2026 21:16:21 -0000 (UTC), John McCue wrote:

    Coherent OS took the "original" microEMACS and added logic to
    compile a program and position the cursor to the error line in the
    editor.

    That's the kind of thing that can be done with a few lines of Lisp
    by the user in *proper* Emacs.

    It was impossible to compile GNU Emacs on the first version
    of Coherent I went to. It was a 16 bit system at that time.

    Their microEMACS clone was quite useable on that system.
    --
    csh(1) - "An elegant shell, for a more... civilized age."
    - Paraphrasing Star Wars
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Daniel@me@fuhgitabutit.com to alt.folklore.computers,comp.emacs on Thu Nov 5 23:26:51 2026
    From Newsgroup: alt.folklore.computers

    Don_from_AZ <djatechNOSPAM@comcast.net.invalid> writes:

    rbowman <bowman@montana.com> writes:

    On Wed, 04 Nov 2026 19:19:28 -0800, Daniel wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    A brief little retrospective on the history of Emacs, on the occasion
    of its 50th birthday
    <https://www.technologyreview.com/2026/10/20/1145399/emacs-turns-50/>. >>>> Before it was reimplemented in Lisp, the original version was written
    in TECO, a language that I once heard characterized as bearing a
    remarkable resemblance to transmission line noise.

    Fifty years of amazing software, wow. There aren't many packages in the
    wild today that can claim such longevity and success. It was roughly
    twenty years old when I began using it - and even then it was mature.

    Mind blown.

    Yeah, emacs blew my mind when I tried to use it. Then I deleted it and
    install vim.

    I first learned to use Emacs on a Honeywell Multics machine in Phoenix
    circa 1980, so apparently only 4 years after it was born. I use it
    primarily as an editor, and for some of its packages like "Org
    Mode". This post is being written with "Gnus" under Emacs. I have not
    yet needed or had occasion to write any Lisp code myself.

    I have yet to play with org mode despite the infectious eagerness
    everyone displays when I hear about it in irc. And yes, gnus is
    constantly in a buffer for me. For the browser, though, lynx wins out.

    I've written a few tools in lisp to automate some things because lazy.
    --
    Daniel
    sysop | air & wave bbs
    finger | info@bbs.airandwave.net
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Geoff Clare@geoff@clare.See-My-Signature.invalid to alt.folklore.computers on Fri Nov 6 13:59:19 2026
    From Newsgroup: alt.folklore.computers

    Lawrence DrCOOliveiro wrote:

    On Thu, 5 Nov 2026 13:53:50 +0000, Geoff Clare wrote:

    From my post on Fri, 30 Oct 2026 13:26:19 +0000:

    My point was that of the shells that /bin/sh can be configured
    to execute (bash, dash and zsh), bash conforms to UNIX03 but I
    don't think dash and zsh do. So if you want conforming behaviour
    you have to stick with the default configuration (bash).

    Which is not true anyway <https://manpages.debian.org/dash(1)>.

    It would have been helpful if you pointed to which part of that
    web page you are referring to. I assume it is the part that says
    "dash is a POSIX-compliant implementation of /bin/sh that aims to
    be as small as possible".

    Notice that it says POSIX-compliant, not UNIX-compliant.

    The difference, as I explained before, is that UNIX conformance
    requires the POSIX "XSI Option" to be supported (and others).
    One of the XSI requirements is that "echo -n foo" writes "-n foo"
    and a newline. With the built-in echo on dash (at least on Debian;
    I haven't tried it on macOS) it writes just "foo" (the -n suppresses
    the newline). This is allowed for POSIX conformance, but not for
    UNIX conformance.

    There may well be other ways that dash does not conform to UNIX
    (or indeed POSIX, despite Debian's claim) requirements too. I seem
    to remember discussions in the Austin Group about it not handling
    multibyte characters correctly.

    POSIX.1 does mention bash, in non-normative rationale, as I said
    before.

    No, you said rCLI think it needs to execute bash in order for the system
    to conform to UNIX03rCY. rCLNeedsrCY is hardly rCLnon-normativerCY is it?

    You are mixing up two completely separate statements that I made.

    "I think it needs to execute bash ..." was a statement of my opinion
    regarding how macOS needs to be configured in order to conform to
    UNIX03.

    "POSIX.1 does mention bash, in non-normative rationale" was a statement
    of fact about the POSIX.1/SUS standard (backed up with evidence).

    I just rechecked the compliance register for UNIX v03

    <https://www.opengroup.org//openbrand/register/xy.htm>

    YourCOll notice Apple is no longer listed ...

    That's strange. Looks like a glitch on their web site, as it's only
    missing from the "umbrella" UNIX03 product standard listing; it's
    still there for the individual product standards that comprise
    UNIX03:

    Internationalized System Calls and Libraries Extd V3
    https://www.opengroup.org/openbrand/register/sd.htm

    Commands and Utilities V4
    https://www.opengroup.org/openbrand/register/cx.htm

    C Language V2
    https://www.opengroup.org/openbrand/register/lm.htm

    Internationalized Terminal Interfaces
    https://www.opengroup.org/openbrand/register/uu.htm

    These only mention macOS 26 rCLTahoerCY, not macOS 27 rCLGolden GaterCY. WasnrCOt that released several months ago? HasnrCOt it passed UNIX
    compliance yet? (Or at all?)

    Could that be why it was dropped from the register page?

    The previous certifications for Sequoia are still listed with the
    Tahoe ones on the above pages. So regardless of what the situation
    is with Golden Gate, there wouldn't be any reason to remove the
    Tahoe ones from the register.

    Still seems like just a glitch to me.
    --
    Geoff Clare <netnews@gclare.org.uk>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to alt.folklore.computers on Fri Nov 6 07:43:28 2026
    From Newsgroup: alt.folklore.computers

    On 11/6/26 06:59, Geoff Clare wrote:
    Lawrence DrCOOliveiro wrote:

    On Thu, 5 Nov 2026 13:53:50 +0000, Geoff Clare wrote:

    From my post on Fri, 30 Oct 2026 13:26:19 +0000:

    My point was that of the shells that /bin/sh can be configured
    to execute (bash, dash and zsh), bash conforms to UNIX03 but I
    don't think dash and zsh do. So if you want conforming behaviour
    you have to stick with the default configuration (bash).

    Which is not true anyway <https://manpages.debian.org/dash(1)>.

    It would have been helpful if you pointed to which part of that
    web page you are referring to. I assume it is the part that says
    "dash is a POSIX-compliant implementation of /bin/sh that aims to
    be as small as possible".

    Notice that it says POSIX-compliant, not UNIX-compliant.

    The difference, as I explained before, is that UNIX conformance
    requires the POSIX "XSI Option" to be supported (and others).
    One of the XSI requirements is that "echo -n foo" writes "-n foo"
    and a newline. With the built-in echo on dash (at least on Debian;
    I haven't tried it on macOS) it writes just "foo" (the -n suppresses
    the newline). This is allowed for POSIX conformance, but not for
    UNIX conformance.

    There may well be other ways that dash does not conform to UNIX
    (or indeed POSIX, despite Debian's claim) requirements too. I seem
    to remember discussions in the Austin Group about it not handling
    multibyte characters correctly.

    POSIX.1 does mention bash, in non-normative rationale, as I said
    before.

    No, you said rCLI think it needs to execute bash in order for the system
    to conform to UNIX03rCY. rCLNeedsrCY is hardly rCLnon-normativerCY is it?

    You are mixing up two completely separate statements that I made.

    "I think it needs to execute bash ..." was a statement of my opinion regarding how macOS needs to be configured in order to conform to
    UNIX03.

    "POSIX.1 does mention bash, in non-normative rationale" was a statement
    of fact about the POSIX.1/SUS standard (backed up with evidence).

    I just rechecked the compliance register for UNIX v03

    <https://www.opengroup.org//openbrand/register/xy.htm>

    YourCOll notice Apple is no longer listed ...

    That's strange. Looks like a glitch on their web site, as it's only
    missing from the "umbrella" UNIX03 product standard listing; it's
    still there for the individual product standards that comprise
    UNIX03:

    Internationalized System Calls and Libraries Extd V3
    https://www.opengroup.org/openbrand/register/sd.htm

    Commands and Utilities V4
    https://www.opengroup.org/openbrand/register/cx.htm

    C Language V2
    https://www.opengroup.org/openbrand/register/lm.htm

    Internationalized Terminal Interfaces
    https://www.opengroup.org/openbrand/register/uu.htm

    These only mention macOS 26 rCLTahoerCY, not macOS 27 rCLGolden GaterCY.
    WasnrCOt that released several months ago? HasnrCOt it passed UNIX
    compliance yet? (Or at all?)

    Could that be why it was dropped from the register page?

    The previous certifications for Sequoia are still listed with the
    Tahoe ones on the above pages. So regardless of what the situation
    is with Golden Gate, there wouldn't be any reason to remove the
    Tahoe ones from the register.

    Still seems like just a glitch to me.


    Linux:
    isdev@pingvin:~$ echo foo
    foo
    isdev@pingvin:~$ echo -n foo
    fooisdev@pingvin:~$
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to alt.folklore.computers on Fri Nov 6 15:42:09 2026
    From Newsgroup: alt.folklore.computers

    Peter Flass <Peter@Iron-Spring.com> writes:
    On 11/6/26 06:59, Geoff Clare wrote:
    Lawrence DrCOOliveiro wrote:

    On Thu, 5 Nov 2026 13:53:50 +0000, Geoff Clare wrote:

    From my post on Fri, 30 Oct 2026 13:26:19 +0000:

    My point was that of the shells that /bin/sh can be configured
    to execute (bash, dash and zsh), bash conforms to UNIX03 but I
    don't think dash and zsh do. So if you want conforming behaviour
    you have to stick with the default configuration (bash).

    Which is not true anyway <https://manpages.debian.org/dash(1)>.

    It would have been helpful if you pointed to which part of that
    web page you are referring to. I assume it is the part that says
    "dash is a POSIX-compliant implementation of /bin/sh that aims to
    be as small as possible".

    Notice that it says POSIX-compliant, not UNIX-compliant.

    The difference, as I explained before, is that UNIX conformance
    requires the POSIX "XSI Option" to be supported (and others).
    One of the XSI requirements is that "echo -n foo" writes "-n foo"
    and a newline. With the built-in echo on dash (at least on Debian;
    I haven't tried it on macOS) it writes just "foo" (the -n suppresses
    the newline). This is allowed for POSIX conformance, but not for
    UNIX conformance.

    There may well be other ways that dash does not conform to UNIX
    (or indeed POSIX, despite Debian's claim) requirements too. I seem
    to remember discussions in the Austin Group about it not handling
    multibyte characters correctly.

    POSIX.1 does mention bash, in non-normative rationale, as I said
    before.

    No, you said rCLI think it needs to execute bash in order for the system >>> to conform to UNIX03rCY. rCLNeedsrCY is hardly rCLnon-normativerCY is it? >>
    You are mixing up two completely separate statements that I made.

    "I think it needs to execute bash ..." was a statement of my opinion
    regarding how macOS needs to be configured in order to conform to
    UNIX03.

    "POSIX.1 does mention bash, in non-normative rationale" was a statement
    of fact about the POSIX.1/SUS standard (backed up with evidence).

    I just rechecked the compliance register for UNIX v03

    <https://www.opengroup.org//openbrand/register/xy.htm>

    YourCOll notice Apple is no longer listed ...

    That's strange. Looks like a glitch on their web site, as it's only
    missing from the "umbrella" UNIX03 product standard listing; it's
    still there for the individual product standards that comprise
    UNIX03:

    Internationalized System Calls and Libraries Extd V3
    https://www.opengroup.org/openbrand/register/sd.htm

    Commands and Utilities V4
    https://www.opengroup.org/openbrand/register/cx.htm

    C Language V2
    https://www.opengroup.org/openbrand/register/lm.htm

    Internationalized Terminal Interfaces
    https://www.opengroup.org/openbrand/register/uu.htm

    These only mention macOS 26 rCLTahoerCY, not macOS 27 rCLGolden GaterCY. >>> WasnrCOt that released several months ago? HasnrCOt it passed UNIX
    compliance yet? (Or at all?)

    Could that be why it was dropped from the register page?

    The previous certifications for Sequoia are still listed with the
    Tahoe ones on the above pages. So regardless of what the situation
    is with Golden Gate, there wouldn't be any reason to remove the
    Tahoe ones from the register.

    Still seems like just a glitch to me.


    Linux:
    isdev@pingvin:~$ echo foo
    foo
    isdev@pingvin:~$ echo -n foo
    fooisdev@pingvin:~$

    There are a dozen different shells for linux. You need
    to be more specific about which one you are actually using.

    You can determine which shell you are using:

    $ echo $0
    -ksh

    bash(1) by default doesn't start in posix mode:

    $ bash
    $ echo $0
    bash
    $ set -o | grep posix
    posix off
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to alt.folklore.computers on Fri Nov 6 10:48:08 2026
    From Newsgroup: alt.folklore.computers

    On 11/6/26 08:42, Scott Lurndal wrote:
    Peter Flass <Peter@Iron-Spring.com> writes:
    On 11/6/26 06:59, Geoff Clare wrote:
    Lawrence DrCOOliveiro wrote:

    On Thu, 5 Nov 2026 13:53:50 +0000, Geoff Clare wrote:

    From my post on Fri, 30 Oct 2026 13:26:19 +0000:

    My point was that of the shells that /bin/sh can be configured >>>>> to execute (bash, dash and zsh), bash conforms to UNIX03 but I >>>>> don't think dash and zsh do. So if you want conforming behaviour >>>>> you have to stick with the default configuration (bash).

    Which is not true anyway <https://manpages.debian.org/dash(1)>.

    It would have been helpful if you pointed to which part of that
    web page you are referring to. I assume it is the part that says
    "dash is a POSIX-compliant implementation of /bin/sh that aims to
    be as small as possible".

    Notice that it says POSIX-compliant, not UNIX-compliant.

    The difference, as I explained before, is that UNIX conformance
    requires the POSIX "XSI Option" to be supported (and others).
    One of the XSI requirements is that "echo -n foo" writes "-n foo"
    and a newline. With the built-in echo on dash (at least on Debian;
    I haven't tried it on macOS) it writes just "foo" (the -n suppresses
    the newline). This is allowed for POSIX conformance, but not for
    UNIX conformance.

    There may well be other ways that dash does not conform to UNIX
    (or indeed POSIX, despite Debian's claim) requirements too. I seem
    to remember discussions in the Austin Group about it not handling
    multibyte characters correctly.

    POSIX.1 does mention bash, in non-normative rationale, as I said
    before.

    No, you said rCLI think it needs to execute bash in order for the system >>>> to conform to UNIX03rCY. rCLNeedsrCY is hardly rCLnon-normativerCY is it? >>>
    You are mixing up two completely separate statements that I made.

    "I think it needs to execute bash ..." was a statement of my opinion
    regarding how macOS needs to be configured in order to conform to
    UNIX03.

    "POSIX.1 does mention bash, in non-normative rationale" was a statement
    of fact about the POSIX.1/SUS standard (backed up with evidence).

    I just rechecked the compliance register for UNIX v03

    <https://www.opengroup.org//openbrand/register/xy.htm>

    YourCOll notice Apple is no longer listed ...

    That's strange. Looks like a glitch on their web site, as it's only
    missing from the "umbrella" UNIX03 product standard listing; it's
    still there for the individual product standards that comprise
    UNIX03:

    Internationalized System Calls and Libraries Extd V3
    https://www.opengroup.org/openbrand/register/sd.htm

    Commands and Utilities V4
    https://www.opengroup.org/openbrand/register/cx.htm

    C Language V2
    https://www.opengroup.org/openbrand/register/lm.htm

    Internationalized Terminal Interfaces
    https://www.opengroup.org/openbrand/register/uu.htm

    These only mention macOS 26 rCLTahoerCY, not macOS 27 rCLGolden GaterCY. >>>> WasnrCOt that released several months ago? HasnrCOt it passed UNIX
    compliance yet? (Or at all?)

    Could that be why it was dropped from the register page?

    The previous certifications for Sequoia are still listed with the
    Tahoe ones on the above pages. So regardless of what the situation
    is with Golden Gate, there wouldn't be any reason to remove the
    Tahoe ones from the register.

    Still seems like just a glitch to me.


    Linux:
    isdev@pingvin:~$ echo foo
    foo
    isdev@pingvin:~$ echo -n foo
    fooisdev@pingvin:~$

    There are a dozen different shells for linux. You need
    to be more specific about which one you are actually using.

    You can determine which shell you are using:

    $ echo $0
    -ksh

    bash(1) by default doesn't start in posix mode:

    $ bash
    $ echo $0
    bash
    $ set -o | grep posix
    posix off

    bash.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to alt.folklore.computers on Fri Nov 6 17:59:00 2026
    From Newsgroup: alt.folklore.computers

    In alt.folklore.computers Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On 5 Nov 2026 03:21:56 GMT, Ted Nolan <tednolan> wrote:

    There aren't many packages in the wild today that can claim such
    longevity and success.

    Well, Unix, of course.

    There is not a single line of original Bell Labs/AT&T code in any
    current Free software *nix system (BSD or Linux).

    AT&T launched a lawsuit to make sure of that.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to alt.folklore.computers on Fri Nov 6 18:16:54 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-06, Peter Flass wrote:

    On 11/6/26 06:59, Geoff Clare wrote:
    Lawrence DrCOOliveiro wrote:

    On Thu, 5 Nov 2026 13:53:50 +0000, Geoff Clare wrote:

    From my post on Fri, 30 Oct 2026 13:26:19 +0000:

    My point was that of the shells that /bin/sh can be configured
    to execute (bash, dash and zsh), bash conforms to UNIX03 but I
    don't think dash and zsh do. So if you want conforming behaviour
    you have to stick with the default configuration (bash).

    Which is not true anyway <https://manpages.debian.org/dash(1)>.

    It would have been helpful if you pointed to which part of that
    web page you are referring to. I assume it is the part that says
    "dash is a POSIX-compliant implementation of /bin/sh that aims to
    be as small as possible".

    Notice that it says POSIX-compliant, not UNIX-compliant.

    The difference, as I explained before, is that UNIX conformance
    requires the POSIX "XSI Option" to be supported (and others).
    One of the XSI requirements is that "echo -n foo" writes "-n foo"
    and a newline. With the built-in echo on dash (at least on Debian;
    I haven't tried it on macOS) it writes just "foo" (the -n suppresses
    the newline). This is allowed for POSIX conformance, but not for
    UNIX conformance.

    There may well be other ways that dash does not conform to UNIX
    (or indeed POSIX, despite Debian's claim) requirements too. I seem
    to remember discussions in the Austin Group about it not handling
    multibyte characters correctly.

    POSIX.1 does mention bash, in non-normative rationale, as I said
    before.

    No, you said rCLI think it needs to execute bash in order for the system >>> to conform to UNIX03rCY. rCLNeedsrCY is hardly rCLnon-normativerCY is it? >>
    You are mixing up two completely separate statements that I made.

    "I think it needs to execute bash ..." was a statement of my opinion
    regarding how macOS needs to be configured in order to conform to
    UNIX03.

    "POSIX.1 does mention bash, in non-normative rationale" was a statement
    of fact about the POSIX.1/SUS standard (backed up with evidence).

    I just rechecked the compliance register for UNIX v03

    <https://www.opengroup.org//openbrand/register/xy.htm>

    YourCOll notice Apple is no longer listed ...

    That's strange. Looks like a glitch on their web site, as it's only
    missing from the "umbrella" UNIX03 product standard listing; it's
    still there for the individual product standards that comprise
    UNIX03:

    Internationalized System Calls and Libraries Extd V3
    https://www.opengroup.org/openbrand/register/sd.htm

    Commands and Utilities V4
    https://www.opengroup.org/openbrand/register/cx.htm

    C Language V2
    https://www.opengroup.org/openbrand/register/lm.htm

    Internationalized Terminal Interfaces
    https://www.opengroup.org/openbrand/register/uu.htm

    These only mention macOS 26 rCLTahoerCY, not macOS 27 rCLGolden GaterCY. >>> WasnrCOt that released several months ago? HasnrCOt it passed UNIX
    compliance yet? (Or at all?)

    Could that be why it was dropped from the register page?

    The previous certifications for Sequoia are still listed with the
    Tahoe ones on the above pages. So regardless of what the situation
    is with Golden Gate, there wouldn't be any reason to remove the
    Tahoe ones from the register.

    Still seems like just a glitch to me.


    Linux:
    isdev@pingvin:~$ echo foo
    foo
    isdev@pingvin:~$ echo -n foo
    fooisdev@pingvin:~$

    This is one of the situations where it's wrong to say "Linux" and where
    calling it e.g. "GNU/Linux" would at least be better (although it'd
    *still* miss the key part here, and just get a hint of what the shell
    may be, if the "GNU" part isn't being used just to refer to such
    distributions generically).

    What would matter here is which shell is that and which echo is that.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to alt.folklore.computers on Fri Nov 6 18:21:59 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-06, Scott Lurndal wrote:

    Peter Flass <Peter@Iron-Spring.com> writes:
    [...]
    Linux:
    isdev@pingvin:~$ echo foo
    foo
    isdev@pingvin:~$ echo -n foo
    fooisdev@pingvin:~$

    There are a dozen different shells for linux. You need
    to be more specific about which one you are actually using.

    You can determine which shell you are using:

    $ echo $0
    -ksh

    Isn't this just the name of the executable entity through which the
    shell was execve()d?

    bash(1) by default doesn't start in posix mode:

    $ bash
    $ echo $0
    bash
    $ set -o | grep posix
    posix off
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers on Fri Nov 6 20:42:34 2026
    From Newsgroup: alt.folklore.computers

    On Fri, 6 Nov 2026 13:59:19 +0000, Geoff Clare wrote:

    Notice that it says POSIX-compliant, not UNIX-compliant.

    After you were insisting they were one and the same?

    "I think it needs to execute bash ..." was a statement of my opinion regarding how macOS needs to be configured in order to conform to
    UNIX03.

    Given that UNIX03 doesnrCOt mention bash, that statement doesnrCOt make
    any sense.

    The previous certifications for Sequoia are still listed with the
    Tahoe ones on the above pages.

    Individual tests, but not on the certification register <https://www.opengroup.org//openbrand/register/xy.htm>

    Still seems like just a glitch to me.

    Five months after Golden Gate was released? Seeing the old version
    dropped, and the new version (coincidentally, or not) nowhere to be
    found? Pretty big rCLglitchrCY, if you ask me ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers on Fri Nov 6 20:43:38 2026
    From Newsgroup: alt.folklore.computers

    On Fri, 6 Nov 2026 07:43:28 -0700, Peter Flass wrote:

    Linux:
    isdev@pingvin:~$ echo foo
    foo
    isdev@pingvin:~$ echo -n foo
    fooisdev@pingvin:~$

    ThatrCOs not rCLLinuxrCY. Remember, rCLLinuxrCY is the kernel. What yourCOre seeing there is the behaviour of a shell, and you havenrCOt said which
    one.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to alt.folklore.computers on Fri Nov 6 21:52:32 2026
    From Newsgroup: alt.folklore.computers

    Nuno Silva <nunojsilva@invalid.invalid> wrote:
    On 2026-11-06, Peter Flass wrote:

    On 11/6/26 06:59, Geoff Clare wrote:
    Lawrence DrCOOliveiro wrote:

    On Thu, 5 Nov 2026 13:53:50 +0000, Geoff Clare wrote:
    <snip>
    The difference, as I explained before, is that UNIX conformance
    requires the POSIX "XSI Option" to be supported (and others).
    One of the XSI requirements is that "echo -n foo" writes "-n foo"
    and a newline. With the built-in echo on dash (at least on Debian;
    I haven't tried it on macOS) it writes just "foo" (the -n suppresses
    the newline). This is allowed for POSIX conformance, but not for
    UNIX conformance.

    There may well be other ways that dash does not conform to UNIX
    (or indeed POSIX, despite Debian's claim) requirements too. I seem
    to remember discussions in the Austin Group about it not handling
    multibyte characters correctly.

    POSIX.1 does mention bash, in non-normative rationale, as I said
    before.

    <snip>
    Linux:
    isdev@pingvin:~$ echo foo
    foo
    isdev@pingvin:~$ echo -n foo
    fooisdev@pingvin:~$

    This is one of the situations where it's wrong to say "Linux" and where calling it e.g. "GNU/Linux" would at least be better (although it'd
    *still* miss the key part here, and just get a hint of what the shell
    may be, if the "GNU" part isn't being used just to refer to such distributions generically).

    What would matter here is which shell is that and which echo is that.

    Both 'bash' and '/bin/sh' (which is actually 'dash'). IIUC each has
    'echo' as a builtin command. Also '/bin/echo' (which comes from
    GNU coreutils) shows the same behaviour.

    Supressing newline in echo is used by quite a lot of shell scripts
    and the '-n' option is normal way to do this on Linux.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers on Sat Nov 7 00:35:10 2026
    From Newsgroup: alt.folklore.computers

    On Fri, 6 Nov 2026 21:52:32 -0000 (UTC), Waldek Hebisch wrote:

    Supressing newline in echo is used by quite a lot of shell scripts
    and the '-n' option is normal way to do this on Linux.

    As on every other *nix that uses the GNU userland utilities.

    I really cannot imagine anybody wanting a command environment that did
    not interpret rCL-nrCY in this way ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to alt.folklore.computers on Sat Nov 7 10:02:14 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-07, Lawrence DrCOOliveiro wrote:

    On Fri, 6 Nov 2026 21:52:32 -0000 (UTC), Waldek Hebisch wrote:

    Supressing newline in echo is used by quite a lot of shell scripts
    and the '-n' option is normal way to do this on Linux.

    As on every other *nix that uses the GNU userland utilities.

    I really cannot imagine anybody wanting a command environment that did
    not interpret rCL-nrCY in this way ...

    It is non-standard, and that has implications for portability. However convenient that "-n" option may be where present, is there really a
    reason not to use something more portable and conformant? IEEE
    1003.1-2008 suggests printf (84381rCo84383).
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to alt.folklore.computers on Sat Nov 7 21:24:52 2026
    From Newsgroup: alt.folklore.computers

    Nuno Silva <nunojsilva@invalid.invalid> wrote:
    On 2026-11-07, Lawrence DrCOOliveiro wrote:

    On Fri, 6 Nov 2026 21:52:32 -0000 (UTC), Waldek Hebisch wrote:

    Supressing newline in echo is used by quite a lot of shell scripts
    and the '-n' option is normal way to do this on Linux.

    As on every other *nix that uses the GNU userland utilities.

    I really cannot imagine anybody wanting a command environment that did
    not interpret rCL-nrCY in this way ...

    It is non-standard, and that has implications for portability. However convenient that "-n" option may be where present, is there really a
    reason not to use something more portable and conformant? IEEE
    1003.1-2008 suggests printf (84381rCo84383).

    Recently I had displeasure to use 'printf' in a Makefile, in my
    setup that lead to orgy of quoting. Comparing, cases when
    'echo -n' were enough were much simpler.

    'echo -n' is standard, AFAIK it is GNU standard and compatible
    with Posix. It seems that only Unix compliance disallows it.
    Given long history, widespread use and utility there should be
    very strong reason to disallow it. I am not aware of such a
    reason.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers on Sat Nov 7 22:25:18 2026
    From Newsgroup: alt.folklore.computers

    On Sat, 7 Nov 2026 21:24:52 -0000 (UTC), Waldek Hebisch wrote:

    Recently I had displeasure to use 'printf' in a Makefile, in my
    setup that lead to orgy of quoting.

    The shell builtin has the rCL%qrCY format specifier which automatically
    handles all quoting of shell specials.

    OK, I think this is a bash-ism, itrCOs not supported by (supposedly more vanilla POSIX-conforming) dash ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to alt.folklore.computers on Sun Nov 8 00:25:44 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-07, Waldek Hebisch wrote:

    Nuno Silva <nunojsilva@invalid.invalid> wrote:
    On 2026-11-07, Lawrence DrCOOliveiro wrote:

    On Fri, 6 Nov 2026 21:52:32 -0000 (UTC), Waldek Hebisch wrote:

    Supressing newline in echo is used by quite a lot of shell scripts
    and the '-n' option is normal way to do this on Linux.

    As on every other *nix that uses the GNU userland utilities.

    I really cannot imagine anybody wanting a command environment that did
    not interpret rCL-nrCY in this way ...

    It is non-standard, and that has implications for portability. However
    convenient that "-n" option may be where present, is there really a
    reason not to use something more portable and conformant? IEEE
    1003.1-2008 suggests printf (84381rCo84383).

    Recently I had displeasure to use 'printf' in a Makefile, in my
    setup that lead to orgy of quoting. Comparing, cases when
    'echo -n' were enough were much simpler.

    'echo -n' is standard, AFAIK it is GNU standard and compatible
    with Posix.

    'echo -n' is standard if it prints "-n" followed by a newline.

    -2The echo utility writes its arguments to standard output, followed
    by a <newline>. If there are no arguments, only the <newline> is
    written.-+ -- POSIX (2008 again, lines 84298rCo84299)

    It seems that only Unix compliance disallows it.
    Given long history, widespread use and utility there should be
    very strong reason to disallow it. I am not aware of such a
    reason.

    It seems to me that widespread use and long history *is* the very strong
    reason not to allow or require it.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kerr-Mudd, John@admin@127.0.0.1 to alt.folklore.computers,comp.emacs on Sun Nov 8 14:26:52 2026
    From Newsgroup: alt.folklore.computers

    On Fri, 6 Nov 2026 00:12:43 +0100
    Jeroen Belleman <jeroen@nospam.please> wrote:

    On 11/5/26 20:17, Charlie Gibbs wrote:
    On 2026-11-05, rbowman <bowman@montana.com> wrote:

    On Wed, 04 Nov 2026 21:09:32 -0700, Don_from_AZ wrote:

    I first learned to use Emacs on a Honeywell Multics machine in Phoenix >>> circa 1980, so apparently only 4 years after it was born. I use it
    primarily as an editor, and for some of its packages like "Org Mode".
    This post is being written with "Gnus" under Emacs. I have not yet
    needed or had occasion to write any Lisp code myself.

    I was introduced to it much later in '99 when I started work at a new
    company and some of the programmers used it. The numbers a laughingly
    small today but iirc the emacs installation required about 10 times more >> disk space than vim. It was an easy decision when you were scrambling for >> every last MB. True, vim didn't tell fortunes or play go.

    Eight Megabytes And Constantly Swapping

    I looked into it a couple of times, but quickly realized
    that we aren't from the same planet.


    A text editor should edit text, no more. I laugh at editors
    that pretend to be 'small', like vim or even nano.

    Nano is 287kB. The text editor I've used since 39 years
    fits in just 40kB. It's a full-screen editor that can open
    multiple files at once, with cut/copy and paste between them.
    I wrote it 1987 for a system that only had a line editor
    at the time. It was modeled on the Rand editor of the era.
    No frills. It was my first C-programming attempt, and it
    shows.

    Of course, there is no syntax highlighting or functions
    like justification, spell checking etc. Those are delegated
    to standard utilities. (As they should be!)

    I've taken it with me on every new system since and still
    use it every day.

    Jeroen Belleman

    I've never indulged in the wonders of emacs, but small text editors are pshurely available. For DOS I think TED at 3k is small yet usable unless
    you want to edit huge (>64k) text files.
    --
    Bah, and indeed Humbug.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Geoff Clare@geoff@clare.See-My-Signature.invalid to alt.folklore.computers on Mon Nov 9 14:05:36 2026
    From Newsgroup: alt.folklore.computers

    Lawrence DrCOOliveiro wrote:

    On Fri, 6 Nov 2026 13:59:19 +0000, Geoff Clare wrote:

    Notice that it says POSIX-compliant, not UNIX-compliant.

    After you were insisting they were one and the same?

    At this point I am going to assume that you are pretending to
    misunderstand things that I have written to try to get me to
    provide more and more corrections. I'm not going to play that
    game any more, sorry.

    If you genuinely thought that I ever said POSIX-compliant and
    UNIX-compliant were one and the same thing, I suggest you
    carefully re-read all of my posts in this thread and you will
    see that I did not.
    --
    Geoff Clare <netnews@gclare.org.uk>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to alt.folklore.computers on Mon Nov 9 22:23:11 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/2026 10:05 PM, Geoff Clare wrote:
    Lawrence DrCOOliveiro wrote:

    On Fri, 6 Nov 2026 13:59:19 +0000, Geoff Clare wrote:

    Notice that it says POSIX-compliant, not UNIX-compliant.

    After you were insisting they were one and the same?

    At this point I am going to assume that you are pretending to
    misunderstand things that I have written to try to get me to
    provide more and more corrections. I'm not going to play that
    game any more, sorry.

    If you genuinely thought that I ever said POSIX-compliant and
    UNIX-compliant were one and the same thing, I suggest you
    carefully re-read all of my posts in this thread and you will
    see that I did not.


    Dear Geoff,

    Don't worry about Lawrence. He is just a Python influencer, and contin-
    ues every conversation until he can show off his Python-skills -- which
    he doesn't have.


    Best wishes, and happy not answering Lawrence!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to alt.folklore.computers,comp.emacs on Mon Nov 9 22:25:48 2026
    From Newsgroup: alt.folklore.computers

    On 10/30/2026 8:16 PM, Nuno Silva wrote:
    On 2026-10-29, rbowman wrote:

    On Thu, 29 Oct 2026 04:56:45 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    It seems to me, the move away from GNU software has to do with the
    adoption of version 3 of the GPL. Something new in that version is being >>> seen by certain folks in Apple as a threat, where they were happy to
    bundle and redistribute software that was licensed under GPLv2.

    https://www.gnu.org/licenses/gpl-3.0.en.html

    I'm not a lawyer so I cannot figure out this steaming pile of legalese.

    In short, if a corporation is arguing that GPLv3 is a reason not to use software or newer versions under that license, you probably should steer clear of that corporation, that means either they don't intend to honor
    the freedoms they need to honor in strong copyleft, or that they're
    trying to reserve the right of defeating these freedoms with patent-wrangling.

    Or is there something else I've forgotten about?

    IIRC GPLv3 was mostly or completely about spelling out what were the
    expected implications in GPLv2, but which some corporations, notably
    TiVo, managed to circumvent and get away with it.


    I thought the GPL3 meant it was a reason for everyone to stay clear of
    GPL3 software. I mean, isn't that what happened in the real world, and
    more and more people started to use MIT-, BSD-based licenses instead?

    So in that sense, doesn't that mean the corporations won the TiVo fight?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Geoff Clare@geoff@clare.See-My-Signature.invalid to alt.folklore.computers on Mon Nov 9 14:38:57 2026
    From Newsgroup: alt.folklore.computers

    Waldek Hebisch wrote:

    'echo -n' is standard, AFAIK it is GNU standard and compatible
    with Posix. It seems that only Unix compliance disallows it.
    Given long history, widespread use and utility there should be
    very strong reason to disallow it. I am not aware of such a
    reason.

    "echo -n" suppressing newline is historical BSD behaviour.
    "echo -n" writing "-n" and a newline is historical System V
    behaviour (with "\c" on the end of the string suppressing newline).

    When the POSIX and XPG/SUS standards were developed in the late
    1980's and early 1990's, the POSIX.2 authors decided to allow
    both behaviours, whereas the XPG authors decided to require the
    System V behaviour. (At the time they were separate standards.)

    When POSIX.1, POSIX.2 and SUSv2 were merged in 2001, no doubt
    there was a discussion of whether to keep the System V behaviour
    when the XSI option is supported. Relaxing the standard to allow
    both behaviours regardless of whether XSI is supported would have
    broken long-established uses of echo on XPG and SUSv1/2 conforming
    systems.

    Bash supports both behaviours, selectable via the bash-specific
    "shopt" built-in or via the corresponding BASHOPTS environment
    variable:

    $ sh --version | head -n 1
    GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
    $ sh -c 'echo -n foo; echo'
    foo
    $ env BASHOPTS=xpg_echo sh -c 'echo -n foo'
    -n foo

    I don't know whether Apple made xpg_echo the default in their
    version of bash or if they expect systems (or individual users)
    to set BASHOPTS if they want a SUS "conforming environment".
    --
    Geoff Clare <netnews@gclare.org.uk>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to alt.folklore.computers on Mon Nov 9 16:00:45 2026
    From Newsgroup: alt.folklore.computers

    Geoff Clare <geoff@clare.See-My-Signature.invalid> writes:
    Lawrence DrCOOliveiro wrote:

    On Fri, 6 Nov 2026 13:59:19 +0000, Geoff Clare wrote:

    Notice that it says POSIX-compliant, not UNIX-compliant.

    After you were insisting they were one and the same?

    At this point I am going to assume that you are pretending to
    misunderstand things that I have written to try to get me to
    provide more and more corrections. I'm not going to play that
    game any more, sorry.

    LDO is a troll, and has been once since it started posting
    relatively recently.

    Best to simply ignore it.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to alt.folklore.computers,comp.emacs on Mon Nov 9 19:58:56 2026
    From Newsgroup: alt.folklore.computers

    On Mon, 9 Nov 2026 22:25:48 +0800, Johann 'Myrkraverk' Oskarsson wrote:

    On 10/30/2026 8:16 PM, Nuno Silva wrote:
    On 2026-10-29, rbowman wrote:

    On Thu, 29 Oct 2026 04:56:45 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    It seems to me, the move away from GNU software has to do with the
    adoption of version 3 of the GPL. Something new in that version is
    being seen by certain folks in Apple as a threat, where they were
    happy to bundle and redistribute software that was licensed under
    GPLv2.

    https://www.gnu.org/licenses/gpl-3.0.en.html

    I'm not a lawyer so I cannot figure out this steaming pile of
    legalese.

    In short, if a corporation is arguing that GPLv3 is a reason not to use
    software or newer versions under that license, you probably should
    steer clear of that corporation, that means either they don't intend to
    honor the freedoms they need to honor in strong copyleft, or that
    they're trying to reserve the right of defeating these freedoms with
    patent-wrangling.

    Or is there something else I've forgotten about?

    IIRC GPLv3 was mostly or completely about spelling out what were the
    expected implications in GPLv2, but which some corporations, notably
    TiVo, managed to circumvent and get away with it.


    I thought the GPL3 meant it was a reason for everyone to stay clear of
    GPL3 software. I mean, isn't that what happened in the real world, and
    more and more people started to use MIT-, BSD-based licenses instead?

    So in that sense, doesn't that mean the corporations won the TiVo fight?

    Or did FOSS win? Google developed Angular, and Meta developed React. Both
    are under the MIT license. Code-OSS was developed by Microsoft and also
    uses the MIT license. Chromium has inherited several licenses from its component parts. There are many more examples.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers on Mon Nov 9 22:13:34 2026
    From Newsgroup: alt.folklore.computers

    On Mon, 9 Nov 2026 14:05:36 +0000, Geoff Clare wrote:

    Lawrence DrCOOliveiro wrote:

    On Fri, 6 Nov 2026 13:59:19 +0000, Geoff Clare wrote:

    Notice that it says POSIX-compliant, not UNIX-compliant.

    After you were insisting they were one and the same?

    At this point I am going to assume that you are pretending to
    misunderstand things that I have written to try to get me to
    provide more and more corrections. I'm not going to play that
    game any more, sorry.

    If you genuinely thought that I ever said POSIX-compliant and
    UNIX-compliant were one and the same thing, I suggest you
    carefully re-read all of my posts in this thread and you will
    see that I did not.

    From previous postings:

    Lawrence DrCOOliveiro wrote:
    >
    > On Tue, 3 Nov 2026 13:17:46 +0000, Geoff Clare wrote:
    >
    >> You do know that POSIX.1 and (the Base volumes of) SUS are one
    >> and the same standard, right?
    >
    > If the two specs were one and the same, there would not be
    > separate certification for both.

    They *are* one and the same, as you can easily verify for yourself
    from the front page of SUSv5 ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to alt.folklore.computers on Tue Nov 10 01:21:06 2026
    From Newsgroup: alt.folklore.computers

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Mon, 9 Nov 2026 14:05:36 +0000, Geoff Clare wrote:

    Lawrence DrCOOliveiro wrote:

    On Fri, 6 Nov 2026 13:59:19 +0000, Geoff Clare wrote:

    Notice that it says POSIX-compliant, not UNIX-compliant.

    After you were insisting they were one and the same?

    At this point I am going to assume that you are pretending to
    misunderstand things that I have written to try to get me to
    provide more and more corrections. I'm not going to play that
    game any more, sorry.

    If you genuinely thought that I ever said POSIX-compliant and
    UNIX-compliant were one and the same thing, I suggest you
    carefully re-read all of my posts in this thread and you will
    see that I did not.

    From previous postings:

    Lawrence DrCOOliveiro wrote:
    >
    > On Tue, 3 Nov 2026 13:17:46 +0000, Geoff Clare wrote:
    >
    >> You do know that POSIX.1 and (the Base volumes of) SUS are one
    >> and the same standard, right?
    >
    > If the two specs were one and the same, there would not be
    > separate certification for both.

    They *are* one and the same, as you can easily verify for yourself
    from the front page of SUSv5 ...

    You're just digging yourself deeper and deeper. The specs
    have been the same since TOG(XPG) and POSIX merged decades ago.

    With the merge, the spec picked up various optional
    requirements from XPG that means that there are
    multiple sets of requirements. POSIX requires
    the base set, while Unix03 requires the base set
    plus additional optional features.

    So the spec is the same, but there are multiple
    certifications available for different subsets of the spec.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Andreas Eder@a_eder_muc@web.de to alt.folklore.computers,comp.emacs on Fri Nov 13 11:26:03 2026
    From Newsgroup: alt.folklore.computers

    On Fr 30 Okt 2026 at 23:45, Bob Eager wrote:

    On Fri, 30 Oct 2026 18:20:53 -0400, Chris Ahlstrom wrote:

    I liked microEMACS as an alternative to PC vi, in the early 90's,
    in a DOS environment.

    I started with it then. Then on OS/2. I still use it - on FreeBSD.

    I compiled it for a Motorola VME installation in 1988. Worked like a
    charm.
    It took me a while to find a way to compile FNU Emacs and some people
    still preferred microEMACS.

    'Andreas
    --
    ceterum censeo redmondinem esse delendam
    --- Synchronet 3.22a-Linux NewsLink 1.2