From: Eli Zaretskii <eliz@gnu.org>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: palves@redhat.com, tom@tromey.com, gdb@sourceware.org
Subject: Re: Readline on Windows (WAS: Re: [PATCH v2 0/2] MI: Add new command -complete]
Date: Mon, 11 Mar 2019 14:43:00 -0000 [thread overview]
Message-ID: <835zsp5v5d.fsf@gnu.org> (raw)
In-Reply-To: <8b116a2bf5f9d7f60c64affab76d72a85b150a11.camel@fit.cvut.cz> (message from Jan Vrany on Mon, 11 Mar 2019 08:45:55 +0000)
> From: Jan Vrany <jan.vrany@fit.cvut.cz>
> Cc: palves@redhat.com, tom@tromey.com, gdb@sourceware.org
> Date: Mon, 11 Mar 2019 08:45:55 +0000
>
> Ah, sorry, I should have been more clear. I meant that it does not work
> for me EVEN when on standard console so I doubted it would work better over
> pipes much better.
>
> All the problems I described do happen when using standard console and never
> worked no matter which GDB I used (compiled by myself or by some third party).
That's strange. Do you have some curses library installed, and if so,
does it get linked into GDB?
> > Do you perhaps have a ~/.inputrc file, or some other local
> > customization, which might affect how Readline works?
>
> Not that I know of. There's no ".inputrc" nor "inputrc" on my Windows filesystem.
> I believe GDB compiled by myself uses the readline that comes with GDB.
The .inputrc file doesn't come with Readline, it is a user init file
that you yourself can create to customize how input through readline
works.
I compile GDB myself as well, also with its bundled readline, I use
GDB in the Windows console all the time, and I have no problems like
the ones you describe. Very strange.
next prev parent reply other threads:[~2019-03-11 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87imynm3ia.fsf@tromey.com>
[not found] ` <20190128124101.26243-1-jan.vrany@fit.cvut.cz>
[not found] ` <87pnrmnolt.fsf@tromey.com>
2019-02-21 16:05 ` [PATCH v2 0/2] MI: Add new command -complete Jan Vrany
2019-02-26 19:49 ` Tom Tromey
2019-02-27 10:41 ` Jan Vrany
2019-02-27 20:41 ` Pedro Alves
2019-02-28 10:18 ` Jan Vrany
2019-03-05 20:53 ` Pedro Alves
2019-03-06 15:09 ` Jan Vrany
2019-03-06 15:45 ` Eli Zaretskii
2019-03-06 16:37 ` Jan Vrany
2019-03-06 17:36 ` Eli Zaretskii
2019-03-11 8:46 ` Readline on Windows (WAS: Re: [PATCH v2 0/2] MI: Add new command -complete] Jan Vrany
2019-03-11 14:43 ` Eli Zaretskii [this message]
2019-03-12 11:43 ` Jan Vrany
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=835zsp5v5d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
--cc=palves@redhat.com \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).