From: Dirk Gouders <dirk@gouders.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Randy Dunlap <rdunlap@infradead.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [RFC 0/1] mconf: Emacs-like isearch
Date: Fri, 08 Jun 2018 09:56:50 +0200 [thread overview]
Message-ID: <gha7s5socd.fsf@lena.gouders.net> (raw)
In-Reply-To: <20180607163208.GA26914@ravnborg.org> (Sam Ravnborg's message of "Thu, 7 Jun 2018 18:32:08 +0200")
Sam Ravnborg <sam@ravnborg.org> writes:
>>
>> 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?
Sounds very interesting, I will see if I can prepare a prototype so that
users can test it an see if they feel that would be an improvement for
them. In mconf, a focus on the buttons would be conceptually new
and I am anticipating I am not yet realizing all of the consequences.
One situation, I am still thinking about how to handle it (without a
dedicated search key):
* The user types a string and then doesn't want to enter further string
characters but find further occurences of the already entered string.
(In my imagination, TAB is reserved to change focus to the buttons,
ENTER is reserved to stop searching -- and enter a submenu, depending
on the item.)
Dirk
prev parent reply other threads:[~2018-06-08 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 21:56 [RFC 0/1] mconf: Emacs-like isearch Dirk Gouders
2018-06-06 22:24 ` Randy Dunlap
2018-06-06 22:32 ` Dirk Gouders
2018-06-06 23:31 ` Randy Dunlap
2018-06-06 23:54 ` Dirk Gouders
2018-06-07 2:02 ` Masahiro Yamada
2018-06-07 5:56 ` Dirk Gouders
2018-06-07 16:32 ` Sam Ravnborg
2018-06-08 7:56 ` Dirk Gouders [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gha7s5socd.fsf@lena.gouders.net \
--to=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=segher@kernel.crashing.org \
--cc=yamada.masahiro@socionext.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox