Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Code completion using LSP and clangd
blauzahn:
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?
ollydbg:
--- Quote from: blauzahn on May 14, 2024, 09:26:51 pm ---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?
--- End quote ---
I prefer Pecan's method "I can change it to a small right pointing arrow that fits inside any other marker".
I use C::B for my daily work, and some of the clangd_client warnings come from third part library's source code, so those warnings will last for a long time.
Thanks.
Pecan:
--- Quote from: ollydbg on May 15, 2024, 12:03:28 am ---
I prefer Pecan's method "I can change it to a small right pointing arrow that fits inside any other marker".
--- End quote ---
Commit HEAD 13521:
Clangd_client warning margin marker changed to a small right pointing arrow.
ollydbg:
--- Quote from: Pecan on May 15, 2024, 06:10:46 pm ---
--- Quote from: ollydbg on May 15, 2024, 12:03:28 am ---
I prefer Pecan's method "I can change it to a small right pointing arrow that fits inside any other marker".
--- End quote ---
Commit HEAD 13521:
Clangd_client warning margin marker changed to a small right pointing arrow.
--- End quote ---
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:
Pecan:
--- Quote from: ollydbg on May 16, 2024, 02:45:26 pm ---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:
--- End quote ---
Same with legacy CC . It's always been that way.
I'd have to change legacy CC use of cbEditor to do anything about that.
I'd prefer not changing legacy CC if I can avoid it.
For me, an obvious code error (red square) should be corrected before debugging occurs. When the error is corrected, the debugger breakpoint circle appears.
Also you can always use the "Debugging windows" icon (top line main menu, left of info icon) to see your breakpoints listed.
I really do not know how to solves this situation without changing the legacy CC interface (cbeditor) for current users.
Legacy CC is used way more than clangd_client.
Suggestions accepted.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version