From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Vladimir Kazanov <vekazanov@gmail.com>
Cc: 67621@debbugs.gnu.org
Subject: bug#67621: [PATCH] documentation for ert-font-lock
Date: Mon, 04 Dec 2023 15:02:16 +0100 [thread overview]
Message-ID: <87cyvmt6af.fsf@gmx.de> (raw)
In-Reply-To: <CAAs=0-34soyksjdmiAqCG2UMCYaPApA-H3oCz=5EBjpdWKUjYg@mail.gmail.com> (Vladimir Kazanov's message of "Mon, 4 Dec 2023 13:29:36 +0000")
Vladimir Kazanov <vekazanov@gmail.com> writes:
> Michael,
Hi Vlad,
> Attached is an updated patch.
Almost fine. Except
> @menu
> -* The @code{should} Macro:: A powerful way to express assertions.
> +* The @code{should} Macro:: A powerful way to express assertions.
Please don't change, it is intended. The @code{} clause isn't visible in
the resulting output. Best would be you check the result in info.
> +The @code{ert-font-lock-deftest} and @code{ert-font-lock-deftest-file}
> +macros accept the same keyword parameteres as @code{ert-deftest} i.e.,
^^ typo?
> Thanks,
> Vlad
Best regards, Michael.
next prev parent reply other threads:[~2023-12-04 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 12:19 bug#67621: [PATCH] documentation for ert-font-lock Vladimir Kazanov
2023-12-04 13:01 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-04 13:29 ` Vladimir Kazanov
2023-12-04 14:02 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-04 14:42 ` Vladimir Kazanov
2023-12-04 15:15 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-08 13:47 ` Vladimir Kazanov
2023-12-08 13:56 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 9:29 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87cyvmt6af.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=67621@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=vekazanov@gmail.com \
/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.