Hi Bakunin,

I am using csh and tcsh too. Could you please tell me that how ksh for vi command line edit mode is reliable, stable job control and is great programming language.

Thank you.

and sometimes tcsh

Hi TLogine,

I said, *my* reasons for preferring the Korn shell are:

1) a stable job control: it is reliable (and predictable) to create, handle and remove daughter processes (unlike in csh, IMHO), there is a coprocess facility (which the csh lacks);

2) a grat programming language: Korn shell has a very good, versatile and elegant programming (script) language built in, which I find in every respect better than the csh scripting language.

3) the vi cmdline editing mode: in Korn shell it is possible to switch to a vi-like way of dealing with the command history and repeat/modify commands. I like this behaviour much better than the (again: IMHO) rather clumsy "!" and "!!", ... the csh features.

If you feel better with the csh (or any other shell): great, I have no problems with that. Still, I would like to point out, that I would greatly appreciate you having equally no problems with *my* decision about *my* working environments. Thanks.

bakunin

Hi Bakunin,

Thanks for your reply. I just asked that questions for knowledge sharing only not for argument!
Please share your technical knowledge with us!

Thank you.

Funny, I use bash for almost exactly the same reasons a lot of people here use ksh. I like being able to quickly switch between emacs and vi-style modes (I use emacs for everyday stuff and vi for editing big multiline stuctures). Bash also has some really nice expansion features like being able to say "mkdir directory{0..9}" and create ten directories.

I'm sure all of what I'm describing can also be done easily with ksh as well -- it's just a matter of what syntax I'm comfy with.

Bash gets it done

Only bash......