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
It can be difficult to read code, especially large regions of code, that have an error overlay applied. AFAIK, Emacs does not provide a command for removing overlays, so one needs to M-: (delete-all-overlays) RET to remove the error. This is a hassle. I've currently bound this procedure to C-x C-M-e:
Are you talking about the compilation error message? If so it's only one in the whole buffer and #690 deletes it once you modify the region. I have been using it for a day now and it feels pretty right. Alternatively it can be deleted when the pointer enters the error region or on a timeout. I am a bit inclined towards deleting it on entering. I will try it today.
It turns out that point-entered hook is a text and not an overlay property. So sorry, it's too complicated.
As we are on it, I think CIDER should blink the region when jumping to an error and don't leave an overlay at all. This is precisely how comilation in emacs works (see next-error-highlight). Unfortunately cider is not quite integrated with emacs next-error functionality. I plan to look more comprehensively into this issue at the end of the week.
It can be difficult to read code, especially large regions of code, that have an error overlay applied. AFAIK, Emacs does not provide a command for removing overlays, so one needs to
M-: (delete-all-overlays) RET
to remove the error. This is a hassle. I've currently bound this procedure toC-x C-M-e
:The text was updated successfully, but these errors were encountered: