unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vladimir Kazanov <vekazanov@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: ert-font-lock
Date: Sun, 19 Nov 2023 09:39:01 +0000	[thread overview]
Message-ID: <CAAs=0-3QoBWJvDejTG5PAOPtK2STZtVKHVEv8QXAbpFmt8oiQQ@mail.gmail.com> (raw)
In-Reply-To: <87a5rbqfs8.fsf@posteo.net>

Hi Philip,

Thank you for taking a look at this!

I've integrated most of the changes but the ones below:

> +  ;; Or would it be possible to define a function that calls `ert-set-test'?

Sure, not a problem. But wouldn't the test implementation on this
level be just a replication of the already existing ert-deftest macro?
And ert-deftest, btw, does use half of cl-lib. Removing cl-incf just
stops making sense.

Admittedly, I don't have a bigger picture on Emacs Lisp idioms and
good practices so I'll just do whatever is suggested.

> +  (user-error "Invalid test comment syntax at line %d. Expected a line to test before the comment line" curline)) ;is this a user error?

Well, I am on the fence about this one. My line of thought was that
submitting invalid test cases is very much a user error, isn't it?

> +    (or
> +     ;; skip empty lines
> +     (eolp)

I like the trick. But on empty lines this would return t instead of
only reporting comment lines.

On Sat, 18 Nov 2023 at 14:47, Philip Kaludercic <philipk@posteo.net> wrote:
>
> Po Lu <luangruo@yahoo.com> writes:
>
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> >> Doesn't this library require ert?  if it does, cl-lib is already
> >> loaded by ert.
> >
> > That's a disappointment, but let's not double the problem.
>
> The problem, as in the usage of cl-lib?  You are probably referring to
> the other thread about using CL in Elisp, right?
>
> >> But if people like cl-incf so much, we could just add incf to subr.el
> >> or something.
> >
> > Fine by me, thanks.  (Don't we have incf elsewhere in core?  Or was it
> > in the old cl.el?)
>
> That is part of cl, and is aliased to cl-incf.
>
> --
> Philip Kaludercic



-- 
Regards,

Vladimir Kazanov



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

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-3QoBWJvDejTG5PAOPtK2STZtVKHVEv8QXAbpFmt8oiQQ@mail.gmail.com' \
    --to=vekazanov@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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).