Computer Old Farts Forum
 help / color / mirror / Atom feed
From: perry at piermont.com (Perry E. Metzger)
Subject: [COFF] Other OSes?
Date: Mon, 9 Jul 2018 07:50:35 -0400	[thread overview]
Message-ID: <20180709075035.59bf47d0@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <20180709073241.6babe8f4@jabberwock.cb.piermont.com>

On Mon, 9 Jul 2018 07:32:41 -0400 "Perry E. Metzger"
<perry at piermont.com> wrote:
> On Sun, 8 Jul 2018 21:52:09 -0600 Warner Losh <imp at bsdimp.com>
> wrote:
> > It would also let the program do 'noise
> > words' like TOPS-20 did w/o having to actually parse them...  
> 
> Noise words are a thing Unix is missing, but given the lack of
> CMND JSYS style completion, the reason for the lack is obvious --
> nothing generates noisewords so nothing needs to ignore them. This
> is yet another cool thing clang's --complete hack could make widely
> available, though then we'd need a standard for noisewords.

Actually, it occurs to me that noisewords aren't actually needed. The
printed help during completion can handle conveying the information
that noisewords provided.

Perry

> > clang --complete is an interesting variation on my ideas within
> > the realm of doing non-standard weird things and starts to place
> > the burden of knowledge on the program itself, which is more in
> > line with the thinking of Unix and the main stream of OOish
> > thought we've know about since the early 70s with smalltalk and
> > other such pioneering things.  
> 
> Precisely. The clang hack is exactly what one would want if it could
> be made popular.
> 
> Perry

-- 
Perry E. Metzger		perry at piermont.com


  reply	other threads:[~2018-07-09 11:50 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  5:56 wkt
2018-07-05  6:29 ` spedraja
2018-07-05  6:40 ` bakul
2018-07-05 15:23   ` clemc
2018-07-05 20:49     ` scj
2018-07-05 21:25       ` david
2018-07-06 15:42         ` gtaylor
2018-07-05 22:38       ` ralph
2018-07-05 23:11       ` bakul
2018-07-06  0:06         ` lm
2018-07-06 15:49           ` gtaylor
2018-07-06  0:52       ` tytso
2018-07-06  5:59         ` ralph
2018-07-06 15:59           ` gtaylor
2018-07-06 16:10             ` ralph
2018-07-06 16:47               ` gtaylor
2018-07-06 15:57         ` gtaylor
2018-07-06 15:38       ` gtaylor
2018-07-09  1:56         ` tytso
2018-07-09  3:25           ` gtaylor
2018-07-09  3:35             ` crossd
2018-07-09  3:43               ` gtaylor
2018-07-09  3:52                 ` imp
2018-07-09 11:32                   ` perry
2018-07-09 11:50                     ` perry [this message]
2018-07-09 11:34                 ` crossd
2018-07-09  5:23             ` tytso
2018-07-09 12:52               ` clemc
2018-07-09 13:06                 ` [COFF] PiDP Obsolesces Guaranteed clemc
2018-07-09 14:39                 ` [COFF] Other OSes? tytso
2018-07-09 14:46                   ` clemc
2018-07-09 11:24           ` perry
2018-07-05 22:51   ` ewayte
2018-07-08 20:31   ` perry
2018-07-08 20:53     ` perry
2018-07-09  2:44     ` crossd
2018-07-10  5:30       ` bakul
2018-07-16 14:49         ` crossd
2018-07-16 16:59           ` [COFF] Capabilities (was " bakul
2018-07-06  0:55 ` [COFF] " crossd
2018-07-06  5:42   ` bakul
2018-07-09  2:51     ` crossd
2018-07-10  5:41       ` bakul
2018-07-06  4:04 ` grog
2018-07-06 16:10   ` gtaylor
2018-07-06 18:27     ` [COFF] Editor Scripts scj
2018-07-06 19:04       ` gtaylor
2018-07-08 20:50 ` [COFF] Other OSes? perry
2018-07-08 23:27   ` bakul
2018-07-09  0:00     ` grog
2018-07-09  0:13       ` perry
2018-07-09  0:05     ` crossd
2018-07-09  0:56       ` lm
2018-07-09  2:23         ` crossd
2018-07-09  0:11     ` perry
2018-07-09  0:19       ` crossd
2018-07-09  2:00         ` bakul
2018-07-09  3:02           ` [COFF] Origination of awful security design [COFF, COFF] bill
2018-07-09 13:10           ` [COFF] Other OSes? david
2018-07-09 13:17           ` perry
2018-07-09 13:13         ` perry

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=20180709075035.59bf47d0@jabberwock.cb.piermont.com \
    --to=coff@minnie.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).