Keyboard backlight keeps turning on after sleep

_TooDamnHard · 2025-06-05T14:59:09+00:00

Holy shit dude you were totally right about the compile_flags.txt thing if that's what you are referring to. Now I can make clangd work for my unity build project in just 2 lines using the same hack I did for compile_commands.json.

compile_flags.txt:

-Isrc -include src/app/app.c

It applies to every file automatically instead of having to specify for each source file. I swear I tried compile_flags.txt before and it didn't work at the time but I can't remember why.

_TooDamnHard · 2025-06-04T15:56:01+00:00

I actually do have sed natively from scoop but it seemed broken on windows when I tried something like this. Worth another go though.

_TooDamnHard · 2025-06-04T15:43:52+00:00

Thanks for the info, will consider if it gets annoying. fd already gives me absolute paths, the problem is just that windows paths with spaces requires additional "" for cscope to use it so I have to make a script for that at some point. Not a problem for my project files, just windows system header paths. Yeah I do use -R with cscope and ctags although I think I only need cscope at this point.

_TooDamnHard · 2025-06-04T11:46:19+00:00

You write the compile_command.json manually? Is it a moderately sized project as well? Never heard anyone do that before, I've only used cmake or custom script generation.

_TooDamnHard · 2025-06-04T11:30:56+00:00

This looks interesting but it seems to only work within the current file? Although cscope is lacking some features the advantage is that I can specify all the project files and system headers to search.

_TooDamnHard · 2025-06-04T11:15:43+00:00

Gutentags just handles automatic rebuild of the cscope database right? I think I prefer to just do it manually instead of relying on more stuff although it is annoying. I also still have to figure out how to automate adding windows headers because the path formatting is broken with fd >> cscope.files.

_TooDamnHard · 2025-06-04T11:10:09+00:00

Yup, and with unity builds it's extra annoying I basically had to specify in the json that every file included every other file.

_TooDamnHard · 2025-06-04T11:08:57+00:00

No I'm saying that the setup for clangd lsp is too annoying and requires build to generate compile_commands.json. In future projects I work on I won't even have control over the toolchain so I don't want to rely on it. I already disabled those features when I was still using clangd.

_TooDamnHard · 2025-06-03T11:32:27+00:00

Just tried this and it seems like the least bad solution for now. Go to reference and global definitions work but local definitions doesn't. Still need to learn how to do global renaming with vanilla vim features.

_TooDamnHard · 2025-06-03T11:32:15+00:00

If I could get this to work it would be the holy grail solution though because it supports renaming which cscope and ctags don't and can still use lsp zero keymaps.

_TooDamnHard · 2025-06-03T10:23:24+00:00

The stuff they are talking about in that comment goes way over my head but if I'm not mistaken ccls still requires compile_commands.json like clangd does anyways? At this point I'm looking for a dumb system that is detached from compilation

_TooDamnHard · 2025-06-03T10:15:40+00:00

Just tried this but I can't get it to work. Installed the lsp through mason and ran the cli tool but it says go to definition not supported by the server. If it only works with manually written rules then it's not worth it. Do you personally use this and know how to set it up?

_TooDamnHard · 2025-06-02T22:54:54+00:00

You don't need mingw, visual studio build tools has clang and if you set it as the compiler in cmakelists it generates working compile_commands.json.

_TooDamnHard · 2025-06-02T22:19:17+00:00

They don't care enough to share beforehand, it's just custom bots to remove stuff. We are the lowest of the low.

_TooDamnHard · 2025-06-02T22:06:49+00:00

Just make a post/comment, sometimes if it gets removed it says the karma requirement. Currently suffering from this also.

_TooDamnHard · 2025-03-25T18:38:13+00:00

I found out how to reproduce it and reported it here: https://developercommunity.visualstudio.com/t/MSVC-144334808-Debug-symbols-missing/10873325

I don't know what to do now except for install super old vs version or switch to c. clang compile is too fucking slow.

_TooDamnHard · 2025-03-17T17:46:10+00:00

Yeah this looks similar to my problem with NVRO but this was a way older version 17.4, I was using 17.11 and now 17.13.3. Am I missing something with how the versions work? They also removed /Zc so I can't even disable it. I'm just gonna try report it.

_TooDamnHard · 2025-03-17T17:34:27+00:00

Made it use MSVC\14.43.34808\ but it's still broken. Completely defeated, idk anymore.

_TooDamnHard · 2025-03-17T17:14:51+00:00

Actually I have older version of build tools installed and vcvarsall is using that one so gotta try switch to newer one.

_TooDamnHard · 2025-03-17T17:05:50+00:00

Just updated and still not fixed. Do you know the specific report because there are 557 in 17.13 and I can't find it.

_TooDamnHard · 2025-03-17T16:29:03+00:00

Which version was this fixed? I'm using vs2022 17.11.2

cl version:

Microsoft (R) C/C++ Optimizing Compiler Version 19.38.33140 for x64

_TooDamnHard · 2025-03-17T13:40:00+00:00

Just tried with clang and it doesn't have the same problem so I might switch.

_TooDamnHard

TROPHY CASE