From: Randy Dunlap <rdunlap@infradead.org>
To: Dirk Gouders <dirk@gouders.net>
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: Wed, 6 Jun 2018 16:31:44 -0700 [thread overview]
Message-ID: <f833ff8b-75ed-3ca4-ec24-a129a05902d1@infradead.org> (raw)
In-Reply-To: <ghzi07v944.fsf@lena.gouders.net>
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
>>
>>> Pressing just CTRL-s subsequently results in line-by-line navigation
>>> through the menu (search for empty strings).
>>>
>>> The isearch is terminated by pressing either ESC ESC or ENTER.
>>>
>>> Because I expect that errors are found in the code and changes are requested, I
>>> completely left out the documentation part and will add it to V2
>>> should anyone find this functionality useful.
>>
>> Hm, it seems to take 2 entries of Ctrl-s to begin the search??
>> No, it takes 2 entries of Ctrl-s to display the "isearch:" prompt,
>> but entering one Ctrl-s + a string will display it also.
>>
>> Anyway, I am having trouble getting the USB drivers example to work.
>
> Yes, I should have stated that this example explains what _I_ have to do to
> navigate to the USB device drivers. Probably, "de" in your case matches
> some other menu entry and the navigation requires more or other input.
>
> I'm sorry for causing confusion.
No problem.
Thanks.
> Dirk
>
>>> Thanks,
>>>
>>> Dirk
>>>
>>> Dirk Gouders (1):
>>> Emacs-like isearch for mconf.
>>>
>>> scripts/kconfig/lxdialog/dialog.h | 5 ++
>>> scripts/kconfig/lxdialog/menubox.c | 140 ++++++++++++++++++++++++++++++++++++-
>>> scripts/kconfig/lxdialog/util.c | 1 +
>>> 3 files changed, 145 insertions(+), 1 deletion(-)
>>>
>>
>> thanks,
--
~Randy
next prev parent reply other threads:[~2018-06-06 23:31 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 [this message]
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
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=f833ff8b-75ed-3ca4-ec24-a129a05902d1@infradead.org \
--to=rdunlap@infradead.org \
--cc=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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®