linux-kernel - Re: [PATCH resend v3 3/3] kconfig: nconf: add vi-style navigation keys

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 9 Feb 2013 12:36:23 +0100
From:	"Yann E. MORIN" <yann.morin.1998@...e.fr>
To:	Roland Eggner <edvx1@...temanalysen.net>
Cc:	linux-kbuild@...r.kernel.org, Dmitry Voytik <dvv.kernel@...il.com>,
	Michal Marek <mmarek@...e.cz>,
	Stephen Boyd <sboyd@...eaurora.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH resend v3 3/3] kconfig: nconf:  add vi-style navigation keys

Rolland, All,

On Saturday 09 February 2013 Roland Eggner wrote:
> 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.

I never said it was anachronistic. I just oppose this change as it conflicts
with a fundamental existing behavior (getting help) that people have come to
rely on.

> 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?

How do you navigate up/down in the help text (when the terminal is not
high enought to display the entire help) if it is displayed at the same
time the menu entries are, yet without breaking the UI behavior people
expect?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/