I think this changed some time ago, but I didn't reported it.
When I'm in sldb and press "v" on one of the stack frames, slime brings up the source file quite nicely in another window. Previously (with xemacs), the offending form would be highlighted, with the cursor in the sldb buffer.
Now, what happens is that the offending form is very momentarily highlighted (in blue). Is my memory wrong, or has this changed?
In any case, it's certainly much nicer if the form were highlighted, even if the cursor is in the sldb window.
Ray
* Raymond Toy [2008-11-01 04:22+0100] writes:
I think this changed some time ago, but I didn't reported it.
When I'm in sldb and press "v" on one of the stack frames, slime brings up the source file quite nicely in another window. Previously (with xemacs), the offending form would be highlighted, with the cursor in the sldb buffer.
Now, what happens is that the offending form is very momentarily highlighted (in blue). Is my memory wrong, or has this changed?
Yes, I changed that.
In any case, it's certainly much nicer if the form were highlighted, even if the cursor is in the sldb window.
The highlighting is occasionally distracting when the highlighted form needs to be edited.
Also, at some point we have to remove the highlighting. Previously the next v command or quitting from the debugger removed the overlays. With temporary highlighting that problem is solved nicely, because the timer does that.
I can restore the old behavior if you feel strong about it.
Helmut.
Helmut Eller heller@common-lisp.net writes:
I can restore the old behavior if you feel strong about it.
I like the flashing, FWIW.
-T.
Helmut Eller wrote:
- Raymond Toy [2008-11-01 04:22+0100] writes:
In any case, it's certainly much nicer if the form were highlighted, even if the cursor is in the sldb window.
The highlighting is occasionally distracting when the highlighted form needs to be edited.
Yes, I've noticed that too.
Also, at some point we have to remove the highlighting. Previously the next v command or quitting from the debugger removed the overlays. With temporary highlighting that problem is solved nicely, because the timer does that.
I can restore the old behavior if you feel strong about it.
Not sure. I guess my problem is that with xemacs, the highlighting is sometimes removed so fast that I don't even see it. Perhaps that's a bug in xemacs. I'll look in to it a bit and see if the highlighting can be on for a bit longer...
Ray
Raymond Toy wrote:
Helmut Eller wrote:
Also, at some point we have to remove the highlighting. Previously the next v command or quitting from the debugger removed the overlays. With temporary highlighting that problem is solved nicely, because the timer does that.
I can restore the old behavior if you feel strong about it.
Not sure. I guess my problem is that with xemacs, the highlighting is sometimes removed so fast that I don't even see it. Perhaps that's a bug in xemacs. I'll look in to it a bit and see if the highlighting can be on for a bit longer...
Oh, I see. If I press v, the form is temporarily highlighted. It's a little annoying that when the file is first loaded, the highlighting happens so fast that I often don't see it, but pressing v highlights it again. That's nice.
Ray
-
Helmut Eller -
Raymond Toy -
Tobias C. Rittweiler