bug#59028: closed ([PATCH] Rewrite the `kill-buffer-delete-auto-save' tests)

[GNU bug Tracking System]

Your message dated Wed, 16 Nov 2022 10:54:27 -0800
with message-id <87o7t6687w.fsf@rfc20.org>
and subject line Re: bug#59028: [PATCH] Rewrite the 
`kill-buffer-delete-auto-save' tests
has caused the debbugs.gnu.org bug report #59028,
regarding [PATCH] Rewrite the `kill-buffer-delete-auto-save' tests
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
59028: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59028
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [PATCH] Rewrite the `kill-buffer-delete-auto-save' tests Date: Fri, 04 Nov 2022 15:53:05 -0700

Tags: patch

Rationale is in the commit description, but it boils down to these tests
being annoying for me recently.  I like to M-x eval-buffer and run tests
interactively, but these tests seemed to work nicely only in batch mode.
In interactive mode they would both fail and issue annoying prompts
"save this modified buffer?" prompts.  In fixing them, I figured out
what they were trying to test and attempted to make that more robust and
clear.

0003-Rewrite-the-kill-buffer-delete-auto-save-tests.patch
Description: Text Data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#59028: [PATCH] Rewrite the `kill-buffer-delete-auto-save' tests
>
>
>
>
> Date: 
>
> Wed, 16 Nov 2022 10:54:27 -0800
>
>
>
>
> Stefan Kangas <stefankangas@gmail.com> writes:
>
> > Matt Armstrong <matt@rfc20.org> writes:
> >
> >> It may be possible to change ert's batch runner to hide each test's
> >> `message' output, perhaps printing it only if the test fails.
> >
> > That's a good idea.  How about opening a feature request to track it?
>
> Done as bug#59317.
>
> And with that, and Eli's commits, I'll close this bug.  Thanks.
>
>
> --- End Message ---