CVS update by didierv packages/xemacs-packages/sh-script ...
xemacs-cvs at xemacs.org
xemacs-cvs at xemacs.org
Tue Feb 6 10:26:30 EST 2007
User: didierv
Date: 07/02/06 16:26:30
Modified: packages/xemacs-packages/sh-script ChangeLog sh-script.el
Log:
Fix sh-mode function: derive from a real mode
Revision Changes Path
1.26 +9 -5 XEmacs/packages/xemacs-packages/sh-script/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/sh-script/ChangeLog,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -p -r1.25 -r1.26
--- ChangeLog 2005/10/18 14:59:49 1.25
+++ ChangeLog 2007/02/06 15:26:29 1.26
@@ -1,3 +1,8 @@
+2007-02-06 Didier Verna <didier at xemacs.org>
+
+ * sh-script.el (sh-mode): Derive from a real mode
+ (fundamental-mode), not from nil.
+
2005-10-18 Norbert Koch <viteno at xemacs.org>
* Makefile (VERSION): XEmacs package 1.21 released.
@@ -22,7 +27,7 @@
2005-10-12 Jérôme Marant <jmarant at free.fr>
* sh-script.el: Sync with GNU Emacs 21.4
- Update FSF's address in GPL notices.
+ Update FSF's address in GPL notices.
(sh-mode-map): Move menu-related code to sh-mode-menu.
(sh-mode-menu): New menu definition.
(sh-mode): Install menu.
@@ -80,7 +85,7 @@
2002-03-02 Jeff Miller <jmiller at cablespeed.com>
* executable.el: missing autoload cookie.
-
+
2000-07-11 Jose Romildo Malaquias <romildo at urano.iceb.ufop.br>
* sh-script.el: Synch with FSF 20.7.
@@ -93,8 +98,8 @@
1999-05-31 Andy Piper <andyp at parallax.co.uk>
* sh-script.el (sh-set-shell): don't include the extension in
- sh-shell name. This is almost never the right thing and breaks
- font-lock.
+ sh-shell name. This is almost never the right thing and breaks
+ font-lock.
1998-05-12 Andy Piper <andyp at parallax.co.uk>
@@ -124,4 +129,3 @@
problems.
* Makefile: Created.
-
1.10 +25 -25 XEmacs/packages/xemacs-packages/sh-script/sh-script.el
Index: sh-script.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/sh-script/sh-script.el,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- sh-script.el 2005/10/15 15:41:59 1.9
+++ sh-script.el 2007/02/06 15:26:29 1.10
@@ -42,7 +42,7 @@
;; syntactically distinguishing those from `'' strings.
;; Indentation
-;; ===========
+;; ===========
;; Indentation for rc and es modes is very limited, but for Bourne shells
;; and its derivatives it is quite customizable.
;;
@@ -61,12 +61,12 @@
;; By changing this one variable you can increase or decrease how much
;; indentation there is. Valid symbols:
;;
-;; + Indent right by sh-basic-offset
-;; - Indent left by sh-basic-offset
-;; ++ Indent right twice sh-basic-offset
-;; -- Indent left twice sh-basic-offset
-;; * Indent right half sh-basic-offset
-;; / Indent left half sh-basic-offset.
+;; + Indent right by sh-basic-offset
+;; - Indent left by sh-basic-offset
+;; ++ Indent right twice sh-basic-offset
+;; -- Indent left twice sh-basic-offset
+;; * Indent right half sh-basic-offset
+;; / Indent left half sh-basic-offset.
;;
;; There are 4 commands to help set the indentation variables:
;;
@@ -109,8 +109,8 @@
;; `sh-learn-buffer-indent' on a small region of the buffer should
;; suffice.
;;
-;; Saving indentation values
-;; -------------------------
+;; Saving indentation values
+;; -------------------------
;; After you've learned the values in a buffer, how to you remember
;; them? Originally I had hoped that `sh-learn-buffer-indent'
;; would make this unnecessary; simply learn the values when you visit
@@ -126,15 +126,15 @@
;; to reload them in another buffer or at another point in time.
;;
;; Use `sh-name-style' to give a name to the indentation settings of
-;; the current buffer.
+;; the current buffer.
;; Use `sh-load-style' to load indentation settings for the current
-;; buffer from a specific style.
+;; buffer from a specific style.
;; Use `sh-save-styles-to-buffer' to write all the styles to a buffer
-;; in lisp code. You can then store it in a file and later use
-;; `load-file' to load it.
+;; in lisp code. You can then store it in a file and later use
+;; `load-file' to load it.
;;
-;; Indentation variables - buffer local or global?
-;; ----------------------------------------------
+;; Indentation variables - buffer local or global?
+;; ----------------------------------------------
;; I think that often having them buffer-local makes sense,
;; especially if one is using `sh-learn-buffer-indent'. However, if
;; a user sets values using customization, these changes won't appear
@@ -152,8 +152,8 @@
;;
;; This may be awkward, but the intent is to cover all cases.
;;
-;; Awkward things, pitfalls
-;; ------------------------
+;; Awkward things, pitfalls
+;; ------------------------
;; Indentation for a sh script is complicated for a number of reasons:
;;
;; 1. You can't format by simply looking at symbols, you need to look
@@ -178,8 +178,8 @@
;; status. This is for cases where the buffer started read-only buffer
;; but the user issued `toggle-read-only'.
;;
-;; Bugs
-;; ----
+;; Bugs
+;; ----
;; - Indenting many lines is slow. It currently does each line
;; independently, rather than saving state information.
;;
@@ -309,7 +309,7 @@ sh Bourne Shell
(ksh . pdksh)))
;; for the time being
'((ksh . ksh88)
- (bash2 . bash)
+ (bash2 . bash)
(sh5 . sh)))
"*Alist for transforming shell names to what they really are.
Use this where the name of the executable doesn't correspond to the type of
@@ -1233,7 +1233,7 @@ frequently editing existing scripts with
(put 'sh-mode 'mode-class 'special)
;;;###autoload
-(define-derived-mode sh-mode nil "Shell-script"
+(define-derived-mode sh-mode fundamental-mode "Shell-script"
"Major mode for editing shell scripts.
This mode works for many shells, since they all have roughly the same syntax,
as far as commands, arguments, variables, pipes, comments etc. are concerned.
@@ -2011,7 +2011,7 @@ STRING This is ignored for the purp
(skip-chars-forward " \t")
(setq this-kw (sh-get-kw)))
- ;; Handle "this" keyword: first word on the line we're
+ ;; Handle "this" keyword: first word on the line we're
;; calculating indentation info for.
(if this-kw
(if (setq val (sh-check-rule 1 this-kw))
@@ -2736,9 +2736,9 @@ so that `occur-next' and `occur-prev' wi
;; (goto-char (point-max))
;; (insert "(setq\n")
;; (while p
-;; (insert (format " %s %s \n"
-;; (nth 0 (car p)) (nth 1 (car p))))
-;; (setq p (cdr p)))
+;; (insert (format " %s %s \n"
+;; (nth 0 (car p)) (nth 1 (car p))))
+;; (setq p (cdr p)))
;; (insert ")\n")
;; )))
;;
More information about the XEmacs-CVS
mailing list