1
General (but related to Code::Blocks) / Re: Project build options - no available tick boxes for Compiler Flags
« Last post by Miguel Gimenez on Today at 01:51:01 pm »Spam reported to moderator.
The new Release 20.03 is out! You can download binaries for Windows and many major Linux distros here .
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.
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.
When debugging, the current PC (program counter) marker is covered by the clangd_client marker.
svn13517: - Clangd_client include "sdk.h" needed for lspdiagresultslog.cpp no matter what clangd says
#include <cmath> // IWYU pragma: keep