From: Daniel Jacobowitz <drow@false.org>
To: Marcelo Taube <mail.marcelo.taube@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Some feedback about the python scripting feature
Date: Wed, 11 Nov 2009 02:00:00 -0000 [thread overview]
Message-ID: <20091110190652.GA16417@caradoc.them.org> (raw)
In-Reply-To: <4AF9B5AE.6070004@gmail.com>
On Tue, Nov 10, 2009 at 08:49:18PM +0200, Marcelo Taube wrote:
> Hello,
> >I don't know if it has completion or automatic indentation, because no
> >version of Python I have installed does either :-) Is this new?
> I am sorry, i guess i was "slightly" wrong.
> The completion is not automatic, someone added it to my working
> environment and i just thought it was part of the default behaiviour.
> But it should be very easy to add to any other environment, i saw
> that the next three lines should do the job:
>
> >>>import rlcompleter
> >>>import readline
> >>>readline.parse_and_bind("tab: complete")
This "works" in GDB... but it doesn't do anything you want it to do.
It changes the tab completion used by the GDB prompt! Whoops.
> In spite of that, i still think that the python shell has advantages,
> there is a difference between having direct response to the commands
> executed in python and having to imagine that the syntax is ok till
> you finish writing all the code. Also mixing the history of lines
> insterted in python context and lines inserted in gdb language is
> kind of bothering, they cannot really be reused.
That should work with the command I showed you, at least to some
extent.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-11-10 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AF898F3.50908@gmail.com>
2009-11-10 8:06 ` Marcelo Taube
2009-11-10 15:12 ` Phil Muldoon
2009-11-10 15:38 ` Tom Tromey
2009-11-10 16:53 ` Daniel Jacobowitz
2009-11-10 20:49 ` Marcelo Taube
2009-11-11 2:00 ` Daniel Jacobowitz [this message]
2009-11-13 21:37 ` scott snyder
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=20091110190652.GA16417@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mail.marcelo.taube@gmail.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