From c929532b4694a1c5d0f61ae77f4e8664706a36a1 Mon Sep 17 00:00:00 2001 From: "Basil L. Contovounesios" Date: Sat, 20 Apr 2024 16:01:49 +0200 Subject: [PATCH] Remove ert-equal-including-properties from manual * doc/misc/ert.texi (Useful Techniques): Mention only equal-including-properties in place of the now obsolete ert-equal-including-properties. --- doc/misc/ert.texi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/misc/ert.texi b/doc/misc/ert.texi index e10b8e3a7b4..74d8a29691d 100644 --- a/doc/misc/ert.texi +++ b/doc/misc/ert.texi @@ -766,7 +766,6 @@ Here's a more complicated test: @end lisp @findex make-ert-test -@findex ert-equal-including-properties This test creates a test object using @code{make-ert-test} whose body will immediately signal failure. It then runs that test and asserts that it fails. Then, it creates a temporary buffer and invokes @@ -775,7 +774,7 @@ to the current buffer. Finally, it extracts the first line from the buffer and asserts that it matches what we expect. It uses @code{buffer-substring-no-properties} and @code{equal} to ignore text properties; for a test that takes properties into account, -@code{buffer-substring} and @code{ert-equal-including-properties} +@code{buffer-substring} and @code{equal-including-properties} could be used instead. The reason why this test only checks the first line of the backtrace