Linux kbuild/kconfig development
 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 resend v3 3/3] kconfig: nconf:  add vi-style navigation keys
Date: Sat, 9 Feb 2013 06:07:48 +0100	[thread overview]
Message-ID: <20130209050748.GB8891@mobil.systemanalysen.net> (raw)
In-Reply-To: <201302090203.04055.yann.morin.1998@free.fr>

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

On 2013-02-09 Saturday at 02:03 +0100 Yann E. MORIN wrote:
> On Friday 01 February 2013 Roland Eggner wrote:
> > Add vi-style navigation keys, based on initial work by Dmitry Voytik.
> 
> As much I am a unconditional vim user, I doubt this is a sane idea to
> include this, as it conflicts with the established UI that people expect,
> especially since <h> is remapped and people already rely on <h> to provide
> help, not do any other weird thing (like exiting the current submenu).

Having the most frequently used keys in the middle of the keyboard is 
a professional computer usage pattern, not an anachronistic one.

Regarding the <h>/<H> conflict:  My vision is to eliminate the need for help 
keybindings <h> <?> at all by displaying the related help text beside the menu 
permanently, similar to some graphical backends.  For terminals with 
COLUMNS>=160 this should be rather easy to implement.  nouveaufb gives me by 
default terminal with 274 columns, “retina” displays are entering the market 
… the frequency of COLUMNS>=160 terminals probably will continue to grow.  While 
staying compatible with COLUMNS=80, it seems reasonable to use the capabilities 
of wider terminals, or what would you say?

Cannot promise when I will find the time to prepare a patch.

-- 
Regards
Roland Eggner

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

  reply	other threads:[~2013-02-09  5:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 18:22 [PATCH resend v3 0/3] kconfig: nconf: rewrite help texts, add vi-style navigation keys Roland Eggner
2013-02-01 18:27 ` [PATCH resend v3 1/3] kconfig: nconf: rewrite help texts Roland Eggner
2013-02-09  0:30   ` Yann E. MORIN
2013-02-09  3:46     ` Roland Eggner
2013-02-09 11:23       ` Yann E. MORIN
2013-02-10  3:00         ` Roland Eggner
2013-02-01 18:30 ` [PATCH resend v3 2/3] kconfig: nconf: rewrite labels of function keys line Roland Eggner
2013-02-01 18:33 ` [PATCH resend v3 3/3] kconfig: nconf: add vi-style navigation keys Roland Eggner
2013-02-09  1:03   ` Yann E. MORIN
2013-02-09  5:07     ` Roland Eggner [this message]
2013-02-09 11:36       ` Yann E. MORIN
2013-02-10  4:09         ` Roland Eggner
2013-02-03 10:16 ` [PATCH resend v3 0/3] kconfig: nconf: rewrite help texts, " yann.morin.1998

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=20130209050748.GB8891@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