GNU bug report logs - #66187
read-file-name unexpected behavior when MUSTMATCH is a function

Previous Next

Full log

Message #62 received at 66187 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Joseph Turner <joseph <at> breatheoutbreathe.in>, Michael Heerdegen
 <michael_heerdegen <at> web.de>
Cc: "philipk <at> posteo.net" <philipk <at> posteo.net>,
 "66187 <at> debbugs.gnu.org" <66187 <at> debbugs.gnu.org>
Subject: RE: [External] : bug#66187: read-file-name unexpected behavior when
 MUSTMATCH is a function
Date: Tue, 3 Oct 2023 23:00:37 +0000

> Since completing-read is such a fundamental part of Emacs,
> I doubt it will be possible to change this behavior.

Apparently it was possible for Someone (TM) to
change the behavior, in spite of the fact that
it's a longstanding "fundamental part of Emacs".
It _was_ a fundamental part of Emacs, but it
seems that somehow it's signature was changed
for Emacs 29.

The new behavior for a function value of
REQUIRE-MATCH is backward-incompatible.

A function as REQUIRE-MATCH value _should_ still
be treated as any other value that's not nil, t,
`confirm', or `confirm-after-completion'.  I
filed bug #66328 for this.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.