From: Sam Ravnborg <sam@ravnborg.org>
To: Dirk Gouders <dirk@gouders.net>
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 v4 0/1] i-search functionality for mconf
Date: Fri, 8 Jun 2018 23:56:55 +0200 [thread overview]
Message-ID: <20180608215655.GB28473@ravnborg.org> (raw)
In-Reply-To: <20180608184606.5029-1-dirk@gouders.net>
Hi Dirk.
On Fri, Jun 08, 2018 at 08:46:05PM +0200, Dirk Gouders wrote:
> Hello,
>
> this version is a prototype of the idea, Sam suggested -- I hope I
> undestood it correctly.
>
> This is a remarkable change to mconf in it's behavior; mainly it now
> differentiates two focuses and operates differently, depending on the
> focus. When the focus is on the menu, mconf is in i-search mode, for
> a detailed description see 1/1.
>
> As stated earlier, this is just a prototype, documentation is missing
> and the code is not ready for a real commit.
When trying this out it started to work as envisioned.
But somehw I manage to get stuck in the menus and cannot navigate to
the buttons.
Consider to remove the old short-cut for the menus.
(Most/all the first_alph thingy in menubox.c)
That will avoid two confliting navigations principles and likely
make the code simpler to read.
I am not sure, but maybe you can get rid of all the hotkey
support in print_item with this change too.
Sam
next prev parent reply other threads:[~2018-06-08 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 18:46 Dirk Gouders
2018-06-08 18:46 ` [RFC v4 1/1] " Dirk Gouders
2018-06-09 0:59 ` Randy Dunlap
2018-06-08 21:56 ` Sam Ravnborg [this message]
2018-06-09 7:40 ` [RFC v4 0/1] " 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=20180608215655.GB28473@ravnborg.org \
--to=sam@ravnborg.org \
--cc=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
all inboxes | Powered by JetHome®