9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Getting started in Plan9 - help
Date: Mon, 21 Jan 2002 11:58:15 -0800	[thread overview]
Message-ID: <200201211958.g0LJwFY93587@ducky.net> (raw)
In-Reply-To: <20020121184840.6A59C19981@mail.cse.psu.edu>

>> If you put the command history editor in the shell, then you can only
>> use it in the shell; if you use another shell from time to time, then
>
>Not if you put it in a library and link the library
>against every single program that could ever possibly
>want to read input!

Or better yet, put it in rio.  Then every program gets the
feature, and nobody has to remember to use the funny library.

Plus, libraries have some troubles of their own..

* If static libraries, then you have to relink everything
  every time you change the library.

* If dynamic linked libraries, you have taken the first step
  on the slippery slope to the land of gratuitious complexity,
  where even a simple "hello, world" C program can execute
  100000 instructions before it actually prints anything.
  (No, I'm not kidding.)  For some reason, people seem to think
  adding features in dynamic libraries is "free".

Only problem with putting it in rio is that you don't have
quite enough information there.  To do intelligent history
and completion, you really want to know a few things like
what program you're doing it for, what their current directory
is, what their environment variables are, and so on.


  reply	other threads:[~2002-01-21 19:58 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 18:48 Russ Cox
2002-01-21 19:58 ` Mike Haertel [this message]
2002-01-21 20:05   ` James A. Robinson
  -- strict thread matches above, loose matches on Subject: below --
2002-01-24 16:30 Russ Cox
2002-01-24 17:34 ` Thomas Bushnell, BSG
2002-01-23 18:24 Russ Cox
2002-01-24  9:38 ` Thomas Bushnell, BSG
2002-01-22 18:28 David Gordon Hogan
2002-01-23 10:04 ` Douglas A. Gwyn
2002-01-23 18:01   ` Thomas Bushnell, BSG
2002-01-23 18:19     ` Ronald G Minnich
2002-01-23 18:21       ` Scott Schwartz
2002-01-24  9:38       ` Thomas Bushnell, BSG
2002-01-23 18:46     ` Boyd Roberts
2002-01-24  9:38       ` Thomas Bushnell, BSG
2002-01-24 13:01         ` David Arnold
2002-01-24 17:35           ` Thomas Bushnell, BSG
2002-01-24 21:40             ` Dan Cross
2002-01-25 10:00               ` Thomas Bushnell, BSG
2002-01-25 22:56                 ` Dan Cross
2002-01-28 18:26                   ` Boyd Roberts
2002-01-29  9:31                     ` Douglas A. Gwyn
2002-01-24 16:05         ` Boyd Roberts
2002-01-24 17:34           ` Thomas Bushnell, BSG
2002-01-25 10:00     ` Douglas A. Gwyn
2002-01-23 10:48 ` Boyd Roberts
2002-01-23 18:01 ` Thomas Bushnell, BSG
2002-01-22  6:44 okamoto
2002-01-22  2:54 dmr
2002-01-22 11:13 ` Boyd Roberts
2002-01-22 17:39   ` Douglas A. Gwyn
     [not found] <20020121170104.2FABD19A05@mail.cse.psu.edu>
2002-01-21 23:30 ` Andrew Simmons
2002-01-21 22:34 erik quanstrom
2002-01-21 22:15 anothy
2002-01-22  9:53 ` Douglas A. Gwyn
2002-01-21 20:39 Russ Cox
2002-01-21 21:16 ` Matt H
2002-01-21 23:39 ` Quinn Dunkan
2002-01-22 15:36 ` cej
2002-01-22 15:42   ` Matt H
2002-01-22 23:02 ` skipt
2002-01-23 10:05   ` Douglas A. Gwyn
2002-01-23 22:28     ` Lyndon Nerenberg
2002-01-21 20:34 presotto
2002-01-21 20:21 Russ Cox
2002-01-21 20:44 ` Mike Haertel
2002-01-21 19:42 David Gordon Hogan
2002-01-21 20:28 ` Matt H
2002-01-25 10:30   ` Ralph Corderoy
2002-01-21 10:01 Re[2]: " steve.simon
2002-01-21 10:28 ` Boyd Roberts
2002-01-20 21:15 rob pike
2002-01-20 20:02 Roshan James
2002-01-20 21:01 ` Matt H
2002-01-20 22:02   ` Scott Schwartz
2002-01-22  9:54     ` ozan s yigit
2002-01-23 10:05       ` Bakul Shah
2002-01-21 10:22   ` Boyd Roberts
2002-01-21 10:40     ` John Murdie
2002-01-20 21:03 ` William S.
2002-01-20 21:34 ` William Josephson
2002-01-21  6:53 ` cej

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=200201211958.g0LJwFY93587@ducky.net \
    --to=mike@ducky.net \
    --cc=9fans@cse.psu.edu \
    /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).