ActiveState Community Site - Comments

new version

shanec — Thu, 03 Jul 2008 22:50:46 +0100

Here's a new version, complete with ability to save selections, deal with unsaved buffers, and open buffers that have been closed.

pushd:

if(typeof(window.ppd)=='undefined'){

    window.ppd = [];
}
var view = ko.views.manager.currentView;

window.ppd.push({

    path: view.document.file ? view.document.file.URI:view.document.displayPath,

    line: view.currentLine,

    pos: view.currentPos,

    anchor: view.anchor

});

if (typeof(window.ppd)=='undefined') {
    window.ppd = [];
}

var view = ko.views.manager.currentView;
window.ppd.push({
    path: view.document.file ? view.document.file.URI:view.document.displayPath,
    line: view.currentLine,
    pos: view.currentPos,
    anchor: view.anchor
});

popd:

if(typeof(window.ppd)=='undefined'){

    window.ppd = [];
}
var os = Components.classes["@activestate.com/koOs;1"].createInstance();
while (1) {

    var m = window.ppd.pop();

    if (!m) break;
    // get the view via the manager

    var v = ko.views.manager.getViewForURI(m.path);

    // no view, maybe an unsaved new file?

    if (!v)

        v = ko.views.manager.getUntitledView(m.path);
    // no view, can we open it?

    if (!v && os.path.exists(m.path))

        v= ko.open.URI(m.path +"#" + m.line);
    if (v) {

        v.makeCurrent();

        v.currentPos = m.pos;

        v.anchor = m.anchor;

        break;

    }

    // we couldn't get a view for this, so go to the next one

}

if (typeof(window.ppd)=='undefined') {
    window.ppd = [];
}

var os = Components.classes["@activestate.com/koOs;1"].createInstance();

while (1) {
    var m = window.ppd.pop();
    if (!m) break;

    // get the view via the manager
    var v = ko.views.manager.getViewForURI(m.path);
    
    // no view, maybe an unsaved new file?
    if (!v)
        v = ko.views.manager.getUntitledView(m.path);

    // no view, can we open it?
    if (!v && os.path.exists(m.path))
        v= ko.open.URI(m.path +"#" + m.line);

    if (v) {
        v.makeCurrent();
        v.currentPos = m.pos;
        v.anchor = m.anchor;
        break;
    }
    // we couldn't get a view for this, so go to the next one
}

> would that re-open the

trentm — Thu, 03 Jul 2008 21:51:28 +0100

> would that re-open the file on calling:
>
> ko.open.URI()
>
> If I had closed?

Yes.

Nice!

IRC — Thu, 03 Jul 2008 20:55:57 +0100

Thanks guys. This is a great starting point. I like the view.displayPath suggestion -- would that re-open the file on calling:

ko.open.URI()

If I had closed? That's something that SlickEdit would do as you traversed backwards through the stack.

Or you could just save the

trentm — Thu, 03 Jul 2008 20:53:06 +0100

Or you could just save the view.displayPath and the line number and use

ko.open.URI(displayPath + "#" + lineNumber);

No reference to the view.

side affects

shanec — Thu, 03 Jul 2008 20:48:17 +0100

Btw, that is a quick hack, and it has problems. Keeping a reference to a view will cause problems if you have pushed a position onto the stack, then close the view. A third macro could trigger on file closing to ensure that the ppd array does not contain the view being closed.

pushd/popd

shanec — Thu, 03 Jul 2008 20:46:01 +0100

Here's a simple pushd/popd implementation, if I understand the required functionality correctly. It consists of two seperate macro's that need to be added to the toolbox. You can then bind keys to the macro's. I haven't tested this deeply, but seems to work.

pushd:

if(typeof(window.ppd)=='undefined'){

    window.ppd = [];
}
window.ppd.push({

    view: ko.views.manager.currentView,

    position: ko.views.manager.currentView.currentPos

});

if (typeof(window.ppd)=='undefined') {
    window.ppd = [];
}

window.ppd.push({
    view: ko.views.manager.currentView,
    position: ko.views.manager.currentView.currentPos
});

popd:

if(typeof(window.ppd)=='undefined'){

    window.ppd = [];
}
var m = window.ppd.pop();

m.view.scimoz.currentPos = m.position;

m.view.makeCurrent();

if (typeof(window.ppd)=='undefined') {
    window.ppd = [];
}

var m = window.ppd.pop();
m.view.scimoz.currentPos = m.position;
m.view.makeCurrent();

Thanks shanec. I just tried

IRC — Thu, 03 Jul 2008 20:25:36 +0100

Thanks shanec.

I just tried playing around with transient marks and they're not quite what I'm looking for. They don't seem to work between files:

If I set transient mark 1 in file 1 and transient mark 2 in file 2 then move to file 3 and select Code -> Marks -> Move to Previous Mark it doesn't take me back to the mark 2 in file 2. Pity.

Bookmarks suffer the same problem: they only work within a file.

This is definitely a step closer to what I'm looking for. I can see how to implement a macro that does what I want. If transient marks worked between files:

