mode errors ...
Emilie Vanvyve <[email protected]>
| Newsgroups | gmane.emacs.xemacs.general |
|---|---|
| Message-ID | <[email protected]> |
Hello !
I wrote last week about a problem to fontify my shell scripts with the
right mode (prog-mode that I didn't have) and if possible
automatically. I received some answers that helped me, but I'm still in
troubles with the "next step" now : I can still not execute the
prog-modes (M-x prog-modes nor fontify my files).
I have two kind of errors :
- either "File mode specification error: (error "sh-mode")" when I open
a file and when XEmacs tries alone to find the right mode to use ;
- either "File mode specification error: (void-variable
allow-remote-paths)" when I open a file and manually force XEmacs to
fontify it (command : menu Options/Syntax Highlighting/In this buffer).
What can I do ? I saw in the mails list that I'm not the only one to
have got this error with allow-remote-path, but I haven't really found
any answer (and as I don't understand a lot about the "elisp", "efs",
it is still less easy ...).
Thanks in advance to anyone who will answer me !
Emilie
MORE DETAILS :
I now have "physically" the prog-modes, in the rigth directory
(/usr/lib/xemacs/xemacs-packages/lisp/prog-modes/), so XEmacs should be
able to recognize it and use it. I have in my init.el file :
(setq frame-title-format "%S: %f")
(setq initial-frame-plist '(top 1 left 0 width 80 height 55))
(setq minibuffer-max-depth nil)
(setq efs-use-passive-mode t)
(setq interpreter-mode-alist
(append '(("^#!.*csh" . sh-mode)
("^#!.*sh\\b" . sh-mode))
interpreter-mode-alist))
(setq ksh-mode-hook
(function (lambda ()
(font-lock-mode 1) ;; font-lock the buffer
(setq ksh-indent 2)
(setq ksh-group-offset -8)
(setq ksh-brace-offset -8)
(setq ksh-tab-always-indent t)
(setq ksh-match-and-tell t)
(setq ksh-align-to-keyword t) ;; Turn on keyword
alignment
)))
I tried also in the init.el file this line :
(setq load-path (cons (expand-file-name
"/usr/lib/xemacs/xemacs-packages/lisp/") load-path))
But it changed nothing and I got the same errors.