nolange
nolange
Since the "full" support is not ready apparently, I would appreciate if the low-level socket_ops parts could get merged on its own.
The master branch is quite impossible to get to work on debian bookworm. There's no python2 and using pip yielded some broken wxpython libraries. Sorry, don't think those 3 changes...
Well, there is the (default) `Tab` intend and `Shift + Tab` unintend support. I believe those should work, Especially since that **functionality is avaliable if you right-click on a line**...
Not sure if you understood my problem. Those paths are clang's internal headers, not the ones from gcc, see this listing: https://packages.debian.org/bookworm/amd64/libclang-common-15-dev/filelist I get that this will cause big mess...
I use clang as "normal" compiler, so those are the paths that are removed. The problem only exists with a custom built clang-tidy - a full clangsa works, reason being...
I did experience this on 2 systems without touching the configuration, I tried removing `libclang_path`I tried setting it to a sane value. No difference for this issue. If you look...
aint that the first 3 characters (including `.`): `version_str[0:3]` ``` # clang -v Debian clang version 15.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/12 Selected...
> As far as I know the stopping index of a slice is non-inclusive. Yes, and that means 3 characters {0, 1, 2}. Inclusive would be 4. Its a weird...
digged around a bit. I guess the code you linked expects single-digit versions like 3.8.2 trying to extract 3.8. I fixed it for versions >= 4 (changed the versioning to...
Turns out clang will modify the searchpath to include `/usr/lib/llvm-15/bin/../lib` *only* if `libc++.so` is found there, that was the difference between my machines. The one which did not have `libc++-15-dev`...