Re: Writing a "Command Prompt"



> I can't give any technical advice, but you might want to see what you can
> find out about the internals of bsh, csh, tcsh, ksh, etc. in UNIX.

Thanks Micheal, that's a good idea too.

To start with, I mainly want to improve the existing shell, by allowing it
to be much bigger in screen-space, longer buffer history, better copy/paste,
multiple grouped windows and that kind of thing. But, a natural extension
would be to provide additional features accessible by scripting.

Tobin


.



Relevant Pages

  • Re: OT: Lets welcome Apple to the 80s
    ... The problem was that ksh was proprietary, so there were only two shells ... available in the '80s; sh and csh. ... I'm sure you're right - but I didn't come across tcsh until later. ... The only shells that that you were pretty much guaranteed to have access ...
    (rec.autos.sport.f1)
  • Re: csh question: foreach
    ... >>I am a reformed tcsh user. ... Now I use ksh. ... > Point of clarification, csh!= tcsh. ... and uses an extended set of /bin/sh syntax. ...
    (comp.unix.solaris)
  • Re: csh question: foreach
    ... >>I am a reformed tcsh user. ... Now I use ksh. ... > Point of clarification, csh!= tcsh. ... and uses an extended set of /bin/sh syntax. ...
    (comp.unix.shell)
  • Default Debian shell
    ... what is default shell by Debian sarge (bash, ksh, zsh or sh) or (csh or ...
    (comp.os.linux.misc)
  • Re: Oh ! my god ! the mac equivalent cost twice the price
    ... try with bash, sh,csh, tcsh, ksh ...
    (comp.sys.mac.system)