From: Juri Linkov <juri@linkov.net>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 74090@debbugs.gnu.org
Subject: bug#74090: 31.0.50; Problems with dabbrev-expand
Date: Tue, 03 Dec 2024 09:35:30 +0200 [thread overview]
Message-ID: <87o71tb4ot.fsf@mail.linkov.net> (raw)
In-Reply-To: <87ttbmxov8.fsf@gmx.net> (Stephen Berman's message of "Mon, 02 Dec 2024 13:15:23 +0100")
> With these changes the test succeeds in batch runs and I think now better
> reflects the user experience with manual input, so I went ahead and
> pushed the fix (commit 6bca138d60e to emacs-30). If you agree, feel
> free to close the bug again (assuming it needs to be reclosed, since you
> unarchived it); otherwise, if you see other problems with the test,
> please let me know.
I see the same test failures that were reported on emacs-devel.
One of them is clear because of quotes mismatch:
(string= "No further dynamic expansion for `ab' found"
"No further dynamic expansion for ‘ab’ found")
But why 4 lines with should-error affect two other tests
is not clear. Maybe other tests expect the initial contents
in the scratch buffer? Or the same buffer list?
Generally, this is deficiency of the test-suite design
that tests are not isolated.
next prev parent reply other threads:[~2024-12-03 7:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 17:06 bug#74090: 31.0.50; Problems with dabbrev-expand Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-29 18:17 ` Juri Linkov
2024-10-29 18:57 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-30 7:32 ` Juri Linkov
2024-10-31 10:01 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-30 13:03 ` Eli Zaretskii
2024-10-31 10:00 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-31 10:09 ` Eli Zaretskii
2024-10-31 10:20 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-31 10:39 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-31 10:47 ` Eli Zaretskii
2024-10-31 11:17 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87ttbq7eie.fsf@mail.linkov.net>
2024-11-29 7:51 ` Juri Linkov
2024-11-29 15:38 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 17:51 ` Juri Linkov
2024-11-30 20:07 ` Eli Zaretskii
2024-11-30 22:30 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-02 7:33 ` Juri Linkov
2024-12-02 12:15 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-03 7:35 ` Juri Linkov [this message]
2024-12-03 9:39 ` Stephen Berman 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
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=87o71tb4ot.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=74090@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stephen.berman@gmx.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).