🦀 Supercharge your Rust experience in Neovim! A heavily modified fork of rust-tools.nvim
GPL-2.0 License
Bot releases are visible (Hide)
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
rust-analyzer.json
in favour of .vscode/settings.json
:h exrc
.vim.g.rustaceanvim.dap.autoload_configurations = true
, default),init_options
when starting the clientnil
safety in codeAction Group..vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] about 1 month ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
vim.g.rustaceanvim.dap.autoload_configurations = true
, default),init_options
when starting the clientnil
safety in codeAction Group..vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] about 1 month ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
init_options
when starting the clientnil
safety in codeAction Group..vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] about 1 month ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
init_options
when starting the clientnil
safety in codeAction Group..vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] about 1 month ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
init_options
when starting the clientnil
safety in codeAction Group..vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] about 1 month ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
init_options
when starting the clientnil
safety in codeAction Group..vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] about 2 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
nil
safety in codeAction Group..vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 2 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
.vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 2 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
.vscode/settings.json
by default.vim.g.rustaceanvim.server.load_vscode_settings
.stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 2 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 3 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 3 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
stdout
and stderr
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 3 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
on_attach
[#466].Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 3 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Rustc unpretty
: Support Windows.rustc
edition.vim.g.rustaceanvim.tools.rustc.edition
optionvim.g.rustaceanvim.tools.rustc.default_edition
.RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 3 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
RustLsp renderDiagnostic
.>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 3 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
>= 0.10.0
.cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 3 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
cargoExtraArgs
field,current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 3 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
current
/cycle
arguments toexplainError
and renderDiagnostic
commands.cycle
, which is current base behaviour. current
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 4 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
termopen
test executor if not using neotest
RustLsp
with selection ranges.rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.Published by github-actions[bot] 4 months ago
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
rustc
was always used due to a missing cwd
parameter).DYLD_LIBRARY_PATH
environment variable.allFeatures
setting by default.config.server.root_dir
option to override the rootrust-analyzer.json
settings"rust-analyzer":
key.check
insteadcheckOnSave
, to enable clippy if detected.<Esc>
to close buffer not silent.completionItem.snippetSupport
client capabilityfloat_win_config
.tools.float_win_config.open_split = 'vertical'
.--show-output
flag when runningrenderDiagnostic
and explainError
skipped diagnosticsrenderDiagnostic
and explainError
stopped searching earlyfloat_win_config.border
not applied--no-run
flags added to command when debuggingtools.code_actions.group_icon
.rust-analyzer
if the rustup wrapper is installed,rust-analyzer
isn't.renderDiagnostic
doesn't move cursor if it falls back to thetools.cargo_override
option tocargo
command for runnables/debuggables/testables.RustLsp [run|debug]
commands for running/debugging targets:RustLsp joinLines
.}
when applying code actionSnippetTextEdit
[#303].stderr
and stdout
to error message:RustLsp openDocs
command [#325]..vscode/launch.json
configurations that don't conflictRustAnalyzer reloadSettings
command to reload settings without restarting.vscode/settings.json
.vim.g.rustaceanvim.server.load_vscode_settings
true
[#286].server.settings
function can now take a default_settings
taberust-analyzer.json
:"rust-analyzer.foo.bar"
textDocument/definition
to std library [#285].:RustLsp! debuggables
not falling back to UI select:RustLsp! runnables
:RustLsp! testables
.RustLsp
command on client exiton_exit
[#267].<ESC>
keymap to close buffer.codelldb
adapter package (without the vscode extension)ftplugin/rust.lua
more than once on the same:e
on a buffer [#250].:Neotest summary
window [#247].dap.configuration.env
should betable
, not a string
."rust-analyzer":
key when importing settings from rust-analyzer.json
.reloadWorkspace
,rebuildMacros
or workspaceSymbol
from a non-rust buffer [#234].codelldb
): Redirect stdio
(stdout
) to a temp file.checkOnSave = false
not respected when clippy is installed4.6.0
).tools.crate_test_executor
option for running--all-targets
).unstable-options
.neotest
executor when using nextest
.test_executor
and crate_test_executor
.tools.enable_clippy
option (defaults to true
).cargo-clippy
installationserver['rust-analyzer']
, instead of replacing the server
config.cd
into directory with spaces [#212].:RustLsp[!] workspaceSymbol [onlyTypes?|allSymbols?] [query?]
.!
.require('neotest').run.run { suite = true }
.rustaceanvim.neotest
adapter with neotest.tools.test_executor
will default to a new 'neotest'
testables
or runnables
that are tests.require('neotest').run.run { strategy = 'dap' }
.:RustLsp debuggables
to set neotest's:RustLsp testables
: Prettier selection options.codelldb
): Redirect stdio
(stdout
) to a temp file.rust-analyzer.debugSingle
command capabilitynil
error if running :RustLsp! testables
and there is norust-analyzer.runSingle
tools.executor
and tools.test_executor
options.test_executor
is used for test runnables (e.g. cargo test
).'background'
that runs tests in the background:RustLsp testables
command, which is equivalent:RustLsp runnables
, but filters the runnables for tests only,[!IMPORTANT]
In Neovim < 0.10,
'background'
executor blocks the UI while running tests.
:Rustc unpretty
command:rustc -Z unpretty=[mir|hir|...]
to inspect mir and other things,tools.rustc
arguments for rustc
.:RustLsp!
, show only subcommands that changerunnables/debuggables last
.renderDiagnostic
: Window closes immediately if auto_focus
explainError
/renderDiagnostic
: Fall back to firstbufnr
passed into lsp.start
function when:RustAnalyzer stop
vim.lsp.commands
for rust-analyzer on the firstftplugin/rust.lua
more than once on the same:RustLsp runnables last
:RustLsp debuggables last
.!
).:RustLsp! debuggables
.vim.cmd.RustLsp { 'debuggables', bang = true }
, and the same'runnables'
.vim.ui.select
if there:RustLsp codeAction
.:RustLsp runnables args[]
and :RustLsp debuggables args[]
.:RustLsp codeAction
[#169].nil
safety in standalone files [#182].autoload_configurations
only for Neovim >= 0.10,nil
error when executing rust-analyzer.debugSingle
:RustLsp debuggables last
commands (introduced in 3.16.0).lldb
and codelldb
configurations found in launch.json
dap.configurations.rust
.nvim-dap
integration:require('dap').continue()
instead of :RustLsp debuggables
,vim.g.rustaceanvim.dap.autoload_configurations = false
.experimental/serverStatus
handler'sroot_dir
[#151].:RustAnalyzer restart
command.:RustAnalyzer
commands.
start
command if there is nostop
and restart
if there is an:RustLsp renderDiagnostic
command:cargo build
.Open in split
action to explainError
and renderDiagnostic
codelldb
adapter nvim-dap field when using codelldb
.tools.float_win_config
for all floating Windowsborder
, max_width
, max_height
, auto_focus
hover_actions
to float_win_config
.hover_actions
window options are still appliedlldb_commands
when using codelldb
.augmentsSyntaxTokens
capability.lspconfig.rust_analyzer
has been setup,nil
value" error [#105].Thanks @Andrew Collins:
dap.adapter
config value into the lldb
adapter, but only if thelldb
adapter is not already configured.dap.configuration
entry to config with the default behaviour of loadinglaunch.json
, or falling back to a basic configuration of the lldb
adapter.
dap.configuration
config value to configure the debug session,rust
configuration.probe-rs
.nil
checks for when there is no root project.:RustLsp flyCheck
: Typo in LSP client request,codelldb
installation detection - liblldb path.codelldb
installation detection (╯°□°)╯︵ ┻━┻.loop error
when auto-detecting mason.nvim codelldb
installation.require('rustaceanvim.dap').get_codelldb_adapter
require('rustaceanvim.config').get_codelldb_adapter
).codelldb
package.codelldb
package isn't nil
before using it.codelldb
if it is installed via mason.nvim.:RustLsp logFile
command, which opens the rust-analyzer log file.:RustLsp flyCheck
: Support run
, clear
and cancel
subcommands.cwd
.vim.g.rustaceanvim
is set,codelldb
lldb
[#74].sourceMap
correctly for both codelldb
and lldb
.codelldb
expects a map, while lldb
expects a list of tuples.:RustLsp hover actions
command suggesting action
.lldb-vscode
and lldb-dap
executable detection.lldb-dap
,lldb-vscode
, but may still have the:RustLsp runnables last
command [#62].tools.open_url
option,server.settings
option is a table [#56].codelldb
configurations.codelldb
configurations [#40].auto_generate_source_map
setting evaluates to false
.nil
checks [#32].std
.dap
/quickfix
executor: Fix setting cwd
for shell commands.:RustLsp
subcommands' arguments.plenary.nvim
dependency (dap
and quickfix
executor).plenary.nvim
dependencies left.dap
, crateGraph
, explainError
) [#26].:RustLsp explainError
command, uses rustc --explain
on error diagnostics with:RustLsp rebuildProcMacros
command.lldb-vscode
was installed.:RustLsp hover range
to accept a range.:RustLsp crateGraph
passing arguments as list.nil
upvalue when sending workspace/didChangeWorkspaceFolders
workspace/didChangeWorkspaceFolders
to prevent more than onerustaceanvim
,vxpm/ferris.nvim
,vxpm/ferris.nvim
was created just before I renamed my forkxdg-open
or open
(MacOS) by defaultnetrw
.vim.g.rustaceanvim.server.auto_attach
option, whichboolean
or a fun():boolean
that determinesRustLsp
command construction.hover
command validation.cargo
is not installed.RustAnalyzer [start|stop]
RustLsp [subcommand]
RustLsp moveItem [up|down]
rustaceanvim
.:RustSyntaxTree
and :RustFlyCheck
commands.:RustAnalyzerStart
and :RustAnalyzerStop
commands.:checkhealth rustaceanvim
).:help rustaceanvim
).tools.executor
to be a string.rust-tools.nvim
setup
functionvim.g.rustaceanvim
table.lspconfig
dependency.:RustAnalyzerStart
and :RustAnalyzerStop
rust-analyzer
binary is found.rt = require('rust-tools')
table.vim.cmd
Lua bridge,:lua vim.cmd.RustSSR()
or :RustSSR
0.9
.0.10
.