GNU bug report logs -
#43308
28.0.50; Improvements to Edit->Search menu
Previous Next
Reported by: Ihor Radchenko <yantar92 <at> gmail.com>
Date: Thu, 10 Sep 2020 14:20:02 UTC
Severity: normal
Found in version 28.0.50
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #71 received at 43308 <at> debbugs.gnu.org (full text, mbox):
> From: Juri Linkov <juri <at> linkov.net>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, Ihor Radchenko <yantar92 <at> gmail.com>,
> 43308 <at> debbugs.gnu.org, stefankangas <at> gmail.com
> Date: Tue, 22 Sep 2020 11:04:58 +0300
>
> >> Why no keybindings are shown for nonincremental menu items?
> >> They still have keybindings, e.g. nonincremental forward search
> >> can be started with 'C-s RET', nonincremental backward search
> >> with 'C-r RET', nonincremental regexp search 'C-M-s RET', etc.
> >
> > I suppose I could add some explicitly, with :keys.
> > That makes sense. Unfortunately, none show up
> > automatically. It would be good to somehow fix that.
>
> How about the following patch?
But the keys this will show don't invoke the same commands, they
invoke slightly different commands, don't they? I don't think we ever
show keys that invoke a different command, why do this here?
> Another problem is that selecting "Continue Tags Search"
> signals the error:
>
> emacs -Q
> Select "Edit" -> "Search" -> "Continue Tags Search"
>
> Lisp error: (wrong-type-argument commandp fileloop-continue)
I guess this is a leftover from migration to Xref.
> I think "Continue Tags Search" should be disabled when it has no effect.
Yes, it should be.
Thanks.
This bug report was last modified 3 years and 28 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.