Question 1

How to set up code_runner.nvim for Python with arguments?

Accepted Answer

Define a function in the filetype config using vim.ui.input to prompt for arguments, e.g., for Python, set 'python = function() ... end' to run 'python3 -u $file' with inputs. This allows interactive testing without leaving Neovim.

Question 2

Can code_runner.nvim run Java projects with Maven or Gradle?

Accepted Answer

Yes, configure project-specific commands in Lua or JSON, such as 'command = "mvn compile exec:java"' for Maven. Use the project management feature to define patterns matching your project root.

Question 3

code_runner.nvim vs vim-test: which is better for testing?

Accepted Answer

code_runner.nvim is general-purpose for code execution and project runs, while vim-test is specialized for running test suites. Choose vim-test if you focus on testing frameworks, or code_runner.nvim for broader execution needs.

Question 4

How to enable hot reload with code_runner.nvim?

Accepted Answer

Use custom hooks with Lua functions, like in the README's markdown example, to compile on save. The experimental hot_reload option is available but less recommended than creating autocommands for stability.

Question 5

Does code_runner.nvim work with toggleterm?

Accepted Answer

Yes, set mode = 'toggleterm' in setup, and it integrates with toggleterm.nvim for terminal-based execution. Ensure toggleterm is installed and configured separately for smooth operation.

Question 6

What are the variables like $dir and $fileName in commands?

Accepted Answer

These are placeholders replaced at runtime: $dir is the file's directory, $fileName is the full filename. They mirror VS Code Code Runner's format for compatibility and ease of migration.

code_runner.nvim

What is code_runner.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions