FS#46362 - [gvim] 7.4.854-2 breaks clang_complete bundle

Attached to Project: Arch Linux
Opened by Jordan Yelloz (jyelloz) - Sunday, 20 September 2015, 16:53 GMT
Last edited by Anatol Pomozov (anatolik) - Saturday, 31 October 2015, 05:33 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I've been using clang_complete for a few years with no problems in vim but the 7.4.854-2 rebuild, most probably due to the ncurses 6.0 upgrade, makes clang_complete unusable in terminal mode.

When running as gvim with an X11 display, this version of gvim works fine with clang_complete. Also, removing the clang_complete vim plugin restores normal C editing.

On my Gentoo system, console vim 7.4.827 built against ncurses 6.0 works fine.

I have previously inquired about this on the forum and one other user confirmed similar problems: https://bbs.archlinux.org/viewtopic.php?id=202590

Additional info:

clang 3.7.0-1
clang-analyzer 3.7.0-1
clang-tools-extra 3.7.0-1
gvim 7.4.854-2
lib32-llvm-libs 3.7.0-1
llvm 3.7.0-1
llvm-libs 3.7.0-1
ncurses 6.0-3
vim-runtime 7.4.854-2

Steps to reproduce:
1. Install vim or gvim package
2. Install llvm and clang
3. Install clang_complete (https://github.com/Rip-Rip/clang_complete) int your vim runtime path
4. Edit a C source file (vim /usr/include/stdlib.h) and the terminal display should be out of control and it should be almost impossible to do anything.
   EdBxl.jpg (48.6 KiB)
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Saturday, 31 October 2015, 05:33 GMT
Reason for closing:  Upstream
Additional comments about closing:  clang bug
Comment by Anatol Pomozov (anatolik) - Monday, 21 September 2015, 14:10 GMT
Could you please also send this question to upstream maillist? https://groups.google.com/forum/#!forum/vim_dev
Comment by Anatol Pomozov (anatolik) - Saturday, 31 October 2015, 05:33 GMT
Per discussion https://github.com/Rip-Rip/clang_complete/issues/453 it is a bug in clang - https://llvm.org/bugs/show_bug.cgi?id=25007

Loading...