[SOLVED] source bashrc -> syntax error: unexpected end of file

ozanbaba · 12-22-2010, 09:16 AM

Ridiculously wild recommendation

Code:

if [ -f /home/xri/personal/somedata.kdb.lock ]; then
rm /home/xri/personal/somedata.kdb.lock;
fi

catkin · 12-22-2010, 09:19 AM

And check whether typeset -F lists any function names that could be affecting the if-fi code.

Ramurd · 12-22-2010, 09:46 AM

Just checked out; the "if" command can be overruled by an alias. In order of execution (correct me if I'm wrong) comes:
- alias
- shell functions
- binaries in order as they appear in the path, unless a direct full pathname is given.

Check if one of your aliases is named "if" :

Code:

alias | grep if

I reckon this would cause unexpected EOFs

Keith Hedger · 12-22-2010, 11:58 AM

Aliasing if certainly causes lots of syntax errors but doesn't seem to cause EOF errors, have you tried just moving the files aside and recreating them from scratch?

xri · 12-26-2010, 10:52 AM

Sorry for the delay to answer to the last posts (this is getting very interesting/educational for me). I've been spending Christmas time with the family, away from my box.
I will use your latest suggestions on my rig today, and I'll post again.

xri · 12-27-2010, 11:05 PM

1)

Quote:

unalias -a

After which, source .bashrc keeps producing the same error message.

2)

Quote:

typeset -F

Does not show anything coinciding with the if statements

3)

Quote:

alias | grep if

does not return any hit. HOWEVER...

Quote:

alias | grep fi

produces alias fi='find . -iname', which coincides with the fi part of the last line of the if statement.

I replaced that line and everything returned to normal.

In short, brilliant and timely suggestions led me to a solution of this. They also led me to read some necessary material to better understand the problem. For all this I'm grateful to you guys.

catkin · 12-28-2010, 05:43 AM

Great that you solved it at last but I do not understand why unalias -a did not fix the problem if it was caused by a fi alias -- unless the fi alias was defined by the $PROMPT_COMMAND value ... ?

mRgOBLIN · 12-28-2010, 07:23 PM

the .bashrc was likely setting the alias again =)

catkin · 12-28-2010, 09:03 PM

Thanks mRgOBLIN

That would explain it -- not directly but via /etc/bashrc according to post #3. .bash_logout would have been OK after unalias -a

Ramurd · 12-29-2010, 06:56 AM

:-) great you got it solved! Now: remember to never ever use any shell keyword as an alias :-D Unless you intentionally want to break it's functionality.
Should've thought that one up: indeed "if" would not cause the unexpected EOF, but an if that never gets closed would... hence "fi" was indeed ever the most logical reason.

xri · 01-12-2011, 12:36 PM

This thread will be among my favorites on my scrapbook. Quite educational