Add whichkey descriptions

[luqasn]

including scripts to generate them.

I am not too happy that I had to create separate *.vim files that I cat together, but unfortunately you can't easily include/source sibling files (a.k.a relative to current file) in vimscript, and ideavim seems to lack workaround options I found for 'normal' vim.

Some group descriptions are still missing, e.g. for <leader><tab>. I think that one is a idea-which-key bug.

[cufarvid]

Thanks for this work! For managing updates - would this be run manually when we notice significant LazyVim changes?

[mikeslattery]

Nice.

Given the number of moving parts, it seems like this should produce a downloadable artifact (.ideavimrc). I am not sure users are going to be keen on having to run a build process just for a single config file. Some Windows users may not have all of the dependencies.

Perhaps the install instructions should be to download the generated file:

Installation

1. Download the .ideavimrc file from this repository to your home directory:

   # Unix/Linux/macOS
   curl -Lo ~/.ideavimrc https://raw.githubusercontent.com/cufarvid/lazy-idea/refs/heads/main/.ideavimrc
   
   # Windows Powershell
   Invoke-WebRequest -OutFile "$HOME/.ideavimrc" -Uri "https://raw.githubusercontent.com/cufarvid/lazy-idea/refs/heads/main/.ideavimrct"

or we could publish the file separately and use Github Actions to build.

[cufarvid]

Nice.

Given the number of moving parts, it seems like this should produce a downloadable artifact (.ideavimrc). I am not sure users are going to be keen on having to run a build process just for a single config file. Some Windows users may not have all of the dependencies.

Perhaps the install instructions should be to download the generated file:

Installation

1. Download the .ideavimrc file from this repository to your home directory:

   # Unix/Linux/macOS
   curl -Lo ~/.ideavimrc https://raw.githubusercontent.com/cufarvid/lazy-idea/refs/heads/main/.ideavimrc
   
   # Windows Powershell
   Invoke-WebRequest -OutFile "$HOME/.ideavimrc" -Uri "https://raw.githubusercontent.com/cufarvid/lazy-idea/refs/heads/main/.ideavimrct"

or we could publish the file separately and use Github Actions to build.

Absolutely agree. I think the GitHub Actions approach with publishing the .ideavimrc could be a nice approach.