From: Changbin Du <changbin.du@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Changbin Du <changbin.du@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kconfig/[mn]conf: handle backspace (^H) key
Date: Fri, 29 Mar 2019 08:15:59 +0000 [thread overview]
Message-ID: <20190329081558.u54hczsjheacwvtk@mail.google.com> (raw)
In-Reply-To: <CAK7LNARkTQoAhjk7qPR4Pn0SHKvW4cvSrtC5brATQ2LbsWegtw@mail.gmail.com>
On Fri, Mar 29, 2019 at 04:50:18PM +0900, Masahiro Yamada wrote:
> On Tue, Mar 26, 2019 at 12:16 AM Changbin Du <changbin.du@gmail.com> wrote:
> >
> > Backspace is not working on some terminal emulators which do not send the
> > key code defined by terminfo. Terminals either send '^H' (8) or '^?' (127).
> > But currently only '$?' is handled.
>
>
>
> Shall I fix '$?' to '^?'
> if it is a typo?
>
yes, please. It is a typo, sorry.
>
>
>
> > Let's also handle '^H' for those
> > terminals.
> >
> > Signed-off-by: Changbin Du <changbin.du@gmail.com>
> > ---
> > scripts/kconfig/lxdialog/inputbox.c | 3 ++-
> > scripts/kconfig/nconf.c | 2 +-
> > scripts/kconfig/nconf.gui.c | 3 ++-
> > 3 files changed, 5 insertions(+), 3 deletions(-)
> >
> > diff --git a/scripts/kconfig/lxdialog/inputbox.c b/scripts/kconfig/lxdialog/inputbox.c
> > index 611945611bf8..1dcfb288ee63 100644
> > --- a/scripts/kconfig/lxdialog/inputbox.c
> > +++ b/scripts/kconfig/lxdialog/inputbox.c
> > @@ -113,7 +113,8 @@ int dialog_inputbox(const char *title, const char *prompt, int height, int width
> > case KEY_DOWN:
> > break;
> > case KEY_BACKSPACE:
> > - case 127:
> > + case 8: /* ^H */
> > + case 127: /* ^? */
> > if (pos) {
> > wattrset(dialog, dlg.inputbox.atr);
> > if (input_x == 0) {
> > diff --git a/scripts/kconfig/nconf.c b/scripts/kconfig/nconf.c
> > index a4670f4e825a..ac92c0ded6c5 100644
> > --- a/scripts/kconfig/nconf.c
> > +++ b/scripts/kconfig/nconf.c
> > @@ -1048,7 +1048,7 @@ static int do_match(int key, struct match_state *state, int *ans)
> > state->match_direction = FIND_NEXT_MATCH_UP;
> > *ans = get_mext_match(state->pattern,
> > state->match_direction);
> > - } else if (key == KEY_BACKSPACE || key == 127) {
> > + } else if (key == KEY_BACKSPACE || key == 8 || key == 127) {
> > state->pattern[strlen(state->pattern)-1] = '\0';
> > adj_match_dir(&state->match_direction);
> > } else
> > diff --git a/scripts/kconfig/nconf.gui.c b/scripts/kconfig/nconf.gui.c
> > index 7be620a1fcdb..77f525a8617c 100644
> > --- a/scripts/kconfig/nconf.gui.c
> > +++ b/scripts/kconfig/nconf.gui.c
> > @@ -439,7 +439,8 @@ int dialog_inputbox(WINDOW *main_window,
> > case KEY_F(F_EXIT):
> > case KEY_F(F_BACK):
> > break;
> > - case 127:
> > + case 8: /* ^H */
> > + case 127: /* ^? */
> > case KEY_BACKSPACE:
> > if (cursor_position > 0) {
> > memmove(&result[cursor_position-1],
> > --
> > 2.17.1
> >
>
>
> --
> Best Regards
> Masahiro Yamada
--
Cheers,
Changbin Du
next prev parent reply other threads:[~2019-03-29 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 15:16 Changbin Du
2019-03-29 7:50 ` Masahiro Yamada
2019-03-29 8:15 ` Changbin Du [this message]
2019-03-29 13:50 ` Masahiro Yamada
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=20190329081558.u54hczsjheacwvtk@mail.google.com \
--to=changbin.du@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®