mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Doug Jolley <doug@footech.com>
To: linux-kernel@vger.kernel.org
Subject: Bug in make menuconfig
Date: Fri, 18 Jul 2003 12:35:22 -0700	[thread overview]
Message-ID: <200307181935.h6IJZMo03779@vds.footech.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi --

I first noticed a bug in make menuconfig under 2.4 kernel.
Basically, while running the menuconfig target, if one
tries to load an alternative configuration file, the
cursor cannot be positioned into the area for adding the
name of the file.  It turns out that it works; but, an
unsuspecting user would likely not know that it is
working because the cursor position doesn't change.  It's
really a much more difficult problem to explain than it
is to observe.  Just try 'make menuconfig' and try to tab
so that the cursor is appropriately positioned so as to
be able to enter the name of an alternative configuration
file to load.  You'll see right away what I'm talking about.

As I say, I first noticed this under the 2.4 kernel.
I thought it would surely get fixed in the next release.
I see that the bug is still present in 2.6.0-test1.
Accordingly, I thought I should mention it.

Thanks and keep up the extroardinarily good work!

     ... doug
         (Linux+ Certified Professional)
         (LPI Level 1 Certified)
_____________________________________________________________________
Doug Jolley     mailto://doug@footech.com      http://www.footech.com
         Don't bogart that file, my friend.  Net it over to me.
#####################################################################
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: http://www.footech.com/doug/pubkey.asc

iD8DBQE/GE0PGg43bNIg8sERAks5AKDi8+npvHK1SmIW1aR2ZfPMNnm30gCeIGFE
E2keGd4kvs/1jIXwZUBcXqc=
=LdUR
-----END PGP SIGNATURE-----

                 reply	other threads:[~2003-07-18 19:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200307181935.h6IJZMo03779@vds.footech.com \
    --to=doug@footech.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®