comparison lisp/textmodes/tex-mode.el @ 57698:5e84f3fe94f0

(tex-font-lock-keywords-1): Fix up the spurious verbatim face on the \ of \end{verbatim}.

57697:64443697a546

	   ;; This would allow highlighting \newcommand\CMD but requires
	   ;; adapting subgroup numbers below.
	   ;; (arg "\\(?:{\\(\\(?:[^{}\\]+\\|\\\\.\\|{[^}]*}\\)+\\)\\|\\\\[a-z*]+\\)"))
	   (arg "{\\(\\(?:[^{}\\]+\\|\\\\.\\|{[^}]*}\\)+\\)"))
      (list
       ;; display $$ math $$
       ;; We only mark the match between $$ and $$ because the $$ delimiters
       ;; themselves have already been marked (along with $..$) by syntactic
       ;; fontification.  Also this is done at the very beginning so as to
       ;; interact with the other keywords in the same way as $...$ does.

      ;; 1 - it's wrong if the verbatim env is empty (the same \n is used to
      ;;     start and end the fenced-string).
      ;; 2 - font-lock considers the preceding \n as being part of the
      ;;     preceding line, so things gets screwed every time the previous
      ;;     line is re-font-locked on its own.
      (,(concat "^\\(\\\\\\)end *{" verbs "}\\(.?\\)") (1 "|") (3 "<"))
      ;; ("^\\(\\\\\\)begin *{comment}" 1 "< b")
      ;; ("^\\\\end *{comment}.*\\(\n\\)" 1 "> b")
      ("\\\\verb\\**\\([^a-z@*]\\)" 1 "\""))))

57698:5e84f3fe94f0

	   ;; This would allow highlighting \newcommand\CMD but requires
	   ;; adapting subgroup numbers below.
	   ;; (arg "\\(?:{\\(\\(?:[^{}\\]+\\|\\\\.\\|{[^}]*}\\)+\\)\\|\\\\[a-z*]+\\)"))
	   (arg "{\\(\\(?:[^{}\\]+\\|\\\\.\\|{[^}]*}\\)+\\)"))
      (list
       ;; font-lock-syntactic-keywords causes the \ of \end{verbatim} to be
       ;; highlighted as tex-verbatim-face.  Let's undo that.
       ;; This is ugly and brittle :-(  --Stef
       '("^\\(\\\\\\)end" (1 (get-text-property (match-end 1) 'face) t))
       ;; display $$ math $$
       ;; We only mark the match between $$ and $$ because the $$ delimiters
       ;; themselves have already been marked (along with $..$) by syntactic
       ;; fontification.  Also this is done at the very beginning so as to
       ;; interact with the other keywords in the same way as $...$ does.

      ;; 1 - it's wrong if the verbatim env is empty (the same \n is used to
      ;;     start and end the fenced-string).
      ;; 2 - font-lock considers the preceding \n as being part of the
      ;;     preceding line, so things gets screwed every time the previous
      ;;     line is re-font-locked on its own.
      ;; There's a hack in tex-font-lock-keywords-1 to remove the verbatim
      ;; face from the \ but C-M-f still jumps to the wrong spot :-(  --Stef
      (,(concat "^\\(\\\\\\)end *{" verbs "}\\(.?\\)") (1 "|") (3 "<"))
      ;; ("^\\(\\\\\\)begin *{comment}" 1 "< b")
      ;; ("^\\\\end *{comment}.*\\(\n\\)" 1 "> b")
      ("\\\\verb\\**\\([^a-z@*]\\)" 1 "\""))))