1
General (but related to Code::Blocks) / Re: patch for the autotools build to work with Msys2/MinGW32
« Last post by Grit Clef on Today at 06:30:38 am »Good! Simple but useful for me.
Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!
Hi, thanks.
I just tried this latest revision.
There is still one issue, clangd error and breakpoint happens in the same line. Still they have the same size. One is circle, and the other is a square.
I can't reproduce a clangd warning easily.
see below image shot:
I prefer Pecan's method "I can change it to a small right pointing arrow that fits inside any other marker".
Commit HEAD 13521:
Clangd_client warning margin marker changed to a small right pointing arrow.
I prefer Pecan's method "I can change it to a small right pointing arrow that fits inside any other marker".
meaningful workflow during editing/debugging should be the guide to visual appearance.
@ollydbg: What is your take on this? For how long do both markers compete for the spot in your projects? Do either markers last that long that it really matters?
When debugging, the current PC (program counter) marker is covered by the clangd_client marker.
Fixed HEAD 13520
The clangd warning/error margin markers are remove when the debugger starts up.
Hi, pecan, thanks for the fix.
When I'm not debugging, I try to set some breakpoints, and I see the clangd's marker still covers the breakpoint's marker.
So, I think we still need to find a way to show both of the above mentioned markers.
EDIT:
Maybe, make the clangd_client's marker a big smaller?
@Pecan: Thank you.
@ollydbg: Maybe it is bit of motivation to change the code for good, so that clangd does not show markers anymore -- at least if it is your own code you are free to change. The smaller a marker is, the harder it is to hit it with the mouse. Alternatively one might consider toggling the markers somehow.