From: Vladimir Kazanov <vekazanov@gmail.com>
To: john muhl <jm@pub.pink>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: ert-font-lock
Date: Thu, 23 Nov 2023 13:00:57 +0000 [thread overview]
Message-ID: <CAAs=0-099RncyJXqqLWF59Z3+VFYsvAY=T37=n43RQXfbGoiVQ@mail.gmail.com> (raw)
In-Reply-To: <87h6lfqbp9.fsf@thelio.lan>
On Tue, 21 Nov 2023 at 17:05, john muhl <jm@pub.pink> wrote:
>
> https://git.sv.gnu.org/cgit/emacs.git/tree/lisp/progmodes/lua-ts-mode.el
>
> Attached are the tests. They fail against master since some bugs
> were found in the process.
>
Got it, thanks!
Your code uses newcomment.el facilities so ert-font-lock.el's comment
detection code should work just fine. Based on your example I've just
added a way to check comment faces as well, i.e. something like the
following should work now :
// comment
// ^ font-lock-comment-face
or
// comment
// <- font-lock-comment-face
This means that single line comments having no (leading "^", or "<-")
should be properly testable now as well. Previously this wouldn't work
as the code assumed all comments to be either assertions, or
non-meaningful lines.
Got to look into the multiline comment case now - you have one early
in the patch.
--
Regards,
Vladimir Kazanov
prev parent reply other threads:[~2023-11-23 13:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 10:43 [ELPA] New package: ert-font-lock Vladimir Kazanov
2023-11-18 11:18 ` Philip Kaludercic
2023-11-18 12:07 ` Po Lu
2023-11-18 12:43 ` Eli Zaretskii
2023-11-18 13:14 ` Po Lu
2023-11-18 14:47 ` Philip Kaludercic
2023-11-18 16:23 ` Eli Zaretskii
2023-11-19 9:39 ` Vladimir Kazanov
2023-11-18 14:18 ` john muhl
2023-11-19 10:02 ` Vladimir Kazanov
2023-11-19 10:08 ` Vladimir Kazanov
2023-11-20 18:27 ` Vladimir Kazanov
2023-11-21 4:45 ` john muhl
2023-11-21 7:43 ` Vladimir Kazanov
2023-11-21 16:51 ` john muhl
2023-11-23 13:00 ` Vladimir Kazanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAs=0-099RncyJXqqLWF59Z3+VFYsvAY=T37=n43RQXfbGoiVQ@mail.gmail.com' \
--to=vekazanov@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jm@pub.pink \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.