Issue resolved:
The 'culprit file' was .bash_aliases. It had the naughty (ASCII for the octal string Bash was detecting and returning an error about). I cleaned it up in Pico (see my post to the thread on favorite editors if you want background on why I use Pico/Nano), re-sourced it via .bash_profile, then .bashrc, and everything seems OK. I quit out of my external {yeah, but not really} RXVT and launched it again and the error was gone.
Fingers crossed it stays gone for good.
BZT
Original post text follows.
Quote:
I don't know for sure what I did, but this morning after making a few changes with my title bar and prompt, as soon as I launch my Cygwin RXVT terminal outside of X-Windows, or my urxvt terminal Inside it, I get the following error:
Code:
bash: $'\357\273\277#': command not found
I've seen it on one line, two lines and three. I thought at first it was a UTF-8 with BOM issue, but it doesn't appear to be so. This last launch brought it up after my motd (which I puzzled out has to be "cat"-ed in since there was no other way I could find to show it that worked) and my Quote Of The Day, for which I use the "toy" application fortune to read in from a fortune-cookie file of my own making. To help you visualize this, here's the rest of my startup messages:
Code:
XWindow Server RESURGAM
BASH cygwin in Windows XP SP3
(Amazing, 'ent it?)
Quote of the day:
Feargail says 'hi.'
I thought this octal-string error may also have been caused by a faulty RXVT, so I ran the setup and re-installed it. Likewise BASH. Just off the top of my head, I'm thinking it may be a corrupt config file that Cygwin's bash is having trouble reading in (parsing) correctly. I've already checked the line endings on everything that rates as a config file and vaguely resembles a bash shell script, and I was able to see and fix a few naughty characters in .bash_profile and .xinitrc. If it is a corrupt startup config file, the question is: which one?
How would I go about finding out which of the files is either bad or refuses to be corrected via editing?
BZT
|
More UNIX and Linux Forum Topics You Might Find Helpful
Powered by 
05-08-2009
Help needed tracing source of bash error
Linear Mode
