From: Bodo Eggert <7eggert@gmx.de>
To: Nir Tzachar <nir@tzachar.com>
Cc: 7eggert@gmx.de,
"Alejandro Riveira Fernández" <ariveira@gmail.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
"Nir Tzachar" <tzachar@grad120a.cs.bgu.ac.il>,
linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] ncurses based config
Date: Thu, 4 Sep 2008 16:37:01 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.0.999.0809041627170.16019@be1.lrz> (raw)
In-Reply-To: <9b2db90b0809040517v4478f1b9md69ea07ef9c62c86@mail.gmail.com>
On Thu, 4 Sep 2008, Nir Tzachar wrote:
> On Thu, Sep 4, 2008 at 3:21 PM, Bodo Eggert <7eggert@gmx.de> wrote:
> > In other words: You don't permanently need half a screen of instructions,
> > hide them by default and offer a popup. The window below the title is the
> > only working area, it can be maximized. (Looking at "make menuconfig",
> > I see the same mistakes.)
>
> I tried to copy the behaviour of menuconfig, hence the similarity.
Obviously. I tried to put the blame on menuconfig by mentioning it.
> Does placing a short help, e.g., 'press I for instruction' seems
> good?
In this case, I'd just add one more button.
next prev parent reply other threads:[~2008-09-04 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b86dt-3nV-39@gated-at.bofh.it>
[not found] ` <b86wB-3HU-1@gated-at.bofh.it>
[not found] ` <b86Qa-4k2-53@gated-at.bofh.it>
[not found] ` <b879t-4DG-23@gated-at.bofh.it>
2008-09-04 12:21 ` Bodo Eggert
[not found] ` <9b2db90b0809040517v4478f1b9md69ea07ef9c62c86@mail.gmail.com>
2008-09-04 14:37 ` Bodo Eggert [this message]
2008-09-03 19:11 Nir Tzachar
2008-09-03 19:38 ` Bartlomiej Zolnierkiewicz
2008-09-03 20:02 ` Randy.Dunlap
2008-09-03 20:03 ` Randy.Dunlap
2008-09-03 20:18 ` Bartlomiej Zolnierkiewicz
2008-09-03 20:29 ` Alejandro Riveira Fernández
2008-09-04 15:02 ` Bartlomiej Zolnierkiewicz
[not found] ` <9b2db90b0809032155h6ed5df9ey846de96779022d11@mail.gmail.com>
2008-09-04 15:28 ` Randy.Dunlap
2008-09-04 4:22 ` KOSAKI Motohiro
2008-09-04 10:36 ` Alejandro Riveira Fernández
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=alpine.LSU.0.999.0809041627170.16019@be1.lrz \
--to=7eggert@gmx.de \
--cc=ariveira@gmail.com \
--cc=bzolnier@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir@tzachar.com \
--cc=rdunlap@xenotime.net \
--cc=tzachar@grad120a.cs.bgu.ac.il \
--cc=zippel@linux-m68k.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®