From: Adam Thornton <athornton@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] sh: cmd | >file
Date: Sat, 4 Jan 2020 18:49:46 -0700 [thread overview]
Message-ID: <CAP2nic03vxZ-G=WBPVuakVKikZxa8CqUM=xNHsrBC-_enj+Lpw@mail.gmail.com> (raw)
In-Reply-To: <026e2abb-fe04-4186-d3b2-0f32109d323a@neophilic.com>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
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 <tuhs@eric.allman.name> 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
> >
>
[-- Attachment #2: Type: text/html, Size: 2258 bytes --]
next prev parent reply other threads:[~2020-01-05 1:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 2:58 Doug McIlroy
2020-01-04 10:07 ` markus schnalke
2020-01-04 11:47 ` Robert Clausecker
2020-01-04 22:31 ` Chet Ramey
2020-01-04 21:02 ` Dave Horsfall
2020-01-04 21:06 ` Jon Steinhart
2020-01-05 0:03 ` Eric Allman
2020-01-05 1:49 ` Adam Thornton [this message]
2020-01-05 2:44 ` Chet Ramey
2020-01-05 8:15 ` Brantley Coile
2020-01-05 15:16 ` Chet Ramey
2020-01-04 21:11 ` Dave Horsfall
2020-01-04 21:39 ` Warner Losh
2020-01-04 22:19 ` Terry Jones
2020-01-04 22:33 ` Chet Ramey
2020-01-04 23:53 ` Dave Horsfall
2020-01-05 0:04 ` Andreas Kusalananda Kähäri
2020-01-05 2:41 ` Chet Ramey
2020-01-05 13:45 ` Sven Mascheck via TUHS
2020-01-05 15:18 ` Chet Ramey
2020-01-05 21:21 ` Dave Horsfall
2020-01-06 13:53 ` Chet Ramey
2020-01-06 15:42 ` Brantley Coile
2020-01-06 15:46 ` arnold
2020-01-06 16:13 ` Clem Cole
2020-01-06 20:44 ` arnold
2020-01-06 20:51 ` Steve Nickolas
2020-01-06 21:32 ` Clem Cole
2020-01-06 21:39 ` Brad Spencer
2020-01-06 21:29 ` Dave Horsfall
2020-01-06 21:55 ` Chet Ramey
2020-01-06 22:22 ` Dave Horsfall
2020-01-06 22:52 ` Dan Cross
2020-01-07 0:50 ` Adam Thornton
2020-01-06 22:10 ` Bakul Shah
2020-01-04 22:44 ` markus schnalke
2020-01-04 23:01 ` Terry Jones
2020-01-04 22:22 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2020-01-07 5:03 Brian Walden
2020-01-07 4:49 Brian Walden
2020-01-06 19:47 Doug McIlroy
2020-01-06 16:11 Brian Walden
2020-01-06 16:33 ` Clem Cole
2020-01-06 3:24 Brian Walden
2020-01-06 15:42 ` Richard Salz
2020-01-06 15:45 ` Brantley Coile
2020-01-03 12:45 markus schnalke
2020-01-03 14:00 ` Steffen Nurpmeso
2020-01-03 17:03 ` Brian Zick
2020-01-03 17:18 ` markus schnalke
2020-01-04 0:53 ` Sven Mascheck via TUHS
2020-01-04 20:41 ` Steffen Nurpmeso
2020-01-03 19:38 ` markus schnalke
2020-01-03 19:44 ` Warner Losh
2020-01-03 22:49 ` Michael Parson
2020-01-03 23:32 ` Dave Horsfall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP2nic03vxZ-G=WBPVuakVKikZxa8CqUM=xNHsrBC-_enj+Lpw@mail.gmail.com' \
--to=athornton@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).