Question 1

How do I compile only part of my code with compiler-explorer.nvim?

Accepted Answer

Highlight the code in visual mode in Neovim and run the command `:'<,'>CECompile` to compile just that selection. This feature is useful for analyzing specific loops or functions without processing the entire file.

Question 2

Does compiler-explorer.nvim work with Rust or other languages besides C/C++?

Accepted Answer

Yes, it supports multiple compiled languages available on Compiler Explorer, including Rust, Go, and more, as it uses the API to fetch compilers and libraries based on the file extension or user selection.

Question 3

Can I use a local instance of Compiler Explorer with this plugin?

Accepted Answer

Yes, you can configure a local instance by setting the `url` option in the setup function, such as `require('compiler-explorer').setup({ url = 'http://localhost:10240' })`. This is documented in the configuration section.

Question 4

What's the difference between compiler-explorer.nvim and godbolt.nvim?

Accepted Answer

compiler-explorer.nvim offers deeper integration with Neovim's native APIs like vim.ui and vim.diagnostic, while godbolt.nvim might be simpler but less feature-rich. The choice depends on whether you prioritize seamless editor workflows over minimal setup.

Question 5

How to set default compiler flags permanently in compiler-explorer.nvim?

Accepted Answer

You can set default flags in the configuration via the `compiler_flags` option or language-specific settings in the `languages` table. For example, add `c = { compiler_flags = '-O2 -Wall' }` to apply flags for C code automatically.

Question 6

Is there a way to save the assembly output to a file?

Accepted Answer

The plugin doesn't include a built-in command to save output directly, but you can manually copy from the assembly buffer or use Neovim's write commands. Future updates might add this feature, but currently, it's focused on in-editor display.

Question 7

What happens if the Compiler Explorer API is slow or down?

Accepted Answer

Compilation will fail or timeout, as the plugin depends on external API calls. You can adjust the `job_timeout_ms` in configuration, but reliability is tied to the service's availability, which is a key limitation for critical workflows.

compiler-explorer.nvim

What is compiler-explorer.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions