All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stevo" <stevo@cool3dz.com>
To: <linux-kernel@vger.kernel.org>
Cc: <shampton@tsiconnections.com>
Subject: (Simple) Basic Design Flaw in make menuconfig GUI
Date: Wed, 3 Sep 2003 10:40:17 -0400	[thread overview]
Message-ID: <001f01c37229$4bbd0410$1400a8c0@gaussian> (raw)

Hello, and thanks to all for continued support and developement of the Linux
kernel.  :)

APPLICATION: This applies to all kernels, all distributions, and all
architectures...


DESRIPTION: "make menuconfig"  GUI issue

SETUP: When I run "make menuconfig" and I am in the process of
enabling/disabling options, I have a "bad habit?" (that I'm sure is more
like an epidemic) of placing one finger on the "Esc" key, one finger on the
"Space" key, and another on the "Enter" key as I manuver through the various
selections.

PROBLEM: (ocassionally) While I am speeding through the kernel
configuration, I will accidentally hit the "Esc" key one too many times (I'm
sure we've all done this) and it will leave me at the "exit" screen:

                        Do you wish to save your new kernel config?

                                           <Yes>     <No>

In this case, neither choice is acceptable. In a plea to save time for all,
can someone please add one more simple choice to the "exit" menu?

                        Do you wish to save your new kernel config?

                             <Yes>     <No>     <Return to Config>



Thanks for your time, and thanks once again for all who continually work
towards the advancement of Linux.


Regards,
Steve Hampton


             reply	other threads:[~2003-09-03 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03 14:40 Stevo [this message]
2003-09-03 15:33 ` (Simple) Basic Design Flaw in make menuconfig GUI Randy.Dunlap
2003-09-03 17:03   ` Jan-Benedict Glaw
2003-09-03 22:17     ` Randy.Dunlap
2003-09-10 15:22 ` Tim Connors

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='001f01c37229$4bbd0410$1400a8c0@gaussian' \
    --to=stevo@cool3dz.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shampton@tsiconnections.com \
    /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.