From: Dirk Gouders <dirk@gouders.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [RFC v7 1/1] mconf: global i-search in menu prompts
Date: Tue, 19 Jun 2018 21:43:34 +0200 [thread overview]
Message-ID: <ghfu1isgt5.fsf@lena.gouders.net> (raw)
In-Reply-To: <7a371124-007b-f758-44f0-c70c64ff5974@infradead.org> (Randy Dunlap's message of "Tue, 19 Jun 2018 12:34:21 -0700")
Randy Dunlap <rdunlap@infradead.org> writes:
> On 06/19/2018 11:47 AM, Dirk Gouders wrote:
>> Randy Dunlap <rdunlap@infradead.org> writes:
>>
>>> Hi Dirk,
>>>
>>> On 06/17/2018 05:15 AM, Dirk Gouders wrote:
>>>>
>>>> At any time, at most one i-search is active and the navigation path to
>>>> the current menu is displayed in the subtitle, the second line in the
>>>> menu window.
>>>
>>> Nice.
>>>
>>> And the highlight of the current menu item is also nice when TAB is used to
>>> switch to the buttons. As well as toggling the help text based on context.
>>>
>>>
>>>> Navigation example:
>>>>
>>>> To navigate to options concerning NFS file systems, simply type 'n',
>>>> 'f' and 's'.
>>>>
>>>> Hint: use the 'z' key with focus on buttons to search for invisible
>>>> prompts.
>>>
>>> I think what this says is that the 'z' key is a toggle for the display of
>>> some (invisible) prompts. Is that correct?
>>>
>>>
>>>
>>> I reliably (consistently) get a segfault. I have hit it several times.
>>> Here is one way to get it:
>>>
>>> $ make menuconfig
>>> and then enter:
>>> /debug\
>>
>> Hello Randy,
>>
>> thank you for testing and your comments!
>>
>> Concerning the segfault, I already have a version 8 prepared but wanted
>> to do more testing before disturbing people, again.
>>
>> The initialization and operation of the serialized menu was ugly and
>> wrong. I did not notice segfaults so far, but I can imagine the
>> segfaults you noticed are caused by this, because the code you tested
>> did not operate only on propper initialized array elements.
>>
>> Before sending out version 8, I would like to include your other
>> suggestions as well, so could you please try the attached patch if that
>> also produces the segfaults?
>
> Yes, this one is working for me without faults.
Thank you very much.
I will prepare a v8 with your comments on the diff also respected.
Dirk
next prev parent reply other threads:[~2018-06-19 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 12:15 [RFC v7 0/1] " Dirk Gouders
2018-06-17 12:15 ` [RFC v7 1/1] " Dirk Gouders
2018-06-19 17:16 ` Randy Dunlap
2018-06-19 18:47 ` Dirk Gouders
2018-06-19 19:34 ` Randy Dunlap
2018-06-19 19:43 ` Dirk Gouders [this message]
2018-06-19 17:43 ` Randy Dunlap
2018-06-19 17:27 ` [RFC v7 0/1] " Randy Dunlap
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=ghfu1isgt5.fsf@lena.gouders.net \
--to=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=segher@kernel.crashing.org \
--cc=yamada.masahiro@socionext.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®