You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
perhaps it's due of my configuration but I can't seem to see the breakpoint when dap started,
while the debugger stopped it shows as expected on the fringe:
but when dape is started the fringe gets hidden, so it makes it hard to know where is the breakpoint
i did quick hack to highlight the current line instead when toggling the breakpoint
It would be nice if you can consider adding that option to highlight the current line instead of just adding it to the fringer
here is my code that does it btw if someone else is looking for it
(defunhighlight-current-line ()
"Highlight the current line using a custom face."
(interactive)
(let ((overlay (make-overlay (line-beginning-position) (line-end-position))))
(overlay-put overlay 'face'highlight-current-line-face)
(overlay-put overlay 'evaporatet)))
(deffacehighlight-current-line-face
'((t (:background"grey80":foreground"yellow")))
"Face for highlighting the current line.")
(defunclear-current-line-highlights ()
"Clear all current line highlights."
(interactive)
(remove-overlaysnilnil'face'highlight-current-line-face))
(defunmy-dape-breakpoint-toggle-and-hl ()
"Add or remove breakpoint at current line."
(interactive)
(if (cl-membernil (dape--breakpoints-at-point)
:key#'dape--breakpoint-type)
(progn
(clear-current-line-highlights)
(dape-breakpoint-remove-at-point))
(progn
(dape--breakpoint-place)
(highlight-current-line))))
The text was updated successfully, but these errors were encountered:
Could you share the logs that dape generate and the other packages that use the fringe and/or margin. I suspect that its related to the other packages that's used.
Are you able to reproduce this independent of the number of breakpoints and where they are placed?
To generate the logs turn on logging with (setq dape-debug t) then share the contents of *dape-connection events* buffer.
Also dape already puts an overlay covering the whole line which can be reused for this purpose. The overlay category was mistakenly removed and is not present in the current elpa version but the latest commit 3a9d35e on master has it.
Sorry, I wanted to take some time to properly figure this out, but it seems to be an issue with my configuration. Nothing in fringe mode is showing when splitting windows, regardless of the fringe-mode setting I use (unless I disable it, but then it uses the margin instead).
The dape-debug variable unfortunately didn’t help and not showing any issue.
I’ll try to bisect further within my configuration to pinpoint the issue.
Feel free to close this issue or keep it open—I’ll update it here if I manage to figure it out for the benefit of other users.
chmouel
changed the title
Cannot see the breakpoint in the fringer when the debugger is started
Cannot see the breakpoint in the fringe when the debugger is started
Dec 9, 2024
perhaps it's due of my configuration but I can't seem to see the breakpoint when dap started,
while the debugger stopped it shows as expected on the fringe:
but when dape is started the fringe gets hidden, so it makes it hard to know where is the breakpoint
i did quick hack to highlight the current line instead when toggling the breakpoint
It would be nice if you can consider adding that option to highlight the current line instead of just adding it to the fringer
here is my code that does it btw if someone else is looking for it
The text was updated successfully, but these errors were encountered: