The Future of the Vim Project

Re:The Future of the Vim Project by djtango on Thursday August 10, 2023 @07:45AM (#37074872)

I've not tried neovim mostly because I'm hopelessly loyal. curious what features were cut?

[ Parent | on HN ]

Re:The Future of the Vim Project by suprjami on Thursday August 10, 2023 @07:50AM (#37074931)

vim-cscope, which is the only reasonable way to read large C projects like the Linux kernel or BSD

[ Parent | on HN ]

Re:The Future of the Vim Project by umanwizard on Thursday August 10, 2023 @08:20AM (#37075259)

What’s wrong with clangd via lsp?

[ Parent | on HN ]

Re:The Future of the Vim Project by devnullbrain on Thursday August 10, 2023 @09:38AM (#37076024)

n.b. LSP support was the reason cscope support was dropped

[ Parent | on HN ]

Re:The Future of the Vim Project by kps on Thursday August 10, 2023 @09:58AM (#37076232)

For one thing, LSP (last I checked) was still unable to distinguish between read and write.

[ Parent | on HN ]

Re:The Future of the Vim Project by suprjami on Thursday August 10, 2023 @04:17PM (#37081200)

You need to build the project to generate compilation database. I switch around kernel versions far too often for that to be viable.

[ Parent | on HN ]