From: Dirk Gouders <dirk@gouders.net>
To: 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>
Cc: Dirk Gouders <dirk@gouders.net>
Subject: [RFC v2 0/1] Emacs-like isearch for mconf.
Date: Thu, 7 Jun 2018 15:53:08 +0200 [thread overview]
Message-ID: <20180607135309.16928-1-dirk@gouders.net> (raw)
*** BLURB HERE ***
Hello,
this is v2 of the isearch implementation, I also added Documentation changes which
probably have to be split, because the older symbol-search also was undokumented in
mconf (I basically copied the relevant documentation from Documentation/kbuild/kconfig.txt.
I could not completely let off CTRL-s but am certainly fine with get rid of it and
stay with just one special key (e.g. \) to start isearch.
Changes since v1:
* Additionally to CTRL-s, \ can be used to start isearch.
* Raw mode is off by default an can be enabled by an environment
variable MENUCONFIG_RAW_MODE.
* I also added a variable for toggling raw mode but did not implement
anything else.
* The isearch indicator is now displayed as soon as isearch is
started.
* Any key except \, CTRL-s, alphanumeric characters and space
terminates isearch and -- except ESC ESC -- is further processed,
e.g. ENTER terminates isearch and is then used to navigate into a
submenu.
* Problems with mismatches and matches above the current position were
fixed.
Dirk
Documentation/kbuild/kconfig.txt | 18 +++-
scripts/kconfig/lxdialog/dialog.h | 6 ++
scripts/kconfig/lxdialog/menubox.c | 173 +++++++++++++++++++++++++++++++++++++
scripts/kconfig/lxdialog/util.c | 14 +++
scripts/kconfig/mconf.c | 48 +++++++++-
5 files changed, 256 insertions(+), 3 deletions(-)
--
2.16.4
reply other threads:[~2018-06-07 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180607135309.16928-1-dirk@gouders.net \
--to=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).