Zheng Luo
Zheng Luo
ArchLinux with Gnome3.20.3 ``` ➜ ~ nvim -v NVIM v0.1.5-611-gdcbd1c7 Build type: Dev Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -g -fvar-tracking-assignments -Wconversion -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes...
After two years I switched back to clang_complete from ycm due to its size. What made me upset two years before was that no header file completion had been provided,...
### fuse not found (for Debian/Ubuntu) check if you have installed **libfuse-dev** package NOT **fuse** ### errors during compilation ``` πfs.c: In function ‘pifs_opendir’: πfs.c:258:14: error: cast from pointer to...
- Did you upgrade to latest plugin version?: Yes - Did you upgrade to/compile latest binary? Run shell command `bin/languageclient --version` to get its version number. `languageclient 0.1.160` - (Neovim...
It seems that `ira.set_empty_dst_to_next` always sets dst to the next IRblock even if the original asm block has no destination (because of some break-flow instructions like `RET` or `HLT`). This...
Hi, I created several `stdout_color_mt` and then used then in various threads. When I run `valgrind --tool=helgrind` to detect data race, it reported the following issue: ``` ==2144== Possible data...
``` [repo-ck] SigLevel = Optional TrustAll Server = http://repo-ck.com/$arch ``` 与AUR中的包不同,这个来源包括了大量预编译的CK版内核。然而,这个源下载速度非常糟糕,加之内核一般都比较大,在家中基本无法正常下完内容,希望能建立其的国内镜像。
I'm using vim-clang with deoplete in neovim. Occasionally pressing `.` in `.` will cause the following Error: ``` Error detected while processing function ICComplete..ClangComplete..95_ClangComplete..95_DiagosticsWindowOpen..95_DiagosticsWindowClose: line 18: E16: Invalid range: 3wincmd...
## Environment details - OS: Linux - OS version: Linux 6.7 - node-pty version: The one bundled in VSCode, and I believe it still exists on master ## Issue description...
https://github.com/rust-lang/rust/issues/58599 https://internals.rust-lang.org/t/expose-llvm-atomic-memcpy-in-intrinsics/9466/4 The `volatile_read` here is an questionable operation which depends on internal implementations to synchronize reads with the previous read-acquire on seqlock. Ref: #2