All of lore.kernel.org
 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: Sun, 20 May 2018 19:22:29 -0700	[thread overview]
Message-ID: <63c7222b-b324-2cca-b4f9-3e07cd59780b@infradead.org> (raw)
In-Reply-To: <CAFkk2KStOwHKmFLpNVA1GNscvi-0wihJVM_uaYNemoy6XWDxiQ@mail.gmail.com>

On 05/20/2018 12:51 AM, Ulf Magnusson wrote:
> On Sun, May 20, 2018 at 6:03 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 05/19/2018 08:45 PM, Randy Dunlap wrote:
>>> On 05/08/2018 09:59 AM, Ulf Magnusson wrote:
>>>> Hello,
>>>>
>>>> I've added incremental search for jumping directly to a symbol now.
>>>> Regular expressions are supported as well.
>>>>
>>>> Some screenshots below:
>>>>
>>>> https://raw.githubusercontent.com/ulfalizer/Kconfiglib/screenshots/screenshots/ss10.png
>>>> https://raw.githubusercontent.com/ulfalizer/Kconfiglib/screenshots/screenshots/ss11.png
>>>> https://raw.githubusercontent.com/ulfalizer/Kconfiglib/screenshots/screenshots/ss13.png
>>>>
>>>> The last screenshot shows how things might look after you jump to a
>>>> symbol. The jumped-to symbol wasn't visible in this case, so show-all
>>>> mode was turned on automatically.
>>>
>>> Hi Ulf,
>>>
>>>
>>>
>>> Hm, OK, I used the trick that you supplied a few weeks ago and I have the UI now.
>>>
>>>     ARCH=x86 SRCARCH=x86 KERNELVERSION=`make kernelversion` \
>>>         Kconfiglib/menuconfig.py
>>>
>>> so yes, a real Makefile target would be nice. :)
>>
>> I want to see all kconfig symbols that end with "_DEBUG" (so excluding
>> _DEBUGFS).  Using:
>>
>> /.*_DEBUG$
>>
>> shows me 6 symbols:
>> ATH9K_COMMON_DEBUG
>> DVB_B2C2_FLEXCOP_DEBUG
>> HAVE_DMA_API_DEBUG
>> IP_DCCP_TFRC_DEBUG
>> NFS_DEBUG
>> PM_SLEEP_DEBUG
>>
>> so where are the other (approx.) 176?
>> see:
>> $ find . -name Kconfig\* | xargs grep "config.*_DEBUG$" | grep -v \.orig | wc
>>     182     364    9179
>>
>>
>> Anyway, something for you to look at. :)
>>
>> --
>> ~Randy
> 
> I changed it to search the symbol name and the prompt separately:
> https://github.com/ulfalizer/Kconfiglib/commit/e0905818ef376c977d0a4540ea72d61b8f554bb5
> 
> Should work the way you expected now. It's more intuitive for the prompt too. :)

Yes, and a user shouldn't need to know about the implementation details.

> Can just do 'debug$' by the way. No '.*' required.

Yep, I had already figured that out.

thanks,
-- 
~Randy

  reply	other threads:[~2018-05-21  2:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  0:57 [ANNOUNCE] Kconfiglib menuconfig implementation 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
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 [this message]
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=63c7222b-b324-2cca-b4f9-3e07cd59780b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.