From: Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74090@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#74090: 31.0.50; Problems with dabbrev-expand
Date: Sat, 30 Nov 2024 23:30:21 +0100 [thread overview]
Message-ID: <87jzcke4n6.fsf@gmx.net> (raw)
In-Reply-To: <865xo47af4.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Nov 2024 22:07:27 +0200")
On Sat, 30 Nov 2024 22:07:27 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Juri Linkov <juri@linkov.net>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 74090@debbugs.gnu.org
>> Date: Sat, 30 Nov 2024 19:51:38 +0200
>>
>> >>> 1. C-x b foo RET
>> >>> 2. Type: abc SPC abd
>> >>> 3. C-x b *scratch* RET
>> >>> 4. Type: ab M-/
>> >>> 5. C-x k foo RET
>> >>> 6. Type: SPC ab M-/
>> >>
>> >> Sorry, I meant emacs-30, not emacs-29.
>> >
>> > Thanks, I can reproduce it. With the attached patch (against emacs-30)
>> > I don't get the error; instead, at step 6 "ab" expands to "abc", which I
>> > suppose is what's expected, and then typing `M-/' again shows the
>> > message "No further dynamic expansion for ‘ab’ found", which also seems
>> > as expected. And with the patch, all current dabbrev regression tests
>> > pass with ert-run-tests-batch-and-exit. Does anyone see a problem with
>> > the patch?
>>
>> Thanks, I confirm it works now.
Thanks!
> Thanks for testing. Stephen, you have green light for installing this
> on the emacs-30 branch.
Thanks, done in commit bd8a6f70fb9.
>> Would it be nice to have a new test that covers this case?
>
> Definitely. But it is less urgent than fixing the bug itself.
I've added a test but I'm somewhat dissatisfied with it. I wanted to
essentially reproduce the behavior I see with the patch, described
above. However, after killing buffer "foo", the message about no
further expansion is from a user-error in dabbrev-expand, and on hitting
this in the test run, the test immediately finishes. So I used
should-error with :type 'user-error and the test succeeds, but I cannot
test for the final buffer content nor the message displayed by
user-error. If anyone has an idea how to do that or otherwise improve
the test, please chime in.
Steve Berman
next prev parent reply other threads:[~2024-11-30 22:30 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 [this message]
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
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=87jzcke4n6.fsf@gmx.net \
--to=bug-gnu-emacs@gnu.org \
--cc=74090@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--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).