Nvim-R VS nvim-treesitter

If you do a lot of R coding, then a package more specific to R, and more fully featured is Nvim-R.

The whole reason I ended up going this route was also sort of data-science related: there’s a really spectacular R plugin for Vim, which I wanted to recapitulate as best I could when using python: https://github.com/jalvesaq/Nvim-R

I am slowly getting into using neovim. I am now trying to setup my R programming environment. I have successfully installed Nvim-R with Packer (https://github.com/jalvesaq/Nvim-R). Now, I would like to use the radian console (https://github.com/randy3k/radian/blob/master/README.md#nvim-r-support). In the documentation, it is said to put this in the config file:

But just wondering if people have tried using it with the Nvim-R plugin? I'm not sure it is worth the effort for me looking through the steps needed. Also, do I need to switch my init.vim/vimrc to lua? Perspectives appreciated!

However, there doesn't seem to be much available support yet for Quarto editing. The only plugin I could find is limited to syntax highlighting. To my knowledge, Quarto also isn't a built-in filetype yet. I've worked around this by manually creating a filetype and using R Markdown syntax highlighting with the Nvim-R plugin, which lets me send R code in chunks to a REPL and see results while I edit. Nvim-R also supports evaluation of Python code chunks using an R package that evaluates Python code, but that's not an ideal solution for editing a Python-only file.

looking for a neovim plugin that's similar to Nvim-R, but for python.

For that reason, I want to use Nvim-R in combination with ncm-R. I get the completion to work if I use it manually with Ctrl+x Ctrl+o, but it does not start automatically. My init.vim file looks like this:

I use Nvim-R. It took a bit of time to learn the key bindings, but the documentation is pretty clear.

If you want to go in a very different direction, you can try vim (or neovim) with nvim-r. For a variety of reasons, that’s what I tend to use.

nvim + Nvim-R user here as well.

I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.

These two plugins are the bare minimum in my view.

https://github.com/nvim-treesitter/nvim-treesitter

Treesitter gives you much better syntax highlighting based on a parser for a given language.

https://github.com/neovim/nvim-lspconfig

This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:

https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.

pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server

Best of luck! Happy hacking.

It was changed in https://github.com/nvim-treesitter/nvim-treesitter/commit/78b54eb

https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.

vim.opt.rtp:prepend(lazypath) require('lazy').setup({ { "nvim-neorg/neorg", build = ":Neorg sync-parsers", opts = { load = { ["core.defaults"] = {}, -- Loads default behaviour ["core.concealer"] = {}, -- Adds pretty icons to your documents ["core.dirman"] = { -- Manages Neorg workspaces config = { workspaces = { notes = "~/notes", }, defaultworkspace = "notes", }, }, }, }, dependencies = { { "nvim-lua/plenary.nvim", }, { -- YOU ALMOST CERTAINLY WANT A MORE ROBUST nvim-treesitter SETUP -- see https://github.com/nvim-treesitter/nvim-treesitter "nvim-treesitter/nvim-treesitter", opts = { auto_install = true, highlight = { enable = true, additional_vim_regex_highlighting = false, }, }, config = function(,opts) require('nvim-treesitter.configs').setup(opts) end }, { "folke/tokyonight.nvim", config=function(,) vim.cmd.colorscheme "tokyonight-storm" end,}, }, }, }) require 'plugins' ```

Change the compiler to use 'llvm' and install visual studio build tools command line stuff - at least that is what worked for me without problems. If you are using c++ then I would assume you have visual studio installed already. If you need more info follow the treesitter windows support

After a lot of time spent yesterday I took a fresh look today and then thought to myself - what if this is what TS does by design? A few clicks later and I found this https://github.com/nvim-treesitter/nvim-treesitter/issues/1327

I've followed the official guide for nvim-treesitter support on Windows, but I'm having problems making it work. I keep getting a compilation error for any parser I try to install using TSInstall. If instead I use TSInstallSync I don't get errors but the parser is not correctly installed. My setup uses lazyvim and I installed LLVM using winget to have a C compiler.

I have read that gcc in windows doesn't always provide the necessary support for treesitter. I have seen ppl prefer clang over gcc in Windows. Please see also Windows support in treesitter's repo. Unfortunately I cannot help further as I don't use Windows for coding, but hope you can deduce something to solve your problem from the above link (if you haven't already read through it).