Re: [Pydev-code] Another good feature to have

[Fabio Z. <fa...@gm...>]

Yeap... I'd do them right away, the problem is that I still don't have what
I need from Eclipse itself for all of it. Actually, according to the Eclips=
e
api, I couldn't even get the input from the console -- fortunatelly, I've
learned how to 'hack' my way into Eclipse ;-)

So, I may be able to do some of your requests, but others will depend upon
the following request I did in the eclipse tracker:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D127501

Cheers,

Fabio

On 2/19/06, Bill Baxter < wb...@gm...> wrote:
>
> Nope.  Last time I asked for something it was the interactive debugging
> console itself, and your response was "it's in the next version already".
> So I thought I'd mention these feature requests here first just in case
> you're already working on it for the next release. :-)
>
> I'll go ahead and submit them to the feature tracker when I get a chance.
>
> --bb
>
> On 2/17/06, Fabio Zadrozny < fa...@gm...> wrote:
> >
> > Hey... Did you already put those as feature requests? It is the best
> > place to put those, otherwise your requests might be 'forgotten' when
> > someone actually has time to go and implement them...
> >
> > Cheers,
> >
> > Fabio
> >
> > On 2/17/06, Bill Baxter < wb...@gm...> wrote:
> > >
> > > Another excellent feature is to have is the ability to postmortem
> > > debug in the console if the app throws an exception.  IPython lets yo=
u do
> > > this by automatically invoking pdb when there's an exception in the p=
rogram,
> > > and the matlab debugger has similar functionality.
> > >
> > > (I mention it because I just noticed that the new 'probe in suspend
> > > mode' feature of pydev doesn't let you do that).
> > >
> > > --bb
> > >
> > > On 2/17/06, Bill Baxter <wb...@gm...> wrote:
> > > >
> > > > Hi there,
> > > >
> > > > On 2/17/06, Fabio Zadrozny < fa...@es...> wrote:
> > > > >
> > > > >
> > > > > - New feature in the debugger: the console is available for
> > > > > probing when
> > > > > in 'suspendend mode'
> > > > >
> > > > > This is a pretty great addition.  How hard would it be to make it
> > > > act more like a full-featured shell?  I.e.,
> > > > - have a promt so you can tell tell that it's waiting for your
> > > > input,
> > > > - respond after just one 'enter' instead of two,
> > > > - print out the value of variables by just typing the variable name
> > > > (instead of having to type "print variable_name")
> > > > - cycle through your command history with keys like up/down-arrow o=
r
> > > > ctrl-up/down-arrow
> > > > - auto-completion of symbols
> > > >
> > > > Ideally it would be nice to just have something like pycrust right
> > > > there in a tab instead of "Console".  Stani's Python Editor has pyc=
rust
> > > > built-in like that, but unfortunately it's not connected in any way=
 to your
> > > > executing program, so it's not so useful.
> > > >
> > > > The ultimate debugger, based on debuggers I'm familiar with, would
> > > > be a hybrid of that in VisualStudio crossed with Matlab.  VisualStu=
dio does
> > > > variable and watches nicely.  It's got a list (several lists actual=
ly) like
> > > > Eclipse's 'Expressions', but you can double click to add a new expr=
ession or
> > > > edit an expression.  Eclipse is pretty close there, just needs a mo=
re
> > > > efficient way to edit the expressions.  The Matlab debugger, on the=
 other
> > > > hand, completely lacks an expression list, but its best feature is =
that when
> > > > you hit a breakpoint, you just have your normal interactive shell p=
rompt
> > > > there with all it's features, plus all your program's state loaded =
in
> > > > memory.  This is an excellent debugging model for a dynamic program=
ming
> > > > language in my opinion.  If there's some error on the current line,=
 you can
> > > > quickly try out a bunch of variations to figure out what the proper
> > > > expression is to get the result you want, using the actual data fro=
m your
> > > > program, without having to cook up a stand-alone test case that cre=
ates data
> > > > similar to what's in your program.
> > > >
> > > > Regards,
> > > > Bill Baxter
> > > >
> > >
> > >
> > >
> > > --
> > > William V. Baxter III
> > > OLM Digital
> > > Kono Dens Building Rm 302
> > > 1-8-8 Wakabayashi Setagaya-ku
> > > Tokyo, Japan  154-0023
> > > +81 (3) 3422-3380
> >
> >
> >
>
>
> --
> William V. Baxter III
> OLM Digital
> Kono Dens Building Rm 302
> 1-8-8 Wakabayashi Setagaya-ku
> Tokyo, Japan  154-0023
> +81 (3) 3422-3380
>