Re: Switching from tcsh to bash as an interactive shell
From: Chris F.A. Johnson (cfajohnson_at_gmail.com)
Date: 17 Sep 2004 18:37:27 GMT
On 2004-09-17, P.T. Breuer wrote:
> Chris F.A. Johnson <email@example.com> wrote:
>> ["Followup-To:" header set to comp.unix.shell.]
>> On 2004-09-17, P.T. Breuer wrote:
>> > Tristan Miller <firstname.lastname@example.org> wrote:
>> >> Yes there is, and I stated it in my original post. Because I do my
>> >> scripting in bash, I find myself constantly typing things like "for f in
>> >> *; do foo; done" at the command line. Needless to say this is incorrect
>> > One doesn't type programs on the command line
>> Once certainly does.
> One certainly does not.
>> It is one of the great advantages of a Bourne-type shell that one
>> can type a multiple line command at the prompt, without having to
>> go through the process of committing it to a script.
> Indeed it is - it's called interpreting, and it makes debugging (small
> things) easy. However, that's not the "command line", that's an
> interpreter, and I encourage you to use it.
> Do not do your programming on the command line. Use an interpreter.
>> It is extremely convenient for testing a structure before putting
>> it in a script.
> No, using an interpreter is, not "it" is.
What do you think you are using at the command line if not an
-- Chris F.A. Johnson http://cfaj.freeshell.org/shell =================================================================== My code (if any) in this post is copyright 2004, Chris F.A. Johnson and may be copied under the terms of the GNU General Public License