[nongnu] elpa/typescript-mode f6d28c7a0d 073/222: Remove the fontification hack.

[ELPA Syncer]

branch: elpa/typescript-mode
commit f6d28c7a0df305893ac567cacc755a1db1bcc86c
Author: Louis-Dominique Dubeau <ldd@lddubeau.com>
Commit: Louis-Dominique Dubeau <ldd@lddubeau.com>

    Remove the fontification hack.
    
    Fixes #50.
---
 typescript-mode.el | 18 +-----------------
 1 file changed, 1 insertion(+), 17 deletions(-)

diff --git a/typescript-mode.el b/typescript-mode.el
index 0379c011c5..ed49358fe8 100644
--- a/typescript-mode.el
+++ b/typescript-mode.el
@@ -2487,23 +2487,7 @@ Key bindings:
     (c-setup-paragraph-variables))
 
   (set (make-local-variable 'syntax-begin-function)
-       #'typescript--syntax-begin-function)
-
-  ;; Important to fontify the whole buffer syntactically! If we don't,
-  ;; then we might have regular expression literals that aren't marked
-  ;; as strings, which will screw up parse-partial-sexp, scan-lists,
-  ;; etc. and and produce maddening "unbalanced parenthesis" errors.
-  ;; When we attempt to find the error and scroll to the portion of
-  ;; the buffer containing the problem, JIT-lock will apply the
-  ;; correct syntax to the regular expresion literal and the problem
-  ;; will mysteriously disappear.
-  (font-lock-set-defaults)
-
-  (let (font-lock-keywords)         ; leaves syntactic keywords intact
-    ;; Avoid byte-compilation errors.  `font-lock-fontify-buffer' is
-    ;; marked as interactive only in Emacs 25.
-    (with-no-warnings
-      (font-lock-fontify-buffer))))
+       #'typescript--syntax-begin-function))
 
 ;; Set our custom predicate for flyspell prog mode
 (put 'typescript-mode 'flyspell-mode-predicate