unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vladimir Kazanov <vekazanov@gmail.com>
To: jm@pub.pink
Cc: Eli Zaretskii <eliz@gnu.org>, Po Lu <luangruo@yahoo.com>,
	philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: ert-font-lock
Date: Sun, 19 Nov 2023 10:02:09 +0000	[thread overview]
Message-ID: <CAAs=0-0w3gEN7taXXCNob8cXQJfHir4rtqf1-nQH3bL-_apujw@mail.gmail.com> (raw)
In-Reply-To: <87wmufunoz.fsf@thelio.lan>

> faceup.el is already included and seems to provide similar
> functionality. Vladimir could you provide a comparison between
> your package and faceup?

Sure!

I use Anders' set of tools intensively but faceup.el is not exactly
what I was looking for. Let me explain.

faceup.el dumps the current state of highlighting into a separate file
and makes it possible to report any differences. This makes it
possible to "freeze" some state and then make sure nothing happens in
the bigger picture. It provides a relatively developed markup language
that surfaces most of the highlighting features of Emacs. The library
is about 700 LOC excluding the header.

So to me faceup.el is a way to save and check full snapshots of syntax
highlighting. This is an *extremely* useful tool for tweaking an
already existing complicated highlighting system.

ert-font-lock.el is the simpler of the two (maybe 200 LOC). It
introduces a way to non-intrusively say something: "check that the
face above is right", and that's about it. The other benefit is that
it's modelled on Tree-sitter unit tests which makes porting already
existing TS grammar highlighting unit tests trivial.

So instead of snapshot-oriented testing this becomes closer to the
original idea of unit tests: adding small tests incrementally.

-- 
Regards,

Vladimir Kazanov



  reply	other threads:[~2023-11-19 10:02 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 [this message]
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

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAs=0-0w3gEN7taXXCNob8cXQJfHir4rtqf1-nQH3bL-_apujw@mail.gmail.com' \
    --to=vekazanov@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jm@pub.pink \
    --cc=luangruo@yahoo.com \
    --cc=philipk@posteo.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).