@jayaddison You probably also need to set CFLAGS/CXXFLAGS so that clang also targets the right architecture. Sorry, it's been a while since I worked on this and at the moment, I don't have the time to look into this in detail.

Change formatting mapping from F3 to F2

F3 currently doesn't work properly when using vim in kitty.

Update mapping for recent ddc versions

Add Makefile with a target to run "cargo watch"

Setup a webserver with a basic health check

Add a workflow for tests/fmt/linting/code-coverage

Add a workflow for vulnerability audits

Initial commit

Set the term config before setting the colorscheme

Otherwise, things like termguicolors might not be setup correctly, causing various issues.

Update vim-plug

vim-lsp: Show inline diagnostics at eol and truncate them

Add more kitty specific terminal configuration

These come straight from the kitty documentation.

Does this also need to handle delete? #1398

My understanding is that the delete call is only necessary, because vim would otherwise complain that the property type already exists. The props are always the same, so the delete call would only make a difference if something else sets a property type with the name vim-lsp-reference-highlight which seems unlikely and/or deliberate.