Bug report: No focus on debugger after REPL wrong evaluation + Enter needs to be typed twice

[Marcio Mazza]

In the REPL view, when some problem activates the debugger, although a
default option is selected, the list of options in the debugger has no
focus (in GUI terms: http://en.wikipedia.org/wiki/Focus_(computing) ).

That means it is initially impossible to choose an option using the
keyboard, neither by typing the option number ("0", "1", ...) nor
using the up and down arrows.

After clicking anywhere in the debugger with the mouse, the debugger
list naturally receives focus. Then:
* it is possible to type the number of the option (0, 1, ...) and
that option is activated; and
* it is possible to use the up and down arrows to select an option, BUT
it is necessary to type "Enter" TWICE (and not just once) for
that option to be activated (a little sub-bug).

One bad consequence of this behaviour is that it is mandatory to use
the mouse to use the debugger.

(My environment: Cusp 1.0.414, Eclipse 3.5.0, Ubuntu Linux.)

[Marcio Mazza]

After some experimenting with Cusp, I consider this bug the worst
usability related I noticed. I really need to be able to go on without
the mouse.

Temporally, it would suffice for me if I simply could disable this
debugger and get the simple textual REPL feedback instead.

[Phil Marneweck]

One can also not copy any/all of the debugger out put which is a pain
when you want to show the output to some one else via an email or such.

Maybe even worse for me is not having a key sequence to repeat repl
input. You have to click on the history button then click in the window
that pops up. Thats a real productivity killer.

[Phil Marneweck]

My appologies I did some scratching around and found that Ctrl + N and
Ctrl + P does the job...

[Gorsal]

Have you tried looking under Lisp Options under miscellaneous. Alt+I,
first, should switch to the debugger, although i have noticed some bug
about not being able to use down arrows though you can use numbers (or
is it the opposite?) There's also an option under the misc to
automatically move to the debug thing. Check it out. I also found this
was an issue for me when i did some code changes. Of course, you
would have to download the jasko.tim.lisp version i released which you
probably don't want to do until i fix some other issues with it. Phil,
does alt+i switch to the debugger and can you choose to automatically
switch to it? I have other course checked these things before but just
to make sure.

[Gorsal]

Also of interest might be Alt+J. Do this in an editor and it will take
the nearest top-level (in-package) statement and switch to that
package if it is loaded. press it again and it will switch back to the
previous package. I think there is also an option under misc. to
always evaluate/macroexpand in the curren toplevel package of the
source editor you are in.

[Phil Marneweck]

Alt + I does switch to the debugger IF you DONT have "Auto focus on
Debugger" switched ON (ticked).

If you switch "Auto focus on Debugger" ON Alt + I does not work.

"Auto focus on Debugger" does not switch focus to the debugger
automatically for me.


Once I have switched to the debugger using "Alt + I" I can use the up
and down arrows to navigate that window but I cant seem to find a key
command that would expand the backtrace information.

I would have expected that the left and right arrows or "enter/return"
would have closed and opened backtrace detail...or something like that.

[Marcio Mazza]

Personally, I remapped those to Ctrl+Up and Ctrl+Down (which I think would be better defaults).

2009/10/11 Phil Marneweck <zar...@global.co.za>

[Marcio Mazza]

I cannot find Alt+I, Alt+J nor the option "Auto focus on Debugger" anywhere.

Please, which version are you both talking about?

I'm using 1.0.414 which was "early" released in this message from Jasko:
http://groups.google.com/group/cusp-development/msg/47fad4979ad1a02c

2009/10/11 Phil Marneweck <zar...@global.co.za>

[Phil Marneweck]

I am using jasko.tim.lisp_1.0.414.zip (Oct 8) found on
http://groups.google.com/group/cusp-development/files


Direct link:

http://cusp-development.googlegroups.com/web/jasko.tim.lisp_1.0.414.zip?gda=9ZPiw0wAAAAVXXfNEm-HQJR-XCWx0FG_DzDenr7vN7_3FSvLKpcZOiW9NhuMWTOXzDOFNhR3SOmpqDBY_JHxqBglGZYy66fz_Vpvmo5s1aABVJRO3P3wLQ

[Seth Burleigh]

We’re atalking about the jasko.tim.lisp zip file under the group files on the homepage of this website. However, I would wait until I submit some new code which fixes the features you wanted (debugger)>

[Gorsal]

You can download it at
http://groups.google.com/group/cusp-development/files
download jasko.tim.lisp(2).zip or whatever i downloaded the latest of.

[Marcio Mazza]

Thank you Seth and Gorsal.

It would be fine if we were able to know what are each of those files at
http://groups.google.com/group/cusp-development/files

I guess Google Groups do not allow file descriptions. If that is so, I would suggest that we try to give a clue about the file's content, however briefly, in it's name.

2009/10/14 Gorsal <se...@tewebs.com>

[Gorsal]

Now the newest version will be named current-cusp-plugin-vx.x.x. The
previous version will be named previous-cusp-plugin-vx.x.x
Just ignore the other files.

[Phil Marneweck]

Thanx will test later today still working on some other stuff...

[Marcio Mazza]

Finally, I decided to try to debug Cusp...

I have moved the line
  debugTree.setFocus();
from
  void jasko.tim.lisp.views.ReplView.DebugState.fillDebugTree(boolean print)
to
  void jasko.tim.lisp.views.ReplView.DebugState.activate()
to be called only after the debugView is shown.

This apparently solves the focus problem.

I attach a patch file to be used against the root of the project:
Repository Root: http://cusp.googlecode.com/svn
Revision: 428

(My environment: Cusp 1.0.414, Eclipse 3.5.0, Ubuntu Linux.)

2009/10/10 Marcio Mazza <marci...@gmail.com>

[Gorsal]

Hey, I assume you're trying to patch the original cusp, right, not the
fork? If you're determined to work on this version, I can provide the
cusp code I've made so far minus the clojure parts. Most of the code
changes so far have been java as I first had to learn the intricacies
of it. Only now am i determined to start developing parts of it in
clojure. Let me know. Thanks!

[Marcio Mazza]

Oh, that would be really fine.
If you can also mention whatever new features and bug fixes you made, that would be very useful.

2009/10/19 Gorsal <se...@tewebs.com>