The current frame after sly-eval-buffer and sly-compile-and-load-file

[hww]

Which values control the current frame (cursor focus) after debugger popped up.

As I can see in the doom emacs the sly-eval-buffer does not change current frame if debugger popped up
But with vanilla emacs the sly-compile-and-load-file does not change current frame if debugger popped up

So how I can make equal behavior for debugger in any emacs configuration?

[joaotavora]

evaluating and compiling code usually happens in a separate thread, and has no relation to whether a debugger is active or not. I don't understand the differences between doom and vanilla emacs, but I don't use doom. Maybe you could explain what you are trying to do.

[joaotavora]

I don't understand the problem, sorry. Are you evaluating a buffer that has a Lisp expression that causes an error when evaluated? If so, then I think if doom emacs and vanilla emacs are not doing the right thing, then the fault is with doom emacs, or with your configuration. I don't use either of those, so maybe someone else can help you.

[hww]

With doom emacs, evaluating the buffer with error will open debugger frame, but keep focus on source code (see image below).
I believe the doom configuration (which by default uses sly) did not set correctly a value which control this behavior. If there is no such value in the sly then there is a deeper problem with doom emacs. And I should avoid to use it.

With same setup the slime works correctly -- it change focus to the debugger.

[joaotavora]

These values are generally in Emacs, not Sly. But, again, I don't know exactly what you are doing because you have not described exactly. And exact descriptions matter. In other words, if there is indeed a problem and the problem is not in your configuration, you should do the work of coming up with a minimal reproducible example (see https://stackoverflow.com/help/minimal-reproducible-example) so that others can witness the problem by themselves, analyze it, and recommend fixes. Else we're just wasting each other's time here.

[hww]

Ok. I will switch to the slime then. Thank You.

[joaotavora]

yes, switch to the slime, and good the luck

[monnier]

In the Doom Emacs the function `sly-eval-buffer` does not switch to debugger frame -- the focus stays in the source buffer. I want to make it work correctly.

Frame focus is a notoriously messy part of Emacs's behavior. In large part this is because it's not fully under the control of Emacs but depends also on the window manager. You should probably report this as a bug in Doom Emacs as well: where the bug lies is not obvious at all based on the info you give, and we'll need someone familiar with Doom (and/or its Sly config, if any) to help find the origin of the problem.

[hww]

Ok. Thank You. I will report it at the DOOM project team. N.P.

[joaotavora]

I'm almost certain that it's not a frame focus issue, but rather window selection issue. SLY has window selection code, but without a reproduction recipe, we can't know what's happening. As far as I understand everything works ok in "vanilla Emacs".

[hww]

Right, there are no problems with vanilla.