mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Kconfiglib menuconfig implementation
Date: Thu, 3 May 2018 13:31:14 -0700	[thread overview]
Message-ID: <5768c009-d659-c5d7-ae63-ea041362762d@infradead.org> (raw)
In-Reply-To: <CAFkk2KTE+h+UY83vvbFDgG9zcyNy4jZYg+-O3p1yOBmLH-K9Xw@mail.gmail.com>

On 05/02/2018 07:47 PM, Ulf Magnusson wrote:
> On Tue, May 1, 2018 at 8:52 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 05/01/2018 11:13 AM, Randy Dunlap wrote:
>>
>> Hi Ulf,
>>
>> When menuconfig displays the Kconfig menu tree and it is over term-width
>> characters, it truncates on the left so that the user can see all of
>> the current menu name. menuconfig.py truncates on the right so that
>> the current menu name may be partially lost or totally lost.
> 
> Fixed. The menu path now scrolls to the right as needed. Maybe "..."
> could be displayed as well, though I'm not sure if it's helpful in
> practice.

Not needed.

>>
>> To enable=y a tristate symbol, cannot enter Y, must do Space Space to cycle
>> from N to M to Y.
> 
> Fixed.
> 
>>
>> No / symbol search. I use that a lot, but I don't claim to be a
>> typical user.
> 
> Coming soon. I have added a "show-all" mode in preparation for it, as
> you might want to jump to invisible symbols.

Sounds good.

> Screenshot: https://raw.githubusercontent.com/ulfalizer/Kconfiglib/screenshots/screenshots/ss9.png


One minor nit (bikeshed?):  I'm not crazy about "make scriptconfig".  :)

thanks,
-- 
~Randy

  reply	other threads:[~2018-05-03 20:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  0:57 Ulf Magnusson
2018-05-01 17:56 ` Randy Dunlap
2018-05-01 18:13   ` Randy Dunlap
2018-05-01 18:52     ` Randy Dunlap
2018-05-01 19:33       ` Ulf Magnusson
2018-05-03  2:47       ` Ulf Magnusson
2018-05-03 20:31         ` Randy Dunlap [this message]
2018-05-03 21:26           ` Ulf Magnusson
2018-05-01 19:12   ` Ulf Magnusson
2018-05-01 19:47     ` Ulf Magnusson
2018-05-01 21:07       ` Ulf Magnusson
2018-05-03 20:28         ` Randy Dunlap
2018-05-03 22:48           ` Ulf Magnusson
2018-05-04  0:05             ` Randy Dunlap
2018-05-08 16:59           ` Ulf Magnusson
2018-05-11  1:22             ` Ulf Magnusson
2018-05-20  3:45             ` Randy Dunlap
2018-05-20  3:51               ` Randy Dunlap
2018-05-20  4:24                 ` Ulf Magnusson
2018-05-20  5:50                   ` Ulf Magnusson
2018-05-20  4:03               ` Randy Dunlap
2018-05-20  4:47                 ` Ulf Magnusson
2018-05-20  5:13                   ` Ulf Magnusson
2018-05-21  2:45                   ` Randy Dunlap
2018-05-21  3:33                     ` Ulf Magnusson
2018-05-21  3:47                       ` Randy Dunlap
2018-05-22 10:18                         ` Ulf Magnusson
2018-05-25 22:06                           ` Randy Dunlap
2018-05-20  7:51                 ` Ulf Magnusson
2018-05-21  2:22                   ` Randy Dunlap
2018-05-20  6:03               ` Ulf Magnusson
2018-05-14 16:58     ` Pavel Machek
2018-05-14 18:12       ` Ulf Magnusson

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=5768c009-d659-c5d7-ae63-ea041362762d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ulfalizer@gmail.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 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®