From: Dirk Gouders <dirk@gouders.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/1] mconf: Emacs-like isearch
Date: Thu, 07 Jun 2018 01:54:30 +0200 [thread overview]
Message-ID: <ghr2ljv5c9.fsf@lena.gouders.net> (raw)
In-Reply-To: <f833ff8b-75ed-3ca4-ec24-a129a05902d1@infradead.org> (Randy Dunlap's message of "Wed, 6 Jun 2018 16:31:44 -0700")
Randy Dunlap <rdunlap@infradead.org> writes:
> On 06/06/2018 03:32 PM, Dirk Gouders wrote:
>> Randy Dunlap <rdunlap@infradead.org> writes:
>>
>>> On 06/06/2018 02:56 PM, Dirk Gouders wrote:
>>>> Hello,
>>>>
>>>> being an Emacs user, I frequently find myself pressing CTRL-s in mconf
>>>> to search for some menu entry, especially in large menus.
>>>>
>>>> I decided to implement a basic isearch in mconf and would like to hear
>>>> if others find this functionality useful, as well.
>>>>
>>>> The new functionality is started with pressing CTRL-s followed by
>>>> characters that form the search string. To search for further
>>>> occurences of an entered string, press CTRL-s instead of further
>>>> characters.
>>>>
>>>> For example: to navigate to the USB device drivers, press CTRL-s de ENTER ENTER usb ENTER ENTER
>>>
>>> Not being an emacs user, what is the "de" for above?
>>
>> "de" (with my .config) causes a match for "Device Drivers" --
>> no other menu entry matching the string "de" is befor that entry.
>>
>
> Device Drivers is the first match for me also.
>
> To get to the USB drivers, I have to enter:
> CTRL-s de ENTER ENTER CTRL-s usb ENTER ENTER
Yes, I left out the second CTRL-s, thank you!
Oh well, I shouldn't have sent this late at night, then I would probably
have explained the needed input as:
1) CTRL-s // start isearch
2) de // substring that matches "Device Drivers"
3) ENTER // quit isearch
4) ENTER // enter Device Drivers menu
5) CTRL-s // start isearch
6) usb // navigate to USB support
7) ENTER // quit isearch
8) ENTER // enter USB support menu
Again, I'm really sorry for the confusion.
Dirk
next prev parent reply other threads:[~2018-06-06 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 21:56 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 [this message]
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
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=ghr2ljv5c9.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=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
all inboxes | Powered by JetHome®