From: Dirk Gouders <dirk@gouders.net>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/1] Emacs-like isearch for mconf.
Date: Thu, 07 Jun 2018 01:03:56 +0200 [thread overview]
Message-ID: <ghvaavv7oj.fsf@lena.gouders.net> (raw)
In-Reply-To: <20180606225259.GY17342@gate.crashing.org> (Segher Boessenkool's message of "Wed, 6 Jun 2018 17:52:59 -0500")
Segher Boessenkool <segher@kernel.crashing.org> writes:
> On Wed, Jun 06, 2018 at 11:58:55PM +0200, Dirk Gouders wrote:
>> @@ -332,6 +332,7 @@ int init_dialog(const char *backtitle)
>>
>> keypad(stdscr, TRUE);
>> cbreak();
>> + raw(); /* Enable CTRL-sequences*/
>
> Is that a good idea? You probably should mention it in the patch
> description, either way.
Thanks for commenting on that. I planned to explicitely mention it in
0/1 when I coded that function call but forgot it when I finally sent
the mail.
Dirk
>
> Segher
prev parent reply other threads:[~2018-06-06 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 21:58 [RFC 1/1] Emacs-like isearch for mconf Dirk Gouders
2018-06-06 22:52 ` Segher Boessenkool
2018-06-06 23:03 ` Dirk Gouders [this message]
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=ghvaavv7oj.fsf@lena.gouders.net \
--to=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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