From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bash question
Date: 30 Oct 2002 13:22:48 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 24
Message-ID: <apomf8$s21$1@nets3.rz.RWTH-Aachen.DE>
References: <3DBEAB08 DOT 765832EA AT junk DOT net> <3DBF05C3 DOT 184F1062 AT junk DOT net>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1035984168 28737 137.226.32.75 (30 Oct 2002 13:22:48 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 30 Oct 2002 13:22:48 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Ian Chapman <ian_chapman AT junk DOT net> wrote:

>     I've corrected my problem.  For some reason it does not like haveing a
> line with

> echo " Start of _inputrc scripe "

> in the _inputrc file, I wonder why?

Because 'echo' is not a valid command in an _inputrc file.

What ever gave you the idea that _inputrc is a shell script in the
first place?  It's a collection of settings for the readline library.

Read up about it under 

	info readline "Command Line Editing" "Readline Init File"

I guess you mixed up _inputrc and _bashrc.  Only the latter of these
is an ordinary shell script, in which you could use the "echo"
command.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.