Re: Weird behaviour of bash

[Patrick R. Wade]

On Fri, May 12, 2000 at 04:53:29PM -0700, Seth Cohn wrote:
>
>
>>[solovay@localhost]$ ./opera
>>./opera: Command not found.
>
>Note, it's NOT saying that opera is not found, it's saying that Command not
>found.
>
>I've seen with perl scripts that point to /someplace/perl/isn't instead of
>/usr/bin/perl (or whatever) on the first line.
>
>Something's flaky with that opera file.

Long shot; try:

[solovay@localhost]$ strings oper<TAB> 

i want to use the tab-completion, just to be sure bash is successfully finding
the opera executable.  Perhaps the strings will show us something like that
/flaky/perl/path problem Seth mentions.

-- 
 UN-altered REPRODUCTION and DISSEMINATION of this 
          IMPORTANT Information is ENCOURAGED, ESPECIALLY to COMPUTER 
          BULLETIN BOARDS.