push_method_macro:
- set transient mark
- goto definition

pop_method_macro:
- move to previous mark

Or if bookmarks worked between files:

push_method_macro:
- set bookmark
- goto defintion

pop_method_macro:
- previous bookmark
- unset bookmark

re: interactive shell

ToddW — Thu, 03 Jul 2008 20:09:00 +0100

The logLevel setting is just to control how verbose the dbgp client internals are, they do not affect the debugger operation (or should not).

When you hit a breakpoint, i.e. on "client.brk()", you can enter the interactive mode by the following methods:
* using the menu "Debug->Interact"
* on the debugging tab "Debug: ...", there is an ">>" icon, which you can press to enter the interactive shell mode

Note: The stdout handle is protected by wsgi, so normal interaction like printing variables will not work in the expected manner. You can do something tricky like "sys.stdout = sys.stderr" and then general stdout goes to stderr, which is visible in the Komodo interact console.

Also, you should be able to see all the local variables in the "Locals" tab on the left side of the debugger tab and examine the contents.

Is that what your after?

Cheers,
Todd

Two possibilities...

shanec — Thu, 03 Jul 2008 19:50:07 +0100

Komodo has transient marks, which may provide a usable alternative to pop/push marking. See the code->marks menu. There is also a go to definition available, in the code menu and the buffer context menu. These are all bind-able to keys if they are not already bound.

Todd, I get the exact same

wyattbiker — Thu, 03 Jul 2008 19:40:55 +0100

Todd,

I get the exact same results except I dont see the Python Shell show up which I thought would show up because of the logging.DEBUG.

I would like it when it stops to use the Python Shell so I can type python commands to help with debugging. Maybe this feature is not available.

How can I start the Python Shell while debugging and have it access the current environment (E.g. application variables)

Thanks

Definitely interested!

trentm — Thu, 03 Jul 2008 19:34:24 +0100

Davide,

We (or at least *I* :) are very interested. I'd love to see Komodo Edit localized (and Komodo IDE too, if things allow) and am willing to help where I can.

I'm not familiar with how the babelzilla process works so I don't know the best way to proceed right now.

All the localization files for Komodo Edit are here (*.dtd and *.properties files):

http://svn.openkomodo.com/openkomodo/browse/openkomodo/trunk/src/chrome/...

There are some possibilities:
- We could create an area in svn.openkomodo.com where localizers would have checkin access to add localization. I'd want that area to be *outside* of the openkomodo/trunk area to make sure there is no interference with the Komodo Edit release process. The natural place is probably starting new addons for language packs under here: http://svn.openkomodo.com/openkomodo/browse/addons
- Or we could look at having some tool to package up the en-US (and other locales) however the babelzilla process needs it to help the localization.

Regarding licensing: What license do babelzilla translations usual fall under? Is it a Creative Commons license or something like that? Are there restrictions on the usage of translations in commercial products?

re: how is the brk statement failing?

ToddW — Thu, 03 Jul 2008 19:28:01 +0100

When testing this code myself, everything seemed to be working as expected. Once the client.brk() call is hit:
* Komodo requests the user to accept the debugger session
* the Komodo debugger is now stopped at the line "a = range(3)"
* stepping over the code (F10) works fine until the third iteration, when the exception is generated, which wsgi then handles in the Python c-compiled mod_wsgi module.
* the browser display a "Internal Server Error" as expected

Is that somehow different from your experience?

Cheers,
Todd

Hi Todd, Understood about

wyattbiker — Thu, 03 Jul 2008 19:14:26 +0100

Hi Todd,

Understood about the brkOnException. I am not talking about the exception though. If you look at my code above its the normal brk that fails.

Thanks

re: exception handling

ToddW — Thu, 03 Jul 2008 18:37:26 +0100

Komodo's exception (brkOnExcept) handling is hooked into the Python interpreter's "sys.excepthook". This "sys.excepthook" code is not reached by the interpreter though as wsgi is handling the exception before it gets there.

Thus Komodo does not get any feedback of an exception, nor does it get any further feedback from wsgi... (this is likely in the wsgi Python binary module, so there is no possibility to debug this part).

If you run the same wsgi code without the Komodo debugger, you should get the same result.

As far as I can see, there would need to be specific hooks added in to the wsgi module to handle the debugging of exceptions.

Cheers,
Todd

Hi Todd,

wyattbiker — Thu, 03 Jul 2008 16:00:14 +0100

Hi Todd,

Now it doesn't crash on the client.brk, but a) it doesn't open the Interactive Shell b) if I single step crashes the debugger on the 3rd iteration of the code below insteaqd of producing error.

# Single steps but crashes debugger on 3rd iteration when called externally
client.brk(host="localhost", port=9000, logLevel=logging.DEBUG)
a = range(3)
for i in a:
    print a[i+1]

Here is my version of Komodo that I upgraded to last week.
Komodo IDE, version 4.4.0, build 20211, platform win32-x86.
Built on Mon Jun 23 17:34:19 2008.

Thanks,