public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: "Nir Tzachar" <tzachar@grad120a.cs.bgu.ac.il>
Cc: linux-kernel@vger.kernel.org, bzolnier@gmail.com,
	zippel@linux-m68k.org, linux-kbuild@vger.kernel.org,
	rdunlap@xenotime.net, kosaki.motohiro@jp.fujitsu.com,
	7eggert@gmx.de, Nir Tzachar <nir@tzachar.com>
Subject: Re: [PATCH] ncurses based config V2
Date: Fri, 5 Sep 2008 15:49:53 +0200	[thread overview]
Message-ID: <20080905154953.3abefbce@Varda> (raw)
In-Reply-To: <1220603220-17090-1-git-send-email-nir@tzachar.com>

El Fri,  5 Sep 2008 11:27:00 +0300
"Nir Tzachar" <tzachar@nexus.cs.bgu.ac.il> escribió:

> Changes:
> 1) Fixed segfaults in help window.
> 2) Removed the instructions window, made the instructions appear as a button
>    which displays a popup window.
> 3) Added hot keys support. As ncurses does not support several colors inside
>    a menu, keys are highlighted using "()".
> 4) Optimized for 80x24 terminals.
> 6) Fixed zconf.y to use _menu_init
> 7) added nconfig to "make help"
> 8) Misc fixes.
> 
> Comments are appreciated.
> Cheers.
> ---
>  scripts/kconfig/Makefile            |   17 +-
>  scripts/kconfig/lkc.h               |    2 +-
>  scripts/kconfig/mconf.c             |    2 +
>  scripts/kconfig/menu.c              |    2 +-
>  scripts/kconfig/nconf.c             | 2019 +++++++++++++++++++++++++++++++++++
>  scripts/kconfig/zconf.tab.c_shipped |    2 +-
>  scripts/kconfig/zconf.y             |    2 +-
>  7 files changed, 2041 insertions(+), 5 deletions(-)
>  create mode 100644 scripts/kconfig/nconf.c

 Tried it and the segmentation fault disappeared 

> 

  reply	other threads:[~2008-09-05 13:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 19:11 [PATCH] ncurses based config 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
2008-09-05  8:27 ` [PATCH] ncurses based config V2 Nir Tzachar
2008-09-05 13:49   ` Alejandro Riveira Fernández [this message]
2008-09-05 19:59   ` Willy Tarreau
2008-09-06  5:41     ` Nir Tzachar
2008-09-14 10:52       ` Willy Tarreau
2008-09-17 11:58         ` Nir Tzachar
2008-11-24 18:44     ` Sam Ravnborg
2008-11-25  2:33       ` Roman Zippel
2008-11-25  8:04         ` Nir Tzachar
2008-11-25 16:02           ` Roman Zippel
2008-11-25  8:01       ` Nir Tzachar
2008-11-25  8:11         ` Sam Ravnborg
2008-11-25 12:35           ` Nir Tzachar
2008-11-29 21:40 ` sss Nir Tzachar
2008-11-29 21:40   ` [PATCH] nconfig V3 Nir Tzachar

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=20080905154953.3abefbce@Varda \
    --to=ariveira@gmail.com \
    --cc=7eggert@gmx.de \
    --cc=bzolnier@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.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