Hide Forgot
RedHat has chosen to call the bash2 the new bash v2.x (to reduce downwards compatibility problems?) thus introducing some little problem here and there :-) One of this is the "fontify"-cation of shell files in xemacs, which results in all sort of strange errors (no file is opened at all, if fontifycation is by default!). The reason seems to be that the elisp code looks at the SHELL env variable to determine the correct fontifycation style, and bash2 is not considered as a correct shell. Suggestion: export SHELL=/bin/bash, but even better: why not throwing away the old bash and using the v2.x? Massimo
We would love to throw away the old bash and just use the new, but at the time there were (and still are) issues with old bash scripts not working with bash2. Just out of curiosity, when you do this "SHELL=/bin/bash" is the problem fixed? Tim
Changing $SHELL to "/bin/bash" works. Since it's such a simple problem, xemacs is ready for the fix. :) In xemacs, Menuitem Options->Customize->Emacs->Programming->Languages->Sh->Ancestor Alist Click on the [INS] at the end and fill in ------ [INS] [DEL] Cons-cell: Symbol: bash2 Symbol: bash ------ Patch to follow.
Created attachment 38 [details] Patch to work-around the problem
apply the patch to xemacs