From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 175c23e8 for ; Sun, 5 Jan 2020 01:50:32 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 6CF159B4D0; Sun, 5 Jan 2020 11:50:31 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id E017395170; Sun, 5 Jan 2020 11:50:02 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="EMPZ5ljn"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id C99899516C; Sun, 5 Jan 2020 11:49:59 +1000 (AEST) Received: from mail-ot1-f50.google.com (mail-ot1-f50.google.com [209.85.210.50]) by minnie.tuhs.org (Postfix) with ESMTPS id 564F795165 for ; Sun, 5 Jan 2020 11:49:59 +1000 (AEST) Received: by mail-ot1-f50.google.com with SMTP id k16so61940397otb.2 for ; Sat, 04 Jan 2020 17:49:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Ta4Zpp8BDEtIkuAe7h136E9ztwq/JneA/2U+/JrbDh8=; b=EMPZ5ljnESN1rnntL4r3FF2xrmGonp3HYSBhVWYn1hwABqqISAOd6/AJzMYNrBijIR rCCO1jY+6jMnpShq4t84QLiROmgPx9Fo02iTrjI1BgprbhIOKIvuz3yO1I6QWhuIfPXK FUhccviM534Xk2QXtW/3Lhv4EQFnrQ/lB6JD++Hhw8NvPtzqp/X2Z6LinhcgcrZ0Zd/N iX/B3QhWxK6l5r7jM4QNYJ3+1qNoo78ju4xUtBTaG1Y+btlvT1bDHZty9P3YoLTsrMKo pFCQS/Bncf5cDpD1qzQw9bj3pKpyN9yYZg6LOjfea5FspLH4Wb0GaibuV7YNwyq18Ke+ kJFg== 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; bh=Ta4Zpp8BDEtIkuAe7h136E9ztwq/JneA/2U+/JrbDh8=; b=NDmOH+tSFeLePRqvPiz+95T7fl1SUVC0Y1pA+CBVS3TQ8zxU3LrJar2RMZovH0MtWL dlkWnBinBt4Xc1Xay5BFGBAEAc/LBFsJn/9M13yvWvnP31suT0IYoCSbOFNxBzChMxcy 6+BJluakYO+OkxeonBc480GhG7r35bUa7ukLcUYkjcP4d0dxzVxrsZpUCoeBm/hAZXv7 DsexecbBq08ViwWln7wu28SNNxy0ImnxjmxmWXUByJuuUoiI6xbtXiHeDe6qAqriD9FS G2I93/b6XrxMBOEenJY/pcOOrWIuGEhyuULVeg8I1SQ3tNQ+j2S9OVZIyYCgBtbmkz9C x22A== X-Gm-Message-State: APjAAAXLc+O5WQDEpQ4RWkvERhwEmZKpFMZvirQFJ0WqDAKSJqkTJPXx ypWmTAYE46wV60eDXIPs5K1dOxcqO9Q31BvMgdeKSvsx X-Google-Smtp-Source: APXvYqwPjLjCy2QjrXqRC7ssTS/jmEzWc3e1mYaWmejv+EkZHz9sj4KfDg7e1zFcbd9EaPq3YHnFc8YPC+ZBXRmxJxA= X-Received: by 2002:a9d:62c7:: with SMTP id z7mr98268847otk.189.1578188998340; Sat, 04 Jan 2020 17:49:58 -0800 (PST) MIME-Version: 1.0 References: <202001040258.0042wuic1359237@mail.cs.dartmouth.edu> <1ingL0-5g6-00@marmaro.de> <202001042106.004L69C1448350@darkstar.fourwinds.com> <026e2abb-fe04-4186-d3b2-0f32109d323a@neophilic.com> In-Reply-To: <026e2abb-fe04-4186-d3b2-0f32109d323a@neophilic.com> From: Adam Thornton Date: Sat, 4 Jan 2020 18:49:46 -0700 Message-ID: To: The Eunuchs Hysterical Society Content-Type: multipart/alternative; boundary="000000000000a2765d059b5ac2ef" Subject: Re: [TUHS] sh: cmd | >file X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000a2765d059b5ac2ef Content-Type: text/plain; charset="UTF-8" v7 Bourne shell does not appear to treat '#' as a comment. I've built termlib and curses for v7 and am now trying to find a small screen editor. I was trying se, but the version I have ships as a shell archive, and it doesn't actually unpack on v7, in part because of the comments. v7 is a target in Jove's Ovmakefile, so that's what I'm trying now. Slow-pasting uuencoded files into the terminal is gross, but efficacious.... Adam On Sat, Jan 4, 2020 at 5:48 PM Eric Allman wrote: > I contacted Steve --- he is on the list, and says he'll weigh in. > > eric > > > On 2020-01-04 13:06, Jon Steinhart wrote: > > Dave Horsfall writes: > >> On Sat, 4 Jan 2020, markus schnalke wrote: > >> > >>> My question was not about the use cases for ``>file'' but *why* it was > >>> made a simple command. Let me explain: > >>> > >>> One creates an empty file or truncates a file with: > >>> > >>> >file > >>> > >>> why not with: > >>> > >>> :>file > >>> ? > >>> > >>> To me it looks to be the more sensible ... more regular way. > >> > >> The Unix philosophy, perhaps i.e. keep it simple? Why have ":" (an > actual > >> internal Shell command) when "" (the null command) will do the job? > >> > >> I guess only the Bell Labs bods here can answer this. > >> > >> -- Dave > > > > Don't know if Steve Bourne is on this list, but he's been a great source > > of information when I've had questions about why the shell did things the > > way it did. > > > > Jon > > > --000000000000a2765d059b5ac2ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
v7 Bourne shell does not appear to treat '#' = as a comment.

I've built termlib and curs= es for v7 and am now trying to find a small screen editor.=C2=A0 I was tryi= ng se, but the version I have ships as a shell archive, and it doesn't = actually unpack on v7, in part because of the comments.

v7 is a target in Jove's Ovmakefile, so that's what I'm t= rying now.=C2=A0 Slow-pasting uuencoded files into the terminal is gross, b= ut efficacious....

Adam

On Sat, Jan 4, 20= 20 at 5:48 PM Eric Allman <tuhs= @eric.allman.name> wrote:
I contacted Steve --- he is on the list, and says he'l= l weigh in.

eric


On 2020-01-04 13:06, Jon Steinhart wrote:
> Dave Horsfall writes:
>> On Sat, 4 Jan 2020, markus schnalke wrote:
>>
>>> My question was not about the use cases for ``>file'= 9; but *why* it was
>>> made a simple command. Let me explain:
>>>
>>> One creates an empty file or truncates a file with:
>>>
>>>=C2=A0 =C2=A0 =C2=A0>file
>>>
>>> why not with:
>>>
>>>=C2=A0 =C2=A0 =C2=A0:>file
>>> ?
>>>
>>> To me it looks to be the more sensible ... more regular way. >>
>> The Unix philosophy, perhaps i.e. keep it simple?=C2=A0 Why have &= quot;:" (an actual
>> internal Shell command) when "" (the null command) will = do the job?
>>
>> I guess only the Bell Labs bods here can answer this.
>>
>> -- Dave
>
> Don't know if Steve Bourne is on this list, but he's been a gr= eat source
> of information when I've had questions about why the shell did thi= ngs the
> way it did.
>
> Jon
>
--000000000000a2765d059b5ac2ef--