Re: [psh-dev] additional features

[Markus P. <wa...@sp...>]

On 20.12.2007, at 15:53, Sam Krasnik wrote:

> Hi all,
> Have been using PSH for quite some time now, and figured I'd try to =20=

> give back a little. I have added backticking support with variable =20
> expansion, proper escape character interpretation, fixed some of the =20=

> quoting/unquoting implementation including execution windows (for =20
> example "hello"$world"how are you" didn't work before), and array =20
> expansion (@a should expand to multiple arguments but was treated =20
> like "@a", which is just one) which is useful in .psh scripts via =20
> @ARGV, and a somewhat improved parser. What would be the best way to =20=

> have someone look at these changes to see if they meet whatever =20
> guidelines the PSH god(s?) desire?
>
> There are still some bugs that I haven't gotten around to fixing, =20
> but hope to do so soon (for example, tab completion inside =20
> directories with spaces in the their name doesn't work properly as =20
> well as some strange issues with the recursive glob operator). These =20=

> kind of things get in the way when using PSH all day as my main shell!

Hi Sam

The psh project is pretty dead I fear: psh1 hasn't been changed in =20
years. I had also written a new, more solid and faster version from =20
ground-up called psh2 which has all the basic features of a shell but =20=

most of the comfort features were not added yet. The other developers =20=

are pretty busy, too, with other things, I think. Gregor is mainly =20
working with Parrot now and from the others I have not heard something =20=

for a while.

I wouldn't mind giving you CVS access, if you want to check in your =20
changes to psh1, but maybe Gregor should say something about that, too.

> On a related note, I was wondering is there exists a perl =20
> implemenation of Gnu Readline, since getting a compiled version to =20
> work on a variety of platforms (I am trying to use it on 32-bit =20
> redhat, 64-bit suse and HP) can be a royal pain, since Perl can get =20=

> rather confused, especially between 32-bit and 64-bit (I had to =20
> compile a 32-bit version and use it on both)


Unfortunately not. There's Term::ReadLine::Perl, which psh1 even =20
supports as far as I can remember, which still dates back to some old =20=

Perl4 code. The codebase of that is rather weird so no-one ever =20
extended it with new features. The Zoidberg guys (another perl shell, =20=

don't know how active they are nowadays) also had an attempt at a new =20=

Term::Readline module called Term::ReadLine::Zoid - but I haven't had =20=

a look at it yet and it would probably need some support of psh to be =20=

useful.

--=20
Markus Peter - wa...@sp... - http://www.spin-ag.de/ - =
http://www.spin.de/
SPiN AG, Bischof-von-Henle-Str. 2b, 93051 Regensburg, HRB 6295 =20
Regensburg
Aufsichtsratsvors.: Dr. Christian Kirnberger, Vorst=E4nde: F. Rott, P. =20=

Schmid