public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Eggner <edvx1@systemanalysen.net>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org,
	Dmitry Voytik <dvv.kernel@gmail.com>,
	Michal Marek <mmarek@suse.cz>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nconf: add vi-style command keys for the menu navigation
Date: Tue, 15 Jan 2013 18:12:52 +0100	[thread overview]
Message-ID: <20130115171252.GD5513@mobil.systemanalysen.net> (raw)
In-Reply-To: <201301142310.32044.yann.morin.1998@free.fr>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

On 2013-01-14 Monday at 23:10 +0100 Yann E. MORIN wrote:
> Dmitry, All,
> 
> On Friday 28 December 2012 Dmitry Voytik wrote:
> > Add alternative vi-style keys for the menu navigation:
> > <j>/<k> for down/up navigation, <C-f>/<C-b> for
> > page down/up, <g>/<G> for first/last menu item selection
> > and <l> for entering to a submenu.
> 
> The <g>/<G> keys are not documented in the help text.
> <HOME>/<END> are not, either.

Already documented in previous version and in v2 posted half hour ago:

User interface:
<F1> “Global help“, table starting near line 36.

Source code:
grep -E -n '(First|Last) entry' scripts/kconfig/nconf.c


> Care to add those and resend, please?

v2 based on 3.8-rc3 posted.


Thanks for review.
-- 
Roland Eggner


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-01-15 17:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121228185108.GA13644@voyt-hp>
2012-12-28 19:40 ` [PATCH] nconf: add vi-style command keys for the menu navigation Dmitry Voytik
2012-12-29 22:33   ` [PATCH 2/2] nconf: function keys line, change background color for better readability Roland Eggner
2013-01-14 22:20     ` Yann E. MORIN
2013-01-14 22:26       ` Yann E. MORIN
2012-12-29 22:34   ` [PATCH 1/2] nconf: add keybindings for vi-style menu navigation, rewrite help texts Roland Eggner
2013-01-08 22:04     ` Yann E. MORIN
2013-01-14 18:24     ` Yann E. MORIN
2013-01-15 16:10       ` Roland Eggner
2013-01-15 16:26         ` [PATCH v2 " Roland Eggner
2013-01-15 16:36           ` [PATCH v2stable " Roland Eggner
2013-01-15 17:39             ` Yann E. MORIN
2013-01-15 22:27           ` [PATCH v2 " Yann E. MORIN
2013-01-16 20:19             ` Roland Eggner
2013-01-16 12:48           ` Michal Marek
2013-01-08 21:57   ` [PATCH] nconf: add vi-style command keys for the menu navigation Yann E. MORIN
2013-01-14 22:10   ` Yann E. MORIN
2013-01-15 17:12     ` Roland Eggner [this message]
2013-01-15 17:38       ` Yann E. MORIN
2013-01-15 17:55         ` Roland Eggner

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=20130115171252.GD5513@mobil.systemanalysen.net \
    --to=edvx1@systemanalysen.net \
    --cc=dvv.kernel@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sboyd@codeaurora.org \
    --cc=yann.morin.1998@free.fr \
    /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