comparison lisp/progmodes/sh-script.el @ 81462:8de1bb9519fe

(sh-font-lock-paren): Mark the relevant text with font-lock-multiline.

81461:e9cd7fd7a63b

;; To try and address points 2 3 and 5 I used a feature that cperl mode
;; uses, that of a text's syntax property.  This, however, has 2
;; disadvantages:
;; 1. We need to scan the buffer to find which ")" symbols belong to a
;;    case alternative, to find any here documents, and handle "$#".
;; 2. Setting the text property makes the buffer modified.  If the
;;    buffer is read-only buffer we have to cheat and bypass the read-only
;;    status.  This is for cases where the buffer started read-only buffer
;;    but the user issued `toggle-read-only'.
;;
;; 	Bugs
;; 	----
;; - Indenting many lines is slow.  It currently does each line
;;   independently, rather than saving state information.
;;
;; - `sh-learn-buffer-indent' is extremely slow.
;;
;; Richard Sharman <[e-mail]>  June 1999.

;;; Code:

                   ;; Maybe we've bumped into an escaped newline.
                   (sh-is-quoted-p (point)))
            (backward-char 1))
	  (when (eq (char-before) ?|)
	    (backward-char 1) t)))
    (when (save-excursion (backward-char 2) (looking-at ";;\\|in"))
      sh-st-punc)))

(defun sh-font-lock-backslash-quote ()
  (if (eq (save-excursion (nth 3 (syntax-ppss (match-beginning 0)))) ?\')
      ;; In a '...' the backslash is not escaping.

81462:8de1bb9519fe

;; To try and address points 2 3 and 5 I used a feature that cperl mode
;; uses, that of a text's syntax property.  This, however, has 2
;; disadvantages:
;; 1. We need to scan the buffer to find which ")" symbols belong to a
;;    case alternative, to find any here documents, and handle "$#".
;;
;; 	Bugs
;; 	----
;; - Indenting many lines is slow.  It currently does each line
;;   independently, rather than saving state information.
;;
;; - `sh-learn-buffer-indent' is extremely slow.
;;
;; - "case $x in y) echo ;; esac)" the last ) is mis-identified as being
;;   part of a case-pattern.  You need to add a semi-colon after "esac" to
;;   coerce sh-script into doing the right thing.
;;
;; - "echo $z in ps | head)" the last ) is mis-identified as being part of
;;   a case-pattern.  You need to put the "in" between quotes to coerce
;;   sh-script into doing the right thing.
;;
;; - A line starting with "}>foo" is not indented like "} >foo".
;;
;; Richard Sharman <[e-mail]>  June 1999.

;;; Code:

                   ;; Maybe we've bumped into an escaped newline.
                   (sh-is-quoted-p (point)))
            (backward-char 1))
	  (when (eq (char-before) ?|)
	    (backward-char 1) t)))
    ;; FIXME: ";; esac )" is a case that looks like a case-pattern but it's
    ;; really just a close paren after a case statement.  I.e. if we skipped
    ;; over `esac' just now, we're not looking at a case-pattern.
    (when (progn (backward-char 2)
                 (if (> start (line-end-position))
                     (put-text-property (point) (1+ start)
                                        'font-lock-multiline t))
                 ;; FIXME: The `in' may just be a random argument to
                 ;; a normal command rather than the real `in' keyword.
                 ;; I.e. we should look back to try and find the
                 ;; corresponding `case'.
                 (looking-at ";;\\|in"))
      sh-st-punc)))

(defun sh-font-lock-backslash-quote ()
  (if (eq (save-excursion (nth 3 (syntax-ppss (match-beginning 0)))) ?\')
      ;; In a '...' the backslash is not escaping.