From: Randy Dunlap <rdunlap@infradead.org>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Aldo Iljazi <me@aldo.io>, linux-kernel@vger.kernel.org
Subject: Re: Proposal for menuconfig removal
Date: Thu, 24 Oct 2013 10:13:43 -0700 [thread overview]
Message-ID: <52695547.6010706@infradead.org> (raw)
In-Reply-To: <52695495.1090007@ahsoftware.de>
On 10/24/13 10:10, Alexander Holler wrote:
> Am 24.10.2013 19:03, schrieb Randy Dunlap:
>> On 10/24/13 09: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.
>>
>> I found it there (in global help):
>>
>> Unless in a data entry window, key <1> may be used instead of <F1>,
>> <2> instead of <F2>, etc.
>>
>> but if you don't have Function keys, you may not be able to read the
>> global help text.
>
> Oh, yes, there it is. I've read the help twice, but haven't seen it. ;)
> Maybe moving that paragraph to the top will help. I don't know why I haven't seen it.
I agree, it should be less hidden.
--
~Randy
next prev parent reply other threads:[~2013-10-24 17:13 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
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 [this message]
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=52695547.6010706@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