From: Nir Tzachar <nir.tzachar@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: nconfig v7
Date: Sun, 13 Dec 2009 09:23:52 +0200 [thread overview]
Message-ID: <9b2db90b0912122323w25d2d815o70d0bd2f1e19a228@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.0912112023170.32039@obet.zrqbmnf.qr>
Hello.
On Fri, Dec 11, 2009 at 9:55 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
> Hi,
>
>
> I gave nconfig a try, and here are a few suggestive points:
10x ;)
> - provide the same color scheme as menuconfig
As far as colrs are involved, I think it is best to not impose any
color scheme. You can never satisfy everyone, and will get into
endless fights about which is best. I believe the current approach in
nconfig works best, as I am using the default terminal colors for the
main body of text (menus, help text, etc), and only use colors for
emphasis (headings, boxes, etc). This is based on the belief that
users have already chosen the colors which work best for them, and are
already using them in their teminal's config.
> - I get a visual glitch (see Exhibit A below) in General setup (patch
> slapped onto 2.6.32); the left frame part is missing.
I cannot reproduce this. Can you provide some more details? (e.g.,
which terminal, $LINES, $COLUMNS, $TERM)
> - For symbol info, it would be cool if it wrapped the "Selected by"
> line (menuconfig also "suffers" from this), because that one can
> get exceptionally long and awkward to scroll.
I took a look at the patch by Vadim Bendebury, should be easy to adapt nconfig.
> - I certainly like F4-Config-ShowAll :) but it has some glitches
> interfering near ARCH_DEFCONFIG (see Exhibit B).
Thanks for catching this. It is a by-product of the code for
presenting everything inside a single menu. Easily fixed in the next
version. By the way, is anyone using this option at all? It would much
simplify the code if I did not have to support the one giant menu
option.
Chhers,
Nir.
next prev parent reply other threads:[~2009-12-13 7:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 19:55 Jan Engelhardt
2009-12-12 11:37 ` Michal Marek
2009-12-13 7:23 ` Nir Tzachar [this message]
2009-12-13 11:09 ` Jan Engelhardt
2009-12-13 11:55 ` Sam Ravnborg
2009-12-13 14:25 ` Jan Engelhardt
2009-12-13 17:28 ` Sam Ravnborg
2009-12-14 5:34 ` Nir Tzachar
2009-12-14 5:39 ` Nir Tzachar
2009-12-14 5:41 ` Nir Tzachar
2009-12-14 12:26 ` Jan Engelhardt
2009-12-14 13:45 ` Nir Tzachar
2009-12-14 13:51 ` Jan Engelhardt
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=9b2db90b0912122323w25d2d815o70d0bd2f1e19a228@mail.gmail.com \
--to=nir.tzachar@gmail.com \
--cc=jengelh@medozas.de \
--cc=linux-kbuild@vger.kernel.org \
--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®