|
From: | Thierry Volpiatto |
Subject: | bug#66394: 29.1; Make register-read-with-preview more useful |
Date: | Thu, 30 Nov 2023 10:21:39 +0000 |
Eli Zaretskii <eliz@gnu.org> writes: >> From: Thierry Volpiatto <thievol@posteo.net> >> Cc: monnier@iro.umontreal.ca, michael_heerdegen@web.de, >> stefankangas@gmail.com, 66394@debbugs.gnu.org >> Date: Wed, 29 Nov 2023 18:18:40 +0000 >> >> Eli Zaretskii <eliz@gnu.org> writes: >> >> > The response "a" to the "Point to register:" question is something I >> > needed to type; >> >> Of course we are using now read-from-minibuffer and the test is related >> to read-key not quitting with C-g >> >> > previously the test never asked any questions (and it shouldn't, >> > AFAIU). >> >> Yes, it shouldn't, but now we are using a real minibuffer, is this test >> really needed? >> It is like if you had to make tests in all functions using >> read-from-minibuffer to check if it quit properly with C-g (it does of >> course). > > Can we have a similar issue with read-from-minibuffer? Not with C-g, > but with some other invalid input, like some function key or non-ASCII > character or invalid character codepoint? No, because unlike read-key, read-from-minibuffer doesn't read these keys and exit immediately. For example we can now set a register to C-g by using "C-q C-g" but hitting directly C-g will quit minibuffer (as expected), BTW I have updated the manual, see the attached patchs. I have also fixed register-preview-default accordingly so that it print the register as a string but not a key representation e.g. "^X" instead of "C-x" (if one find this ugly we could use "C-x" as a display property of "^X"). > If this cannot happen, then perhaps the whole test file should be > removed? I think it can be removed, yes (done in patch below). > Anyway, I trust you to do what is needed here, I just want the test > suite to keep running successfully, and I don't have time to work on > this myself. TIA. Ok, can you review (and merge if ok) following patchs. >> ALSO: I intentionally leave register-preview-delay defcustom with a FIXME >> comment, do you want to remove it? It is not used anymore now AFAIK. > > This should be declared obsolete, with an explanation that it is no > longer used, and a note about that should be added to NEWS, in the > incompatible changes section. Then we can remove the FIXME. done. Thanks. -- Thierry
0001-Make-register-preview-delay-obsolete.patch
Description: Text Data
0002-Fix-register-preview-default.patch
Description: Text Data
0003-Update-register-manual.patch
Description: Text Data
0004-Delete-register-tests.el-now-no-more-needed.patch
Description: Text Data
signature.asc
Description: PGP signature
[Prev in Thread] | Current Thread | [Next in Thread] |