terraform-ls VS vim-plug

Marcin here, one of the OpenTF folks

This repo [0] seems to still be licensed under MPL, so there is no need for an immediate action, but if there is a willingness in the community to take it over and improve, I see no reason why we wouldn't do it.

[0] https://github.com/hashicorp/terraform-ls

For example my other issue with simple click through URLs to resource documentation pages, this would be a simple solution if the resource documentation URL formatting was done to a standard with the resource names.

I have followed this guide: https://github.com/hashicorp/terraform-ls/blob/main/docs/USAGE.md

As /u/fridgedigga, neither LSP implements renaming. The LSP spec can be found here. I don't know how all of this is wired up. At a minimum, you'll need to add a mapping in service.go and handler. The bulk of work is performed in the handlers.

Look at terraform-ls vs terraform-lsp. Both can be used with coc.nvim.

For the LSP, I have never heard of Terraform before but it looks like they have a section on using it with vim/neovim. Not sure if this is already part of what you have tried, but I can't really help more since I have never used it.

This worked, thank you! I found all the cli options here for anyone that needs them.

https://github.com/hashicorp/terraform-ls

These are both fairly limited but you can see every editor (except intellij) uses this under the hood.

I've used them at companies with 300+ terraform repos and have never had much of an issue navigating/understanding TF through Vim.

So, what happens when you run the server from command line and then open your file in Kate? Any difference? Also, is there any command argument for logging and/or debugging the terraform-ls? It might help to find the issue, if any. I found this from the docs.

vim-plug

Did you really install VimTeX? Did you run :PlugInstall? Ensure you installed and set up vim-plug correctly (https://github.com/junegunn/vim-plug). If VimTeX is installed, it should be installed to '~/.vim/plugged', thus you can open a terminal, then cd ~/.vim/plugged/vimtex and you should find the files there.

If you're determined to use vim for some reason, I'd suggest checking out vim-plug: https://github.com/junegunn/vim-plug. Quite useful for installing and maintaining all of the plugins that you're going to need to get vim to provide even a subset of the features offered by modern editors.

I encourage you to add plugins to your vim (tip: use vim-plug). Use vimawesome.com for inspiration.

Personally, I like https://github.com/junegunn/vim-plug

But the plugin manager https://github.com/junegunn/vim-plug can also install from offline sources, without accessing Github:

To get started, simply install the plugin using your favorite plugin manager, such as vim-plug or packer.nvim. You can find detailed installation instructions in the README.

Not sure if Vundle did anything particularly fancy, but I'm using vim-plug [0] and have no complaints. It stays out of my way to the point that I had to look at my .vimrc just now to make sure that's what I was using.

[0] https://github.com/junegunn/vim-plug

I chose to move on to vim-plug and can report it was a simple switch from Vundle.