public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Alexander Holler <holler@ahsoftware.de>, Aldo Iljazi <me@aldo.io>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Proposal for menuconfig removal
Date: Thu, 24 Oct 2013 09:39:48 -0700	[thread overview]
Message-ID: <52694D54.8040404@infradead.org> (raw)
In-Reply-To: <52693E48.6000905@ahsoftware.de>

On 10/24/13 08:35, Alexander Holler wrote:
> Am 24.10.2013 17:02, schrieb Aldo Iljazi:
>> On 24-10-2013 17:03, Alexander Holler wrote:
>>> Am 24.10.2013 13:56, schrieb Aldo Iljazi:
>>>> Since nconfig is there, menuconfig is redundant.
>>>>
>>>> I am proposing to remove it from the kernel.

I am not seeing a good reason to remove menuconfig.

>>>
>>> Looks like nconfig depends on F-keys, which unfortunately do disappear
>>> more and more on modern keyboards, so I wouldn't call that a very good
>>> idea.
>>>
>>> Regards,
>>>
>>> Alexander Holler
>>> -- 
>>
>> If that's the case then I agree, but are they really? I've not seen a
>> keyboard without F-keys.
> 
> There are many of them. But it isn't only about keyboards without those keys, it's about situations where those keys are inaccesible too. Guess why Midnight Commander supports ESC-n as alternative for Fn.
> 
> Or just try to use make nconfig from any of the various Android (SSH)-Terminals. Relying on F-keys isn't a very good idea.

nconfig supports use of <Fn> or just numeric <n> key for the same functions.


-- 
~Randy

  reply	other threads:[~2013-10-24 16:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 11:56 Proposal for menuconfig removal Aldo Iljazi
2013-10-24 14:03 ` Alexander Holler
     [not found]   ` <e0a7d6b725f97abf03b4bcf1a4238658@aldo.io>
2013-10-24 15:35     ` Alexander Holler
2013-10-24 16:39       ` Randy Dunlap [this message]
2013-10-24 16:43         ` Alexander Holler
     [not found]           ` <ec548356659f70fd3a15c33bc365e171@aldo.io>
     [not found]             ` <526951EB.6010705@ahsoftware.de>
2013-10-24 17:03               ` Aldo Iljazi
2013-10-24 17:04                 ` Randy Dunlap
2013-10-24 17:12                   ` Alexander Holler
2013-10-25  7:51                   ` Richard Cochran
2013-10-24 17:06                 ` Richard Weinberger
2013-10-24 17:08                   ` Aldo Iljazi
2013-10-24 17:03           ` Randy Dunlap
2013-10-24 17:10             ` Alexander Holler
2013-10-24 17:13               ` Randy Dunlap
2013-10-25 22:39 ` Sören Brinkmann

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=52694D54.8040404@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=holler@ahsoftware.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@aldo.io \
    /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