From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7434 invoked from network); 23 Jun 2020 01:54:12 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 23 Jun 2020 01:54:12 -0000 Received: (qmail 4019 invoked by alias); 23 Jun 2020 01:54:06 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: Sender: zsh-workers@zsh.org X-Seq: 46101 Received: (qmail 8434 invoked by uid 1010); 23 Jun 2020 01:54:06 -0000 X-Qmail-Scanner-Diagnostics: from mail-ot1-f41.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25850. spamassassin: 3.4.4. Clear:RC:0(209.85.210.41):SA:0(-1.9/5.0):. Processed in 1.902097 secs); 23 Jun 2020 01:54:06 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.210.41 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=P9ehTUeiUYbQ1Xq/cKhh95+1fVpvYWVuJS3UBXFhV2A=; b=DjTooKxUhcu5kwbkN0+OiIDSpJhZO4ef8Sk1qENhUmQPzU0yQ5l7eKHO0vVXcC58oU UX0yZgHIQCILTNPxuyaHOhULyDdHX5SM07HyYS7daVYRjMHeVZZo71qRWLH43sAc3cOO 0kmJBrmoqNHOCAdJpzplPOn3GmK+tKoBgkuGtwUhiBNuYWAaBQUM45XGXR3QTPGlmk+5 EVqex8NQuSjbjaMxDq1kzJrz+wXuA7YpxtjoBYmHDG/ZPonnVXBqu7QqTm+vy5Rkt1wI 0TF/DEdWYlU76IbxapDfsa337OyOmGrOPAtQ5SIK3iMOb2RftNMeIrlEFI/gwSu/8pzz I34A== X-Gm-Message-State: AOAM532BoD+e56nAiHB+NN3Rik0g+c+POTIRfqQV3mux5kTOJ7vikvuA 8tBjapHfxGTUVRRvRj8AiWcqutssEfwTuZx+58Mk+Q== X-Google-Smtp-Source: ABdhPJw/a75gcQhSTyQMEfD7AD6yTXI4nLeh0NxSR81dkaKvBgk403LE/uOWnWLBXilgQ1C3+BtnmLvVpWGhVGTqu40= X-Received: by 2002:a9d:5d11:: with SMTP id b17mr11408238oti.260.1592877210905; Mon, 22 Jun 2020 18:53:30 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bart Schaefer Date: Mon, 22 Jun 2020 18:53:20 -0700 Message-ID: Subject: Re: support for POSIX job control terminal management in zsh To: Godmar Back Cc: "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" On Mon, Jun 22, 2020 at 6:40 PM Godmar Back wrote: > > Hence my question, out of curiosity, is: why does zsh not follow > POSIX.1 semantics in this regard? The direct answer is because zsh didn't even begin to claim any level of POSIX compliance until those constraints began to be added to the "sh" emulation mode, more than 10 years after the shell was written. The indirect answer is because this is a pretty dark corner case, and there is no organized effort to examine the entire POSIX spec for items that haven't yet been included. What effort there has been has been focused on shell scripting more than interactive use.