From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from asavdk4.altibox.net ([109.247.116.15]:34410 "EHLO asavdk4.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753703AbeFGQcP (ORCPT ); Thu, 7 Jun 2018 12:32:15 -0400 Date: Thu, 7 Jun 2018 18:32:08 +0200 From: Sam Ravnborg Subject: Re: [RFC 0/1] mconf: Emacs-like isearch Message-ID: <20180607163208.GA26914@ravnborg.org> References: <20180606215616.12817-1-dirk@gouders.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Dirk Gouders Cc: Masahiro Yamada , Randy Dunlap , Linux Kbuild mailing list , Linux Kernel Mailing List , Segher Boessenkool > > I'd say it's not important to start isearch with CTRL-s, I am just so > used to it. So, I am open for suggestions. Today we have first or one of the first letters as shortcut to menus. How about considering everything typed as search inputs. Search is then stopped by ESC, arrow keys and maybe more. Search is only possible when a menu is selected, not with focus on the buttons. This will break the habits of people used to the shortcut variant, but then we have the more flexible i-search variant. Idea? Sam