want shell should I learn 17
On 2006-01-07, Peter T. Breuer Of course it's not. For serious programming, whether scripts or any...
That's what I said was not adequate for writing a program in, since it lack colorization, formatting, bracket matching, etc. Apparently one can do it in a programming editor instead ...
Readline simply is not an editor that is anywhere near the quality f a programming editor - if it were, writing programming editrs would be trivial, and it ain't.
You can do it in a single key, no?
It's the editor that is at issue - and if you have multiple versions des this not indicate that you have multiple failures?
It's not - we are talking about editing programs in this instance, although more generally I am trying to get you to argue about WHY programming should even be a consideration in a command line shell. I see no reason why it should, and since programming is not what the command line is generally used for, you have to justify why it should be considered.
Yu haven't.
There ARE justifications - you just haven't raised any.
I believe that was the point you contested - one edits programs using a programming editor. Not that WP is precisely that. Indeed, I don't see how you could use WP at all since it does its own formatting and line wrap, and the newlines are significant in bourne shell.
You can only have one shell open at a time, or the others history will be overwritten on close (it's complicated to work around that, but I daresay it can be done).
That's okay. It happens to all of us. :-) I guess it's a matter of opinion. In the csh case, parentheses are...
Try "man sh", man "ksh". Look for ways to make the shells identify themselves, something like "sh --version". I havn't used AIX for about ten years, so I just guess they...
That might be one way - but it's not good on a laptop, where one wants to save battery power by not touching disk.
It's a key-binding.
SUre there is - hitting "ZZ" in vi (or whatever binding one has programmed to do that).
Here - for the umpteenth time, the command line shell is the discussion, NOT "programming in bash", or programming anything at all.
I don't - experience has taught me that the idea of always working in the same language is silly. The cool factor of having a command shell that is the same as the language you prgram in is superficial - in practice one wants a command shell that is good as a command shell, not as a proramming language.
OK, I claim that bash is no good as a command shell because the colour of its manual is not nice.
(when you get the idea, wake me up).
Peter
Linux groups from Newsgroups