Computer Old Farts Forum
 help / color / mirror / Atom feed
From: perry at piermont.com (Perry E. Metzger)
Subject: [COFF] Other OSes?
Date: Sun, 8 Jul 2018 16:50:06 -0400	[thread overview]
Message-ID: <20180708165006.21a7429e@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <20180705055650.GA2170@minnie.tuhs.org>

On Thu, 5 Jul 2018 15:56:50 +1000 Warren Toomey <wkt at tuhs.org> wrote:
> OK, I guess I'll be the one to start things going on the COFF list.
> 
> What other features, ideas etc. were available in other operating
> systems which Unix should have picked up but didn't?
> 
> [ Yes, I know, it's on-topic for TUHS but I doubt it will be for
> long! ]

A minor feature that I might mention: TOPS-20 CMND JSYS style command
completion. TL;DR, this feature could now be implemented, as after
decades of wanting it I finally know how to do it in a unixy way.

In TOPS-20, any time you were at the EXEC (the equivalent of the
shell), you could hit "?" and the thing would tell you what options
there were for the next thing you could type, and you could hit ESC to
complete the current thing. This was Very Very Nice, as flags and
options to programs were all easily discoverable and you had a handy
reminder mechanism when you forgot what you wanted.

bash has some vague lame equivalents of this (it will complete
filenames if you hit tab etc.), and if you write special scripts you
can add domain knowledge into bash of particular programs to allow for
special application-specific completion, but overall it's kind of lame.

Here's the Correct Way to implement this: have programs implement a
special flag that allows them to tell the shell how to do completion
for them! I got this idea from this feature being hacked in, in an ad
hoc way, into clang:

http://blog.llvm.org/2017/09/clang-bash-better-auto-completion-is.html

but it is apparent that with a bit of work, one could standardize such
a feature and allow nearly any program to provide the shell with such
information, which would be very cool. Best of all, it's still unixy
in spirit (IMHO).

Kudos to the LLVM people for figuring out the right way to do
this. I'd been noodling on it since maybe 1984 without any real
success.

Perry
-- 
Perry E. Metzger		perry at piermont.com


  parent reply	other threads:[~2018-07-08 20: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
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 ` perry [this message]
2018-07-08 23:27   ` [COFF] Other OSes? 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=20180708165006.21a7429e@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).