[nongnu] elpa/lua-mode 432d9a0 333/468: lua-try-match-multiline-begin: reword the comment

[Philip Kaludercic]

branch: elpa/lua-mode
commit 432d9a033268fbdfef5f65a95ce77e7bba19cdf9
Author: immerrr <immerrr+lua@gmail.com>
Commit: immerrr <immerrr+lua@gmail.com>

    lua-try-match-multiline-begin: reword the comment
---
 lua-mode.el | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/lua-mode.el b/lua-mode.el
index 4db8dd5..614c0ec 100644
--- a/lua-mode.el
+++ b/lua-mode.el
@@ -904,10 +904,20 @@ If none can be found before reaching LIMIT, return nil."
         (and (setq last-search-matched
                    (re-search-forward lua-ml-begin-regexp limit 'noerror))
 
+             ;; Handle triple-hyphen '---[[' situation in which the multiline
+             ;; opener should be skipped.
+             ;;
+             ;; In HYPHEN1-HYPHEN2-BRACKET1-BRACKET2 situation (match-beginning
+             ;; 0) points to HYPHEN1, but if there's another hyphen before
+             ;; HYPHEN1, standard syntax table will only detect comment-start
+             ;; at HYPHEN2.
+             ;;
+             ;; We could check for comment-start at HYPHEN2, but then we'd have
+             ;; to flush syntax-ppss cache to remove the result saying that at
+             ;; HYPHEN2 there's no comment or string, because under some
+             ;; circumstances that would hide the fact that we put a
+             ;; comment-start property at HYPHEN1.
              (or (lua-comment-or-string-start-pos (match-beginning 0))
-                 ;; Handle triple-hyphen '---[[' situation: match-beginning is
-                 ;; BEFORE the second hyphen, but the comment would only starts
-                 ;; AFTER it.
                  (and (eq ?- (char-after (match-beginning 0)))
                       (eq ?- (char-before (match-beginning 0)))))))