I now have both 21.4.13 and 21.4.18 installed on the same box, with the
same load-path values. I can see that this might cause me some problems
down the road, but it makes it real easy to compare the two. The key to
this problem appears to be the interpreter-mode-alist value. On
21.4.13, the default value for this has lots of content, covering
numerous shell script languages. On 21.4.18, this only has "emacs".
-----Original Message-----
From: Adrian Aichner [mailto:adrian@xemacs.org]
Sent: Tuesday, December 13, 2005 12:27 PM
To: Karr, David
Cc: XEmacs Beta
Subject: Re: 21.4.18: How Xemacs can figure out to go into
shell-script-mode?
"Karr, David" <david.karr(a)wamu.net> writes:
I have Cygwin/Xemacs 21.4.13 installed on one box. I'm now
installing
21.4.18 on another box. I noticed that when I edit a bash script in
21.4.13, it knows to go into shell-script-mode. When I edit the same
script in 21.4.18, it doesn't do that. I have to go into
shell-script-mode manually. The script does not have an extent. I
assume it would figure this out by the "#! ..." line. Why might this
not be working in 21.4.18?
Hi David,
just a quick guess from my memory:
Do you have
sh-script/executable.el
on both systems?
I also have these in my site-start.el, but haven't needed to test these
for years:
(setq interpreter-mode-alist
(cons '("^#!.*/csh\\b" . csh-sh-mode) interpreter-mode-alist))
(setq interpreter-mode-alist
(cons '("^#!.*/ksh\\b" . ksh-sh-mode) interpreter-mode-alist))
(setq interpreter-mode-alist
(cons '("^#!.*/sh\\b" . sh-sh-mode) interpreter-mode-alist))
Good Luck,
Adrian
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/