From: Vladimir Kazanov <vekazanov@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, brownts@troybrown.dev
Subject: Re: ert-font-lock improvements
Date: Thu, 21 Mar 2024 15:09:48 +0000 [thread overview]
Message-ID: <CAAs=0-3p2zp-KJKw2+WyjYyDGUEujbppGMWBg7MRJK7qQ_WX9Q@mail.gmail.com> (raw)
In-Reply-To: <86zfur24yy.fsf@gnu.org>
Got it, sorry for distracting.
Also, having that merged, I have something like an emacs-devel-wide
announcement of the tool in mind, looking for builtin major modes that
would benefit from having more syntax highlighting tests. That is, I
would provide the initial sets of tests myself. What do you think?
Thank you for you work
On Thu, 21 Mar 2024 at 11:34, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Vladimir Kazanov <vekazanov@gmail.com>
> > Date: Thu, 21 Mar 2024 08:49:56 +0000
> >
> > Hi all,
> >
> > Some time ago an extension for ERT (the built-in unit testing system)
> > was merged: ert-font-lock, a tool for syntax highlighting tests.
> >
> > A couple of weeks ago certain problems (see bug#69714) with
> > ert-font-lcok were raised, and I've also accumulated a few
> > quality-of-life improvements for the tool.
> >
> > Could somebody please take a look at the patch and merge it if it's
> > okay? Bug author and myself did some testing and the changes proposed
> > do solve a lot of problems for us.
>
> Don't worry, it is in my queue.
>
> (You've posted the patch less than a week ago, so it's too early to
> worry about it.)
--
Regards,
Vladimir Kazanov
next prev parent reply other threads:[~2024-03-21 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 8:49 ert-font-lock improvements Vladimir Kazanov
2024-03-21 11:34 ` Eli Zaretskii
2024-03-21 15:09 ` Vladimir Kazanov [this message]
2024-03-21 17:00 ` Eli Zaretskii
2024-03-21 16:22 ` John ff
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-3p2zp-KJKw2+WyjYyDGUEujbppGMWBg7MRJK7qQ_WX9Q@mail.gmail.com' \
--to=vekazanov@gmail.com \
--cc=brownts@troybrown.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.