From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org, Nick Roberts <nickrob@snap.net.nz>
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: PATCH: PR tui/2173: Arrow keys no longer works in breakpoint command list
Date: Fri, 21 Mar 2008 21:26:00 -0000 [thread overview]
Message-ID: <20080321212609.GA10522@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20080321212144.GA18716@caradoc.them.org>
On Fri, 21 Mar 2008 22:21:44 +0100, Daniel Jacobowitz wrote:
> On Fri, Mar 21, 2008 at 09:33:11PM +0100, Jan Kratochvil wrote:
> > On Fri, 21 Mar 2008 20:01:51 +0100, Chet Ramey wrote:
> > > I'm looking at the rl_unwind_protect thing a little more closely, and I'm
> > > wondering why you didn't use rl_save_state and rl_restore_state
...
> Thanks. I didn't know about those either. Is there anything
> currently broken with our readline wrapper that needs fixing, though?
I am not aware of any problem.
> If it's working, I would rather leave it alone. We may in the future
> want to really return to the main event loop while we're waiting for
> the user to type, so that we can notice target events in async mode.
> A blocking call to readline is a problem for that.
OK, I was not aware of it.
Regards,
Jan
next prev parent reply other threads:[~2008-03-21 21:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18019.18081.448928.93993@kahikatea.snap.net.nz>
[not found] ` <20070604010633.GA927@caradoc.them.org>
2007-06-05 12:56 ` Nick Roberts
2007-06-05 13:27 ` Daniel Jacobowitz
2007-06-24 15:46 ` Daniel Jacobowitz
2007-06-24 21:55 ` Nick Roberts
2007-07-01 22:38 ` Daniel Jacobowitz
2007-07-03 1:28 ` Nick Roberts
2007-07-03 3:03 ` Daniel Jacobowitz
2007-07-03 15:39 ` Daniel Jacobowitz
2007-06-26 13:49 ` Jan Kratochvil
2007-06-26 14:33 ` Daniel Jacobowitz
2008-03-21 20:34 ` Jan Kratochvil
2008-03-21 21:22 ` Daniel Jacobowitz
2008-03-21 21:26 ` Jan Kratochvil [this message]
2008-03-21 21:41 ` Daniel Jacobowitz
2006-11-21 21:32 H. J. Lu
2006-11-28 16:53 ` Daniel Jacobowitz
2006-11-28 17:09 ` H. J. Lu
2006-11-28 17:15 ` Daniel Jacobowitz
2006-12-02 18:44 ` H. J. Lu
2006-12-02 18:55 ` Daniel Jacobowitz
2006-12-02 18:59 ` Joel Brobecker
2006-12-02 19:17 ` Chet Ramey
2006-12-02 19:09 ` Chet Ramey
2006-12-02 22:15 ` H. J. Lu
2006-12-02 23:06 ` Daniel Jacobowitz
2006-12-03 5:25 ` Chet Ramey
2006-12-17 23:46 ` Jan Kratochvil
2006-12-18 20:09 ` Chet Ramey
2006-12-19 23:20 ` Jan Kratochvil
2006-12-26 6:00 ` Jan Kratochvil
2007-01-03 21:46 ` Daniel Jacobowitz
2007-01-03 21:47 ` Daniel Jacobowitz
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=20080321212609.GA10522@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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