I love this thing so don't take the following as a complaint, but rather as feedback that might be useful to the inmplementors: I just had an experience that was a little bit frustrating. I did a show threads command which changed the bottom pane(debug out) into the threads buffer. No problem. I looked at the threads and that was all nice. Then I wanted to do an operation that output to the debug out buffer. For example I did a display local variables. I expected the debug out buffer to replace the threads buffer in the bottom pane. It didn't, which is ok, no great hardship, I could always do a C-x b and get it back, which works fine if it happens to be the next buffer in the ring. It wasn't so then I had to do a C-x C-b which displayed in the source window, I then selected the debug out buffer and it was displayed in the wrong pane. So now things are pretty out of wack. I don't have my source buffer, etc. IOW, it took some time out of my workflow to get things back to where I needed them. If I could have done one of the following, things would have been smooth: When a display blah is done, and the bottom pane is occupied by the *threads* pane or whatever other buffer might be there, put the debug out buffer back in the bottom pane. Or give the debug out buffer an easy-to-remember and easy-to-type name so that one can do a C-x b and type it in easily, ie., "debugout*, or *do* or whatever. Thanks.
begin:vcard n:Johns;Rich x-mozilla-html:TRUE org:Trajecta version:2.1 email;internet:[EMAIL PROTECTED] title:Software Designer note:[EMAIL PROTECTED] x-mozilla-cpt:;0 fn:Rich Johns end:vcard
