From: Alexander Holler <holler@ahsoftware.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Aldo Iljazi <me@aldo.io>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proposal for menuconfig removal
Date: Thu, 24 Oct 2013 19:12:16 +0200 [thread overview]
Message-ID: <526954F0.5040807@ahsoftware.de> (raw)
In-Reply-To: <5269532F.2080002@infradead.org>
Am 24.10.2013 19:04, schrieb Randy Dunlap:
> On 10/24/13 10:03, Aldo Iljazi wrote:
>> On 24-10-2013 19:59, Alexander Holler wrote:
>>> Am 24.10.2013 18:52, schrieb Aldo Iljazi:
>>>> On 24-10-2013 19:43, Alexander Holler wrote:
>>>>> Am 24.10.2013 18:39, schrieb Randy Dunlap:
>>>>>
>>>>>> nconfig supports use of <Fn> or just numeric <n> key for the same
>>>>>> functions.
>>>>>
>>>>> Ah, that isn't mentioned in the global help.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Alexander Holler
>>
>> Therefore, it can be done?
>
> Why? You don't offer any justification for removing menuconfig.
>
> Is it a burden to someone? to its maintainer?
I still prefer menuconfig because I find it easier to use <tab> to cycle
between menu-options than to use <Fn> or just <n>.
Regards,
Alexander Holler
next prev parent reply other threads:[~2013-10-24 17:12 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
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 [this message]
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=526954F0.5040807@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=me@aldo.io \
--cc=rdunlap@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.