9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "André Günther" <Andre.G@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] what features would you like in a shell?
Date: Tue, 31 Mar 2009 18:19:26 +0200	[thread overview]
Message-ID: <4FB4BD86-9112-44B2-A2B2-CFE1CE407D95@gmx.de> (raw)
In-Reply-To: <2047553083.376861238516093038.JavaMail.root@joey.catt.com>

Just Ctrl+F and you have completion for the current dir. I think it's
a pretty easy hack to extend this to /bin

On 31 Mar 2009, at 18:14, rapogue@catt.com wrote:

> I'd love to see tab completion at the command line. If there is a
> way to do it in Plan 9, then I haven't figured it out yet. But then
> I'm a newby to the OS.
>
> ----- Original Message -----
> From: noagbodjivictor <noagbodjivictor@gmail.com>
> To: 9fans@9fans.net
> Sent: Tue, 31 Mar 2009 11:29:44 -0400 (EDT)
> Subject: [9fans] what features would you like in a shell?
>
> hello,
>
> I'm a undergrade CS student doing a project for my introductory
> operating systems class. my team wants to write a simple shell from
> scratch.
>
> one idea we have found so far is the following. the shell will record
> all the programs it has run. whenever a program goes awry and is
> killed by the kernel. the shell will reload it.
>
> what do you think of it?
>
> also, we know there are many many shells out there. and our professor
> would not like us to write from scratch. we wanted because it provides
> much exercise. but we certainly don't know about all the shells out
> there.
>
> so I'm writing to get your opinions. maybe there are thing that people
> implement themselves but want included in the shell itself? or just
> something they want implemented?
>
> thanks a lot in advance for your help.
>
>
>




  reply	other threads:[~2009-03-31 16:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 15:29 noagbodjivictor
2009-03-31 15:47 ` erik quanstrom
2009-03-31 16:10 ` matt
2009-03-31 16:26   ` erik quanstrom
2009-04-01  2:39     ` sqweek
2009-04-01  3:14       ` erik quanstrom
2009-03-31 16:14 ` rapogue
2009-03-31 16:19   ` André Günther [this message]
2009-03-31 16:19   ` erik quanstrom
2009-03-31 16:27     ` erik quanstrom
2009-03-31 16:16 ` noagbodjivictor
2009-03-31 16:47   ` erik quanstrom
2009-03-31 17:03     ` michael block
2009-04-01  9:28   ` matt
2009-04-01  9:43     ` yy
2009-04-01 10:01       ` matt
2009-04-01 12:41         ` hiro
2009-04-01 12:54           ` Martin Neubauer
2009-03-31 16:55 ` J.R. Mauro
2009-03-31 18:28 ` Corey
2009-04-02 18:41 ` John Stalker
2009-04-02 23:20   ` LiteStar numnums
2010-10-03 16:25 C H Forsyth
2010-10-05 19:12 ` erik quanstrom

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=4FB4BD86-9112-44B2-A2B2-CFE1CE407D95@gmx.de \
    --to=andre.g@gmx.de \
    --cc=9fans@9fans.net \
    /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).